Managed bean/Data exchange between two ADF Rich Faces based applications

Question

Hi,
I have been trying to research what seems to be a small issue. My requirements are as follows.
1. I need to be able to pass managed bean information from one ADF Rich Faces based application to another (in two separate ears) at runtime (e.g. from Ear1: SenderApp/Sender.jspx -> Ear2: ReceiverApp/Receiver.jspx).
2. I do not want to use the database as my applications need to be performant.
3. Serialization/de-serialization would fall pretty much under the database category. In other words, I like to avoid Serialization/de-serialization of the managed bean.
4. I cannot use query string due to security issues.
My question is as follows:
1. Is there any standard/architecture/best practices for data exchange of backing beans or other forms between two ADF Rich Faces based apps (in two separate ears)?
2. Has someone found anything similar to an applicationScope that works across applications?
I would appreciate any ideas.
Thanks very much,
Edited by: user11219846 on Jul 23, 2009 2:38 PM
Edited by: user11219846 on Jul 23, 2009 2:42 PM

Answer 1

Hi,
its not an ADF Faces problem, but not possible in Java EE. You can however fallback to vendor specific implementations like in WLS. From the WebLogic documentation : http://e-docs.bea.com/wls/docs103/webapp/sessions.html
Enabling Web applications to share the same session*
By default, Web applications do not share the same session. If you would like Web applications to share the same session, you can configure the session descriptor at the application level in the weblogic-application.xml deployment descriptor. To enable Web applications to share the same session, set the sharing-enabled attribute in the session descriptor to true in the weblogic-application.xml deployment descriptor. See “sharing-enabled” in session-descriptor.
The session descriptor configuration that you specify at the application level overrides any session descriptor configuration that you specify at the Web application level for all of the Web applications in the application. If you set the sharing-enabled attribute to true at the Web application level, it will be ignored.
All Web applications in an application are automatically started using the same session instance if you specify the session descriptor in the weblogic-application.xml deployment descriptor and set the sharing-enabled attribute to true as in the following example:
+<?xml version="1.0" encoding="ISO-8859-1"?>+
+<weblogic-application xmlns="http://www.bea.com/ns/weblogic/90";;>+
+...+
<session-descriptor>     
+<persistent-store-type>memory</persistent-store-type>+
+<sharing-enabled>true</sharing-enabled>+
+...+
+</session-descriptor>+
+...+
+</weblogic-application>+
Frank