I found what was it: even though i am using a different InitialContext (created to point to the remote box), the Session bean B 's JNDI name existing localy in the ENV it takes over, and any lookups (even using different InitialContext's) is done using this exisiting jndi name. I wonder if this is a bug in the NamingService implementation? Differrent NamingContext associated with different NamingServers should not override eachother. Thoughts? Art.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871341#3871341 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871341 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
