Choosing and developing a Session Bean

Use a session bean if:

1. Only one client has access to bean at any given time
2. State of bean is not persistent
3. Bean represent a web service

Use a Stateful Session bean if:

1. Bean state represent client interaction
2. Bean needs to hold client data across interactions
3. Bean acts as a client mediator to other beans
4. Need thread-safe interactions

Session Bean cardinality(taken from DevelopIntelligence)

From the diagram, you can see that Stateless and Singleton beans looks very similar when it comes to Client-bean instances, except that in singleton all the clients access single object while in Stateless some objects are uses by clients and returned back to pool.

Developing a Session Bean

Steps to create a session bean:

1. Define business logic interface
2. Annotate the business interface
3. Create the session bean, implementing the interface
4. Annotate class defining type
5. Compile, deploy and debug as discussed above

Advertisements