From the client’s perspective, a Singleton bean always supports concurrent access. In general, a Singleton client does not have to concern itself with whether other clients might be accessing the Singleton at the same time.

From the bean developer’s perspective, Read more...

• A singleton session bean instance’s life starts when the container invokes the newInstance method on the session bean class to create the singleton bean instance.
• Next, the container performs any dependency injection as specified by the metadata annotations on the

• The EJB container is responsible for determining when to initialize a singleton session bean instance.
• However, the Singleton Session bean can be requested to be initialized by the container upon application startup. This is called eager initialization and can be

Business Interface

Create the bean interface and mark it either as @Remote, @Local or @WebService.

Remote Interface

Local Interface

Web service interface

Bean implementation class

Create a class which implements the business interface. Mark this class as singleton session bean Read more...

The @Singletion annotation is used to mark the class as Singleton Session Bean. This annotation’s specification is as follows.

@Target(value=TYPE)
@Retention(value=RUNTIME)
public @interface Singleton 
{
	String description() default “”;
	String name() default “”;
	String mappedName() default “”;
}

where, Read more...

• Available from EJB 3.1, Singleton Session Beans are business objects having a global shared state within a JVM.
• The @Singleton annotation is used to mark the class as Singleton Session Bean.
• They are instantiated once per application and exist

• The application container can pool instances of stateless session beans to increase performance.
• When the client requests an operation on the bean, the container can assign an available instance from the pool reducing instance creation overhead.
• After completion the bean

• 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.
• Next, the container performs any dependency injection as specified by metadata annotations on the

The lifecycle callbacks are methods defined in the bean class but not in business interface which the container calls when specific lifecycle event or transition occurs. The following two annotations are used to define lifecycle callbacks on stateless session beans. Read more...

Business Interface

Create the bean interface and mark it either as @Remote, @Local or @WebService.

Remote Interface

Local Interface

Web service interface

Bean implementation class

Create a class which implements the business interface. Mark this class as stateless session bean Read more...