Ans:

For get access a J2EE session from RemoteObject in flex we have follow the following description.

Flex preconfigures a session servlet in the default web.xml file, which makes available a server-side Java object that can be used to access and modify the J2EE session for an application. By placing one of the following Remote object definitions in our Service Locator at services.mxml, we make available to our application a service that can get and set objects in the J2EE session, as well as remove objects from the session:

As with any other tag, the session service can use result and fault event handlers to handle requests to fetch items from the session.

The web.xml descriptor defines the name of the session servlet as servlet; therefore, we use one of the following examples to work with the J2EE session:

sessionObject.session( "set", "customerID", 500 ); sessionObject.session( "get", "customerID" ); sessionObject.session( "remove", "customerID" );

These three examples demonstrate how the session service is used to get, set, or remove items in the J2EE session from a Flex client.

As a best-practice, we recommend that access to the J2EE session be encapsulated in a client-side SessionDelegate Business Delegate in the same way that we recommend interaction with other server-side Java objects. Furthermore, because setting and getting items in the J2EE session is a relatively expensive operation compared with setting state on the client, we advocate using value objects in their role as ?bulk accessors? to get and set a number of related properties.