0 Replies Latest reply on Feb 16, 2004 5:54 PM by Adrian Hallam

    Deploying Remote and Local Stateless Session

    Adrian Hallam Newbie

      Hello,

      I have a Session Bean that I am trying to deploy. The ejb-jar.xml looks like:

      ...

      MyBean
      <display-name>MyBeanEJB</display-name>
      <ejb-name>MyBeanEJB</ejb-name>
      <local-home>me.MyBeanEJBLocalHome</local-home>
      < local >me.MyBeanEJBLocal< /local >
      <remote-home>me.MyBeanEJBHome</remote-home>
      < remote >me.MyBeanEJB< /remote >
      <ejb-class>me.MyBeanEJBBean</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>

      (no spaces in the tags - i put them there to fix presentation on this screen)

      ...
      <method-permission>
      <role-name>admin</role-name>
      <role-name>guest</role-name>

      <ejb-name>MyRoleEJB</ejb-name>
      <method-name>*</method-name>

      </method-permission>
      ...

      jboss.xml looks like:
      ...
      < session >
      <ejb-name>MyBeanEJB</ejb-name>
      <jndi-name>me/MyBeanRemote</jndi-name>
      <local-jndi-name>me/MyBeanLocal</local-jndi-name>
      < /session >


      When I change the local jndi value - I see the change in the jmx-console (so it is seeing my jboss.xml file OK). However, nothing I try will get the Remote JNDI to deploy... If I remove the local jndi line then it deploys under local/MyBeanEJB but still no remote interface.

      I looked through my JNDI tree and noticed that nothing has deployed as both local and remote. Is it possible in 3.2.3 to deploy both local and remote interfaces for the same EJB?

      I have also written the local and remote interfaces to implement my actual Interface. That is,

      public interface MyBeanEJB extends EJBObject, IMyBean
      {
      }

      so that I don't have to put all the methods in both MyBeanEJB and MyBeanEJBLocal. Can this cause a problem with deployment?

      I have a JDBC security realm which is talking to a Unicode MySQL database but I don't think that is related to this problem?!? All of this code/config was working in an earlier version of JBoss.

      Any help, pointers or ideas are greatly appreciated.

      Regs,
      Adrian