-
1. Re: JBossWS 1.2.0.GA
greenbean Feb 28, 2007 5:28 PM (in response to greenbean)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
greenbean Feb 28, 2007 5:57 PM (in response to greenbean)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 Mar 1, 2007 4:14 AM (in response to greenbean)Did you try the samples that ship with 1.2.0? When exactly does this error occur?
-
4. Re: JBossWS 1.2.0.GA
greenbean Mar 1, 2007 12:35 PM (in response to greenbean)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 Mar 2, 2007 6:09 AM (in response to greenbean)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?