0 Replies Latest reply on Mar 27, 2010 4:30 PM by David Small

    JBoss's NamingContext favoring local references

    David Small Newbie

      Hi, I'm using JBoss 4.0.4 that has EJB3 services. Our application is a small inhouse Content Management System (CMS) that our internal authors use to change static content on our web sites. Currently, they prepare content in our TEST environment and then manually copy it to our CMS application in PROD. I've added a component that allows the authors to simply publish content entered into TEST to PROD. The last step is for the TEST environment to make a remote call to the EJBs in PROD to send the content.


      The code instantiates a new InitialContext with the appropriate provider URL and attempts to get the PROD version of the necessary EJBs. For some unknown reason it instead gives me the EJBs from the TEST instance (which is the instance that the publisher is running in). I've even copied the code to a standalone Java application to test outside a JBoss container where it works fine. It appears that for whatever reason the org.jnp.interfaces.NamingContext will ignore the provider URL if it can find the object in the current instance even if disableDiscovery is set to TRUE.


      Does anyone have experience with this problem? Any help would be appreciated.