The JNDI name of the session bean: SomeSBHomeRemote.JNDI_NAME (which is: public static final String JNDI_NAME="ejb/SomeSBRemote";) So it will be the same deployed on the local box and the remote box, and the session bean is deployed on box computers. But on the local box I am using a InitialContext set up to point to the remote box. So I dont think why it has this featuretter and overrides the lookup. It looks to me that it binds the JNDI name to a NaminServer and any subsequent lookups (en usiveng different NamingServers) are done via this binding. This is not desired at all: whats the point of having NamingServers if on can overtake the other (functionality wise)?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871472#3871472 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871472 ------------------------------------------------------- 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
