JNDI has two parts: 1) Deployment - binding jms admin objects into jndi - suitable for this forum because JBossMQ does that work.
But nobody ever reports a problem on that side since JBossMQ knows what it is doing. Except the infamous XAConnectionFactory not bound problem FAQ (AKA I have broken my server configuration but can't read server logs properly). 2) Accessing JNDI - client code and/or network/jndi configuration problems - not JMS code and not a topic for this forum. http://www.jboss.org/index.html?module=bb&op=viewforum&f=214 This forum is full of type (2) just because the object being looked up is a jms destination or connection factory. The object being looked up is entirely irrelvent to the problem. (2) would be a problem for this forum if your naming context used jms as its transport :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873825#3873825 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873825 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
