[jboss-user] [EJB 3.0] - jboss.xml question AS 5

[bdlink]

The following jboss.xml would bind a jndi name under jboss as 4, but does not do so under jboss as 5, even though the dtd would seem to indicate that it is still supported:
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
  |              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |              xsi:schemaLocation="http://www.jboss.org/j2ee/schema
  |                             http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
  |              version="5.0">
  |    <enterprise-beans>
  |       <session>
  |          <ejb-name>TravelAgentBean</ejb-name>
  |          <jndi-name>TravelAgentRemote</jndi-name>
  |       </session>
  |    </enterprise-beans>
  | </jboss>
  | 
Looking at the jmx jndi view, there is a TravelAgentBean in the global context, but no TravelAgentRemote.
Global JNDI Namespace
  | 
  |   +- UserTransactionSessionFactory (proxy: $Proxy93 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
  |   +- jmx (class: org.jnp.interfaces.NamingContext)
  |   |   +- rmi (class: org.jnp.interfaces.NamingContext)
  |   |   |   +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
  |   |   +- invoker (class: org.jnp.interfaces.NamingContext)
  |   |   |   +- RMIAdaptor (proxy: $Proxy94 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
  |   +- TravelAgentBean (class: org.jnp.interfaces.NamingContext)
  |   |   +- remote (class: Proxy for: com.titan.travelagent.TravelAgentRemote)
  |   |   +- remote-com.titan.travelagent.TravelAgentRemote (class: Proxy for: com.titan.travelagent.TravelAgentRemote)
  |   +- queue (class: org.jnp.interfaces.NamingContext)
  |   |   +- DLQ (class: org.jboss.jms.destination.JBossQueue)
  |   |   +- ExpiryQueue (class: org.jboss.jms.destination.JBossQueue)
  |   +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
  |   +- ClusteredConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
  |   +- ClusteredXAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
  |   +- ConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
  |   +- ProfileService (class: AOPProxy$0)
  |   +- console (class: org.jnp.interfaces.NamingContext)
  |   |   +- PluginManager (proxy: $Proxy95 implements interface org.jboss.console.manager.PluginManagerMBean)
  |   +- topic (class: org.jnp.interfaces.NamingContext)
  |   +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
  |   +- persistence.unit:unitName=#titan (class: org.hibernate.impl.SessionFactoryImpl)
  |   +- TomcatAuthenticators (class: java.util.Properties)
  |   +- XAConnectionFactory (class: org.jboss.jms.client.JBossConnectionFactory)
  |   +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
  | 
Using the annotation @jboss.ejb3.annotations.RemoteBinding does work.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196377#4196377

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196377