We are getting you a rw passwd,
go ahead and fix what you want.
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Anatoly Akkerman
|Sent: Wednesday, April 25, 2001 4:54 PM
|To: JBoss-Dev
|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 is supposed to call BeanB, so it has an entry in jboss.xml that maps
|<ejb-ref>ejb/BeanB</ejb-ref>
|
|to <jndi-name>jnp://host2:port/testapp/BeanB</jndi-name>
|
|After obtaining the LinkRef and resolving it, JNP does not contact the
|remote server on the remote machine (checkRef() only obtains a new Naming
|for the server if the current one is null, which is wrong in this case of
|a remote reference, since we are leaving the current Naming of the local
|machine and have to contact the remote now). One way to fix it is to
|remove this if (naming == null)
|
|around checkRef() body but it would obviously hurt performace. Any better
|ideas?
|
|-------------------------------------------------------------------------
|Anatoly Akkerman
|Computer Science Dept.
|Courant Institute of Mathematical Sciences, NYU
|719 Broadway, #715 Tel: 212 998-3525
|New York, NY 10003 Fax: 212 995-4123
|-------------------------------------------------------------------------
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development