Its all right ;) I found the problem - it was in a framework we're using. They force a setRollbackOnly in all cases where something 'bad' happens. And in this instance the business code was written to catch the error and choose an alternate path. Hence, a great example of how *not* to write a framework ;D A framework should always help the user achieving their goal by lightening their load but without forcing them down paths they might not want to go ;) Ah well - I guess I'll have a chat with the framework guys :D
Cheers, C View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886754#3886754 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886754 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
