I just worked through an issue where my development JBoss server started directing EJB calls to my local JBoss server.
It turns out I accidentally copied jndi.properties from our client app into a JAR on my local JBoss server. The new jndi.properties pointed at the development JBoss server and apparently caused my local EJBs to register with JNDI on the development server. Is there any way to make the JNDI server read-only to external clients? Or at least ignore jndi.properties found outside the conf directory? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871193#3871193 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871193 ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
