We continue having trouble to acquire correct SFLB-instance to the
web-deployment (in an EAR on JBoss 4.2.1). It appears the web-session is not
identical with the client-session on the EJB-tier, hence JNDI delivers a new
instance of that SFLB instead of the one already assigned to this user.
bean-class:
@Stateful
| @Name("shopTree")
| @Scope(ScopeType.SESSION)
| @CacheConfig(idleTimeoutSeconds=3600)
| public class ShopTreeBean implements ShopTree {
|
| @PersistenceContext
| private EntityManager em;
|
| @Logger
| private Log log;
|
| @In
| private ApplicationUser applicationUser;
In the facelet, the correct instance can be addressed via #{shopTree.xxx}
Now this bean is published to the WEB-deployment by the following code:
jboss-web.xml:
<jboss-web>
| <ejb-local-ref>
| <ejb-ref-name>ejb/ShopTree</ejb-ref-name>
| <local-jndi-name>app/ShopTreeBean/local</local-jndi-name>
| </ejb-local-ref>
| </jboss-web>
web.xml:
<ejb-local-ref>
| <ejb-ref-name>ejb/ShopTree</ejb-ref-name>
| <ejb-ref-type>Session</ejb-ref-type>
| <local-home>java.lang.Object</local-home>
| <local>pkg.ShopTree</local>
| <ejb-link>app/ShopTreeBean</ejb-link>
| </ejb-local-ref>
If we lookup this EJB using context "app/ShopTreeBean/local" , we get ANOTHER
(new) instance.
What additional configuration is needed in order to make JBoss EJB deliver the
correct SFSB-instance that is already assigned to that user?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4103171#4103171
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4103171
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
