PROTECTED]
To: JBoss-Dev [EMAIL PROTECTED]
Sent: Thursday, April 26, 2001 3:39 AM
Subject: Re: [JBoss-dev] Bug in jnp (handling references to remote JNDI servers)
I run into a similar problem with EJB handles:
BeanA is on host1, JBoss1
BeanB is on host2, JBoss2
BeanA creates an EJB
Right, the name should be the full jnp url not just the local jndi name.
- Original Message -
From: Alf Werder [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 26, 2001 8:50 AM
Subject: Re: [JBoss-dev] Bug in jnp (handling references to remote JNDI servers)
The problem
| To fix this, all proxy objects need to know the host, they are
| originating from.
If you really want to do that (because you really need to use the code you
just showed us) then go ahead and work on the JNP stub classes also the home
must be able to extract that information from the IC (is
It seems to me that there is a bug in JNP NamingContext.checkRef() method
Here is when I encounter
BeanA is on host1, JBoss1
BeanB is on host2, JBoss2
BeanA is supposed to call BeanB, so it has an entry in jboss.xml that maps
ejb-refejb/BeanB/ejb-ref
to
PROTECTED]
Sent: Wednesday, April 25, 2001 1:54 PM
Subject: [JBoss-dev] Bug in jnp (handling references to remote JNDI servers)
It seems to me that there is a bug in JNP NamingContext.checkRef() method
Here is when I encounter
BeanA is on host1, JBoss1
BeanB is on host2, JBoss2
BeanA
