Oct 16th, 2007, 09:11 PM
Default transactionAttribute if method name doesn't match?
If while using a TransactionProxyFactoryBean, if the method name masks in the transactionAttributes don't match a particular method in the target class, what exactly will be used if that method is called? For instance, will it essentially use PROPAGATION_REQUIRES_NEW, or something else?
Oct 17th, 2007, 01:18 AM
Oct 17th, 2007, 08:48 AM
Normally, the method mask is supposed to match the methods in the target class (the DAO class, usually), correct? Well, in the instance I'm describing, I realized that the method called in the target class to do the work isn't covered by the method mask.
So, assuming this method is doing a "save", and a previous step in the same request did a retrieve from the database, would the second call result in a second session or transaction, as if it defaulted to "PROPAGATION_REQUIRES_NEW"?
I'm just trying to look for details that might explain some symptoms we were seeing.
Oct 17th, 2007, 09:42 AM
No transaction is started then, so in effect it works just like "SUPPORTS" propagation.