Yep, we've walked that same path too. Unfortunately there are few long running transactions which need write access and these seem to screw things up.
We also have long running transactions, calling potentially external applications from our workflow app, but we have chosen to restructure the app and follow the readers/writers strategy imposed by the pessimistic/read-only combo.
We defer most of our writes as late as possible to cut down on the contention and use separate transactions for those we can't.
By the way, does anyone know how wildcarded "read-only" methods (e.g. get*) apply when the method has been inherited from another class?
It applies to all matching members of the defined interface used to expose it.
In other words if I have getSomething() in class A, and then create class B which inherits from class A.
Will a get* rule in class B also apply to the getSomething() method inherited from class A?
Good luck.
Kev
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
