SessionBean non-reentrancy?

Question

Can a SessionBean invoke a method on itself through its local or remote interface without violating the non-reentrancy rule?

Answer 1

Interesting. Without trying this I'm only speculating, but I would suspect
the container to throw an EJBException at a.bar(). Have you tried it?
You could accomplish your goal using the second coding style and configuring
the bean to use BMT. That would allow bar() to begin/commit/rollback a
UserTransaction.
Bill
"Bjvrn Hamrin" <[email protected]> wrote in message
news:23318269.1106816185992.JavaMail.root@jserv5...
Thanks for the reply.
Ok, having two SessionBeans eliminates any reentrancy problem. What I wasconsidering was having only one, by writing code something like this:
>
public class ABean implements SessionBean
public void foo()
A a = (A) sessionContext.getEJBLocalObject();
a.bar();
This is nearly the same as:
public class ABean implements SessionBean
public void foo()
bar();
Except that by using the local interface I would expect that transactionattributes and other stuff in deployment descriptors should have effect. In
my case I don't want any transaction in foo(), but bar() must have a
transaction.
>
/Björn