7 Replies Latest reply on Apr 26, 2006 8:54 AM by kalaiselvane

    migration from websphere to jboss

    kalaiselvane

      hello,
      while migrating from websphere to jboss,i have some problem.

      i have configured the login module in login-config file.. it is working fine ...

      in this project i m using both stateless sesion facade and entity... here m using entity as local for the session...

      it enters into the session facade but not into entity...it creates the entity local home object...but it is giving remote object as null...

      i guess the problem is due the <ejb-link> tag used in ejb -jar.xml... i dont know how to configure the same in jboss.xml...

      i tried with giving <local -jndi -name> in jboss.xml but still i m not able to link my session with entity....


      for ur reference i m giving my portion of ejb-jar.xml and jboss.xml

      IN ejb-jar.xml


      <ejb-name>LoginSession</ejb-name>
      com.ilink.ptrack.comps.loginSessionFacade.LoginSessionHome
      com.ilink.ptrack.comps.loginSessionFacade.LoginSession
      <ejb-class>com.ilink.ptrack.comps.loginSessionFacade.LoginSessionBean</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>
      <ejb-local-ref id="EJBLocalRef_1121842413218">
      <ejb-ref-name>ejb/LoginEJB</ejb-ref-name>
      <ejb-ref-type>Entity</ejb-ref-type>
      <local-home>com.ilink.ptrack.comps.login.ejb.LoginEJBLocalHome</local-home>
      com.ilink.ptrack.comps.login.ejb.LoginEJBLocal
      <ejb-link>LoginEJB</ejb-link>
      </ejb-local-ref>



      IN jboss.xml


      <ejb-name>LoginSession</ejb-name>
      <jndi-name>ejb/com/ilink/ptrack/comps/loginSessionFacade/LoginSessionHome</jndi-name>
      <local-jndi-name>com/ilink/ptrack/comps/login/ejb/LoginEJBHome</local-jndi-name>



      please check this and help me...

      i m in dare need of the solution...

      thanks ,
      kalai.

        • 1. Re: migration from websphere to jboss
          kalaiselvane

          hello,

          have you understand my query???

          please give me some suggessions


          thanks

          • 2. Re: migration from websphere to jboss
            mlybarger

            kalai,

            it's truely a bit challenging to piece through the words and make sense of your problem ( especially with sentences like: "have you understand my query??? " ), but it seems that you have a stateless session bean that is not able to access another bean in the same jar file correct? this exact same deployment descript (w/o jboss-ejb-jar.xml) was used on WAS?

            here's my suggestion. if you're not using xdoclet to manage deployment descriptors, you need to be. if you're using ejb without xdoclet you're really asking for troubles.

            btw, you're jndi names are questionable. why does this LoginSessionHome have ejb/com/ilink whereas the other is just com/ilink?

            <jndi-name>ejb/com/ilink/ptrack/comps/loginSessionFacade/LoginSessionHome</jndi-name>
            <local-jndi-name>com/ilink/ptrack/comps/login/ejb/LoginEJBHome</local-jndi-name>

            • 3. Re: migration from websphere to jboss
              kalaiselvane

              mlybarger,

              thanks for your suggestions...

              yea i m using the same ejb-jar.xml for WAS...it is working fine in WAS...

              sorry mlybarger its my mistake... later i came to know that jboss.xml is optional...

              since,i m very new to jboss...could you tel me how to use xdoclet to manage deployment descriptors...

              please do send me some examples...

              thanks,
              kalai.

              • 4. Re: migration from websphere to jboss
                kalaiselvane

                mlybarger,

                please send me how to acess BMP entity bean from stateless session bean with the use of xdoclet..

                thanks,
                kalai.

                • 5. Re: migration from websphere to jboss
                  mlybarger

                  i'm sorry, you'll have to read xdoclet's documentation for that one.

                  • 6. Re: migration from websphere to jboss
                    kalaiselvane

                    mlybarger,

                    ok no problem....

                    i have one more doubt...




                    ***********

                    I have one stateless session bean which invokes an entity bean locally.

                    In my case session bean is invoked remotely and is working fine...but the problem comes when i invoke the entity bean.it is creating the home object of entity bean.But when i create the localinterface object ie home.create(),its returning null...why is it so??

                    here is my code snippet from session bean(stateless)

                    Context context = new InitialContext();
                    Object o = context.lookup("java:comp/env/ejb/LoginEJB");
                    home = (LoginEJBLocalHome)PortableRemoteObject.narrow(o, LoginEJBLocalHome.class);//returns home object
                    LoginEJBLocal localhome = home.create();///problem occurs here.localhome is null.
                    ..........
                    ,............

                    ************


                    this was my only problem while deploying the same application in jboss....

                    i want to know ,to solve this problem , is it mandatory to use xdoclet?

                    why i want to know is,if i use xdoclet,i have to change my ejb coding part ....(it is a big application)

                    but the same application working fine in WEBSPHERE....

                    m now in full of confusion.... i guess ur suggestion wil give me better solution to solve this problem..
                    PLEASE HELP ME.....


                    thanks,
                    kalai



                    • 7. Re: migration from websphere to jboss
                      kalaiselvane

                      hello,

                      please help me mlybarger...



                      thanks,
                      kalai.