Java Doc for SessionBean1.java in  » ESB » open-esb » org » openesb » tools » charting » Java Source Code / Java DocumentationJava Source Code and Java Documentation

Session scope data bean for your application. Create properties here to represent cached data that should be made available across multiple HTTP requests for an individual user.

An instance of this class will be created for you automatically, the first time your application evaluates a value binding expression or method binding expression that references a managed bean using this class.

This method is called when this bean is removed from session scope.

This method is called when this bean is initially added to session scope.

This method is called when the session containing it is about to be passivated.

Construct a new session data bean instance.

This method is called when the session containing it was reactivated.

You may customize this method to reacquire references to session data or resources that could not be serialized with the session itself.

This method is called when this bean is removed from session scope. Typically, this occurs as a result of the session timing out or being terminated by the application.

You may customize this method to clean up resources allocated during the execution of the init() method, or at any later time during the lifetime of the application.

Return a reference to the scoped data bean.

This method is called when this bean is initially added to session scope. Typically, this occurs as a result of evaluating a value binding or method binding expression, which utilizes the managed bean facility to instantiate this bean and store it into session scope.

You may customize this method to initialize and cache data values or resources that are required for the lifetime of a particular user session.

This method is called when the session containing it is about to be passivated. Typically, this occurs in a distributed servlet container when the session is about to be transferred to a different container instance, after which the activate() method will be called to indicate that the transfer is complete.

You may customize this method to release references to session data or resources that can not be serialized with the session itself.