No, it was something a teacher told my collegue when he attended a Java EE 5 course. I got curious as to why (as the teacher didn't say) and thought I would ask you folks as most of you are more experienced with JEE than me.
So if anyone can give a reason as to why, or why not, you certainly have my attention. [ May 26, 2008: Message edited by: Kent Larsson ]
author & internet detective
I have a reason for why not: Session bean methods are just methods. The outer one gives you the lifecycle management support (transactions, security, etc). After that, you are just calling Java methods.
This is common when signatures are deprecated. If I have method(int) and want to change it to method(int, int), I may want to stay backward compatible for a while and have the later call method(int, 0). Just like in regular Java.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: EJB 3.0: SLSB with two methods a() and b(). Is it bad practise calling b() from a()?