6 Replies Latest reply on Jan 15, 2006 1:58 PM by Jason Greene

    WS & EJB3

    Stephen Wang Newbie

      I'm not sure I should post my problem here.
      I'm using JBoss Alpha 5, EJB Web Service and EJB3.

      I got a stack overflow exception when deploy certain services.

      That services deals with some Session Beans. That session beans returns certain presentation object which contains some Entity Beans.

      My entity bean is like; say,

      Account.

      Contact (extends Account)

      In Contact, we have reference to both account and contact.

      My guess is, we are having recursive structure on contact. That's why I think we are having stack overflow.

      Can someone help me giving some idea or advice on that?

      --
      Regards;
      Stephen

        • 1. Re: WS & EJB3
          Heiko Braun Novice

          You need to figure out if the problems occurs in the webservice stack or the EJB/Entity part. In the latter case, this forum is probably not the right place.

          Anyway the stacktrace would be useful.

          • 2. Re: WS & EJB3
            Stephen Wang Newbie

            When I looked at the jboss server log, the exceptions come after or at the generation of wsdl of the service.

            Another is, stack over flow and it comes like this;

            at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:460)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:385)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:348)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:158)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:122)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:369)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:348)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:158)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:122)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:487)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:385)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:348)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:158)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:122)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.introspectJavaProperties(SchemaTypeCreator.java:487)
            at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:385)

            and go on.....

            --
            Regards;
            Stephen

            • 3. Re: WS & EJB3
              Stephen Wang Newbie

              this is from jboss service log;

              2006-01-12 11:19:15,031 DEBUG [org.jboss.ws.tools.JavaToWSDL] generate [endpoint=xxxx.xxxx.xxxx. xxxserviceImpl,tnsURI=null,service=null,portType=null]
              2006-01-12 11:19:15,031 DEBUG [org.jboss.ws.tools.JavaToWSDL11] Creating JavaToWSDL11 instance
              2006-01-12 11:19:15,062 DEBUG [org.jboss.ws.jaxrpc.TypeMappingImpl] register: TypeMappingImpl@7705189 [xmlType={xxxx.xxx.xxxx.xxx.xxx.....}Collection,javaType=java.util.Collection,sf=null,df=null]
              2006-01-12 11:19:23,078 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] Setting SocketClientInvoker::enableTcpNoDelay to: true
              2006-01-12 11:19:23,078 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] Setting SocketClientInvoker::timeout to: 600000
              2006-01-12 11:19:23,078 DEBUG [org.jboss.remoting.transport.socket.SocketClientInvoker] connect called for: org.jboss.remoting.transport.socket.SocketClientInvoker@8f7943
              2006-01-12 11:19:23,609 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/jboss/server/default/tmp/deploy/tmp47419XXXXXXX-Service.jar-contents/XXXXXXXXXService.ejb3

              • 4. Re: WS & EJB3
                Heiko Braun Novice

                Are you Using Contact as parameter or return value within the webservice impl.? Can you provide the source code for the webservice and the value objects?

                I could imagine that, if you really have a circular dependency between Account and Contact, schema generation might fail.

                - Circular dependencies are bad anyway
                - If you cant avoid them use a flat DTO within the webservice instead



                • 6. Re: WS & EJB3
                  Jason Greene Master

                  I fixed this issue just recently on friday, so this should be solved now.

                  -Jason