Hello,
I see a current behaviour with the last 3.0 snapshot and the 3.0 alpha. The
home stub of a bean is not bound to the jndi name that is specified in
jboss.xml. Example below uses testbean2.jar from the testsuite.
After a compilation from a clean snapshot, I deployed testbean2.jar and
checked with JNDIView (through the JMX HTML tool on 8082).
In java:comp everything is fine:
=======================
java:comp namespace of the AllTypes bean:
+ env (class: org.jnp.interfaces.NamingContext)
| + ejb (class: org.jnp.interfaces.NamingContext)
| | + entity[link -> nextgen.EnterpriseEntity] (class:
javax.naming.LinkRef)
| | + stateful[link -> nextgen.StatefulSession] (class:
javax.naming.LinkRef)
| | + stateless[link -> nextgen.StatelessSession] (class:
javax.naming.LinkRef)
=======================
it indicates that beans are linked to nextgen.XXX but *no* nextgen.XXX
bindings exist in the global jndi namespace:
=======================
Global JNDI Namespace
+ XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+ AllTypes (proxy: $Proxy6 implements
org.jboss.test.testbean2.interfaces.AllTypesHome)
+ UserTransactionSessionFactory (class:
org.jboss.tm.usertx.server.UserTransactionSessionFactoryImpl)
+ RMIXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+ HAPartition (class: org.jnp.interfaces.NamingContext)
| + DefaultPartition (class:
org.jboss.ha.framework.server.HAPartitionImpl)
| + SessionState-'|HASessionState|Default'-Group-0 (class:
org.jboss.ha.framework.server.HAPartitionImpl)
+ topic (class: org.jnp.interfaces.NamingContext)
| + example (class: org.jboss.mq.SpyTopic)
| + testTopic (class: org.jboss.mq.SpyTopic)
| + bob (class: org.jboss.mq.SpyTopic)
+ queue (class: org.jnp.interfaces.NamingContext)
| + D (class: org.jboss.mq.SpyQueue)
| + C (class: org.jboss.mq.SpyQueue)
| + B (class: org.jboss.mq.SpyQueue)
| + A (class: org.jboss.mq.SpyQueue)
| + controlQueue (class: org.jboss.mq.SpyQueue)
| + testQueue (class: org.jboss.mq.SpyQueue)
| + ex (class: org.jboss.mq.SpyQueue)
| + DLQ (class: org.jboss.mq.SpyQueue)
| + F (class: org.jboss.mq.SpyQueue)
| + E (class: org.jboss.mq.SpyQueue)
+ HASessionState (class: org.jnp.interfaces.NamingContext)
| + Default (class:
org.jboss.ha.hasessionstate.server.HASessionStateImpl)
+ ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+ RMIConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+ UserTransaction (class:
org.jboss.tm.usertx.client.ClientUserTransaction)
+ invokers (class: org.jnp.interfaces.NamingContext)
| + ejb (class: org.jnp.interfaces.NamingContext)
| | + mgmt (class: org.jnp.interfaces.NamingContext)
| | | + J2EEDomain (class:
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker)
| | + jmx (class: org.jnp.interfaces.NamingContext)
| | | + ejb (class: org.jnp.interfaces.NamingContext)
| | | | + Adaptor (class:
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker)
| + AllTypes (class:
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker)
+ ejb (class: org.jnp.interfaces.NamingContext)
| + mgmt (class: org.jnp.interfaces.NamingContext)
| | + J2EEDomain (proxy: $Proxy2 implements interface
javax.management.j2ee.ManagementHome,interface javax.ejb.Handle)
| + jmx (class: org.jnp.interfaces.NamingContext)
| | + ejb (class: org.jnp.interfaces.NamingContext)
| | | + Adaptor (proxy: $Proxy4 implements interface
org.jboss.jmx.adaptor.interfaces.AdaptorHome,interface javax.ejb.Handle)
+ UILXAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
+ UILConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
+ jmx:COGITO02:rmi (class: org.jboss.jmx.adaptor.rmi.RMIAdaptorImpl)
=======================
Any change to the JNDI code or deployement code recently?
Cheers,
Sacha
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
