[jboss-jira] [JBoss JIRA] Updated: (JBAS-3261) Serialization of EJB handles

Tue Jul 25 17:19:11 EDT 2006

     [ http://jira.jboss.com/jira/browse/JBAS-3261?page=all ]

Dimitris Andreadis updated JBAS-3261:
-------------------------------------

    Fix Version/s: JBossAS-4.0.6.CR1
                       (was: JBossAS-4.0.5.CR1)

> Serialization of EJB handles
> ----------------------------
>
>                 Key: JBAS-3261
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3261
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>    Affects Versions: JBossAS-3.2.8.SP1, JBossAS-4.0.4.GA
>            Reporter: Lars Kral
>         Assigned To: Scott M Stark
>             Fix For: JBossAS-4.0.6.CR1
>
>         Attachments: test-ejb.jar
>
>
> According to [JBAS-1620], we have to use org.jboss.naming.NamingContextFactory to allow the handle to remember the JNDI environment that was in effect when it was created. But what about handles constructed inside the JBoss server JVM and later serialized into the client JVM? Each JVM may use different properties to access the JNDI - e.g. the "java.naming.provider.url" property, which is not available in the JBoss JVM but is required in a client JVM. Sure, I can add the "java.naming.provider.url" property to the $JBOSS_SERVER_HOME/conf/jndi.properties file, but as far as I know this forces in-VM calls to use RMI.
> Please have a look at the attached testcase (sources are included). The code works in our production environment (v3.2.7) but fails with the latest JBoss releases (4.0.4.GA and 3.2.8.SP1).
> Regards,
> lkral

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira