Originally posted by Sankar Subbiramaniam:
Note: In EJB, a deployed bean is a client of the container.
Hope this helps.
It's confusing. Sankar, I don't think it's right to say that bean is a client to container.
This is how I understand it so far: A bean is an object inside container. However, whatever business methods you call on a bean, you are really calling on a subclass of bean you wrote. The container adds more meat to the class you write and extends it. So in the grand scheme of things, container is controlling everything but in between at appropriate times, it calls methods which you wrote. This is already agreed upon in spec that what services container will provide and at what time and situation it will callback the bean methods. The agreed upon methods are container callback methods. You can also add methods which are not defined in the spec or in other words are not container callback methods but they will never be called by container and should be called from container callback methods you write, otherwise they will be use-less.
The container callback name seems to appropriate in this situation. Do you have more appropriate name in mind?