Hi Scott thanks for the reply. Your right in my described example I could perform setRollbackonly() after I access the entity bean to get around the issue.
But this is not the only place I may want to access business functions. I actually catch this exception further up stream, to throw a new application exception. Each public api set the middleware exposes has its own exceptions and transfer objects independant of my service layer. It is imperative I dont expose any service or domain level objects to my client applications, for api stability / deprecation management etc... As such I would need to perform additional business operations after the original exception is thrown to better describe the exception with context to the client app. I suppose I could stop calling setRollbackOnly in my Service layer and call it when I catch the Exception upstream. But this would just be a workaround, it really should be marked for rollback by the business rules. I hope this better describes my situation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905049#3905049 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905049 ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
