4 Replies Latest reply on Apr 10, 2009 12:50 AM by hsiung

    Seam Action not working on Weblogic 10.3

    hsiung

      I let SeamTools 2.1.1 generate a Seam Action and deploy on Weblogic 10.3.
      But I get the following exception. Strangely, a Seam Entity is working correctly.


      javax.naming.NameNotFoundException: While trying to lookup 'serviceRegistration.local' didn't find subcontext 'serviceRegistration'. Resolved ''; remaining name 'serviceRegistration/local'
           at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
           at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
           at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
           at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
           at webloghttp://seamframework.org/Community/SeamUsersForum?showTopicForm=true#ic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
           at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:380)
           at javax.naming.InitialContext.lookup(InitialContext.java:392)




      Any ideas?

        • 1. Re: Seam Action not working on Weblogic 10.3
          hsiung

          I mean JBossTools 3.0

          • 2. Re: Seam Action not working on Weblogic 10.3
            meetoblivion
            • 3. Re: Seam Action not working on Weblogic 10.3
              hsiung

              Thank you. Yes I did. The page is helpful, I did all the stuff it says, but I still get this exception.


              What it strange is that it's very basic. I'm just creating a plain Seam Action without any code of me.


              The Seam action is generated from JBossTools and it doesn't work on weblogic.


              I expected more from a 3.0 version...


              • 4. Re: Seam Action not working on Weblogic 10.3
                hsiung

                i now found a solution to my problem, the following 2 things:


                1) in components.properties:


                jndiPattern=java:comp/env/wsRepository/#{ejbName}/local



                2) in web.xml:


                  <ejb-local-ref>
                    <ejb-ref-name>wsRepository/ServiceRegistrationBean/local</ejb-ref-name>
                    <ejb-ref-type>Session</ejb-ref-type>
                    <local>org.domain.wsrepository.session.ServiceRegistration</local>
                  </ejb-local-ref>     
                



                then the Seam framework in the web container calls the EJB3 correctly.


                Conclusion: JBossTools 3.0 should have generated the correct jndiPattern and the correct ejb-local-ref. It would have all the necessary information. The currently generated jndiPattern simply doesn't work. By the way, in the Seam 2.1.1 jee5 sample the jndiPattern is correct. Why does JBossTools not generate any ejb-local-ref that is obviously needed in EJB3?


                Did I missed something?!