5 Replies Latest reply on Mar 2, 2007 6:09 AM by Heiko Braun

    JBossWS 1.2.0.GA

    Kevin Urciolo Newbie

      I installed the JBossWS 1.2.0.GA. It looks ok so far. I see these errors in my logs repeated again and again. However, I am not sure what problems it is causing. I am testing things using jbossws 1.2.0.GA for both the client and server.

      2007-02-28 21:52:46,469 ERROR [STDERR] org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
      2007-02-28 21:52:46,469 ERROR [STDERR] Continuing ...

        • 1. Re: JBossWS 1.2.0.GA
          Kevin Urciolo Newbie

          I failed to mention that I deployed the jdk 1.5 version. I am using JBoss 4.0.5.GA. So I deployed the JBoss 40 version of the SAR.

          • 2. Re: JBossWS 1.2.0.GA
            Kevin Urciolo Newbie

            This showed up sometimes as well... using the exact same request and response.

            2007-02-28 22:55:55,877 ERROR [STDERR] [Fatal Error] :1005:26: XML document structures must start and end within the same entity.
            2007-02-28 22:55:55,878 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception
            2007-02-28 22:55:55,912 ERROR [org.jboss.ws.core.server.AbstractServiceEndpointServlet] Error processing web service request

            • 3. Re: JBossWS 1.2.0.GA
              Heiko Braun Master

              Did you try the samples that ship with 1.2.0? When exactly does this error occur?

              • 4. Re: JBossWS 1.2.0.GA
                Kevin Urciolo Newbie

                I did not try the samples. I upgraded from the version shipping with JBoss 4.0.5.GA. The version included in JBoss 4.0.5.GA worked, but had a problem.

                2007-02-27 22:59:30,052 ERROR [org.jboss.ws.jaxrpc.CallImpl] Call invocation failed with unkown Exception
                javax.xml.rpc.JAXRPCException: Cannot obtain deserializer factory for: [xmlType=
                {http://localhost:8080/xxx/}>XXX,javaType=class com.XXX]
                at org.jboss.ws.soap.SOAPContentElement.getDeserializerFactory(SOAPContentElement.java:421)
                at org.jboss.ws.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:230)
                at org.jboss.ws.binding.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:233)
                at org.jboss.ws.binding.EndpointInvocation.getReturnValue(EndpointInvocation.java:182)

                After I upgraded, this problem went away. However, I ran into this new issue.





                "heiko.braun@jboss.com" wrote:
                Did you try the samples that ship with 1.2.0? When exactly does this error occur?


                • 5. Re: JBossWS 1.2.0.GA
                  Heiko Braun Master

                  If we want to nail it down, we need more information about the request/response, the WSDL, etc.

                  You'll need to verify what request does exactly cause that error.
                  Does happen upon parsing the request or when the response is marshalled?