"JerryGauth" wrote : I don't have any information on your problem, just an observation about the Global Namespace in the JNDIView mbean. | | The Global Namespace is unrelated to HA-JNDI; it's a store for local JNDI bindings. So if you bind something in HA-JNDI, it won't appear there. Of course, HA-JNDI should locate bindings in local namespaces on other nodes so if something is bound there on one node, it should be found via an HA-JNDI lookup on any node. | | JBossAS 4.0.4 includes HA-JNDI bindings in the JNDIView mbean's list() output so that you can also view HA-JNDI bindings. They're included under the heading HA-JNDI Namespace. Sorry, I didn't know that. However, the problem remains. We wrote our own HAJNDIView MBean, which gets it's InitialContext via:
| Properties properties = new Properties(); | properties.setProperty(Context.PROVIDER_URL, bindAddress); | properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); | properties.setProperty(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); | InitialContext context = new InitialContext(properties); | When using exactly the same properties with a standalone client, we get the right context back. When using this inside the server, we get something else. Is that intended? Regards, Martin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928747#3928747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3928747 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
