concept session bean component in category seam

appears as: session be components, session bean component, session be components
Seam in Action

This is an excerpt from Manning's book Seam in Action.

Seam session bean components differ from other Seam component types in one fundamental way: Seam doesn’t create instances of session bean components using the default constructor of the class. Instead, the work of instantiating the class is delegated to the EJB container. The EJB container is responsible for managing session bean components in the same way that Seam manages JavaBean components.

When the Seam container determines that an instance of the component needs to be created, Seam asks the EJB container for a reference to the session bean instance using a JNDI lookup. Once Seam has a reference to the session bean instance, Seam adds additional services to it and then binds it to a context variable, just as Seam would do with a JavaBean component instance. The two containers are working together to create and initialize an instance of a session bean component.

The fusion with the EJB container occurs when the Seam container receives a request for an unassigned context variable that’s associated with a session bean component. To resolve a value, Seam performs a JNDI lookup to get a reference to the corresponding session bean in the EJB container. This lookup is part of the standard EJB mechanism.