About Question enthuware.oce-ejbd.v6.2.492 :

[deadlock_gr]

I have 2 points:

1. The business method is not called by the container, but by the client.
2. Also, what if the setSessionContext method does not exist, and the SessionContext is rather injected?

[admin]

1. It is the container that invokes the business method as result of a call from the client.
2. Even if the Session Context is injected, it would be done after the constructor is done. But your point is valid, this may cause confusion. It needs to be improved.

Thanks for the feedback!

[jszczepankiewicz]

misspell in explanation:
(...)It can also not implement SessionSyncrhonization.

[admin]

Fixed. Thanks for your feedback!

[kezman9]

The answer says that the first method called on SLSB by container is constructor. I think it's precise to say that container calls newInstance on bean class which in turn invoke the zero-argument constructor.

Spec 4.7.1

A stateless session bean instance’s life starts when the container invokes the newInstance method on the session bean class to create a new session bean instance.

But as for me the original explanation is also clear.

Thanks,
Jarek

[admin]

The answer says that the first method called on SLSB by container is constructor. I think it's precise to say that container calls newInstance on bean class which in turn invoke the zero-argument constructor.

Fixed.

thank you for your feedback!