To your first question: if your session beans launch not Runtime exceptions and you catch them, the transaction is not rolled back. You can create your own exceptions to get this behaviour, for example... To question a): deciding on one of the two approaches is subjective... For a good design, your method should throw an application exception you have created, but when throwing and exception (and catching it too) creates overhead on your app, so it's up to you... To question b): better don't use the "not supported", because if you access these session beans from a web-app, by default I think it uses a transaction, so when you call the bean it will throw an exception... But I think that with my first answer this question has no sense...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857807#3857807 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857807 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
