Our project is contained within and EAR file that contains both an EJB project and a web project, which utilizes JSF. We are attempting to deploy our application into a cluster and I have followed the documentation pertaining to the specific settings needed for distributing the application.
[b][u]In web.xml:[/u][/b]
<distributable/>
[u][b]In sun-web.xml:[/b][/u]
<session-config>
<session-manager persistence-type="replicated">
<manager-properties>
<property name="persistenceFrequency" value="web-method" />
</manager-properties>
<store-properties>
<property name="persistenceScope" value="session" />
</store-properties>
</session-manager>
</session-config>
My question pertains to EJB references that we have defined as properties of our managed-beans. If I have a managed-bean, call it SalesRepsBacker, that implements java.io.Serializable, and within this bean I have references to several stateless EJB's, (which would also need to be serializable), will the stateless EJB's still be accessible and functional after serialization from one server in the cluster to the other, or should I define these properties as transient and perform a look-up each time I need them?
Thanks for the help...
[Message sent by forum member 'cmathrusse' (cmathrusse)]
http://forums.java.net/jive/thread.jspa?messageID=295706