Hello Gloxinia, Stateless session bean's ejbCreate() is very ambiguous for sure. When container creates stateless session beans, container won't assign a valid EJBOject which represents a client but it assigns a dummy/fake EJBObject to the bean inorder to create the bean. So in this case you can access getUserTransaction method and UserTransaction methods but these are not valid as there is no real EJBObject is assigned to it.
So to avoid that confusion people think there can't be a UserTransaction access in ejbCreate method in Stateless Session Bean since there is no valid EJBObject available in that method .
please correct me if I am wrong here.
What's that smell? I think this tiny ad may have stepped in something.