Search:

Right ...

I was thinking that even if you use Spring AOP for coarse grained objects (or business objectw) as it is used for transaction demarcation, with millions of simultaneous transactions the...

Hello,

As Spring documentation states "Spring defaults to using J2SE dynamic proxies for AOP proxies". The other alternative is to use CGLIB proxies.

However I'm a bit worried about first...

I must admit that this is quite interesting. From your last traces it looks like the JDBC Connection is closed before JTATransactionManager triggers rollback.


...hmm.... may this indicate a...

Hi,

From your trace



it looks like Spring transaction manager is setting the transaction to be rolled back but JTA transaction started by Weblogic when you're calling your EJB for some...

I forgot to mention about one other thing. If some other participant of the transaction causes a rollback, and you want your broker to also rollback, then I guess DataSource from Broker needs to be...

Here is how I see things:

1. Make a POJO and wrap it around your Service layer.
2. Make it transactional (very important).
3. If your Broker layer throws an exception (e.g. SQLException) and it...

One solution that I see right now is to use POJO wrappers over your "jar" objects, and make these POJO's to participate in a transaction e.g thourgh TransactionProxyFactoryBean.

It looks like there is very elegant way of getting notified on rollback. AbstractPlatformTransactionManager uses TransactionSynchronizationManager to notify registered TransactionSynchronization...

Right, I don't really need to be notified on commit . Now regarding rollback I guess that by "watch" you mean to catch those exceptions. ... hmmm I would like a more graceful mechanism. I guess...

Hi,

Here is a scenario:

1. Assume that I have 2 beans that are business logic POJOs
2. I'm making these 2 beans part of the same transaction.
3. From bean A I call a method from bean B
4....