There are two possibilities here that I know of. 1) The XML is, in fact, defective. One way to have this problem is to send character data that includes characters outside of the XML 1.0 repertoire. Receiving a completely empty message would have similiar effects.
2) Some other error was thrown in the middle of reading. I recommend SOAPui or WireShark or TCPMon to get an unbiased view of the wire traffic. I would also recommend comparing CXF's messages to those built by a comparable .NET client. On Tue, Sep 16, 2008 at 12:01 PM, M. Hunter <[EMAIL PROTECTED]> wrote: > > I have an application that is attempting to connect to a .NET WCF web service > (hosted on IIS 6, Windows Server 2003) using CXF 2.1-generated client stubs > (through WSDL2Java via a Maven goal). The application is ultimately being > deployed to Tomcat 5.5 and proxies are being stood up via Spring 2.5 when > deployed and through the client-suggested code (e.g., new > <ServiceContractImplementation>(wsdlURL, > SERVICE_NAME).getBasicHttpBinding<ServiceContractName>();) in JUnit tests. > > I was previously having issues connecting the client to the server > (revolving around a 400 error), but have worked around those issues by > changing the binding on the server to use basicHttpBinding (instead of the > default wsHttpBinding). From that change, I was able to get a JUnit test to > connect to the service, provide data (in the form of a complex object), and > receive data (in the form of another complex object). That is, it works, and > I can trace through both the Java code (using Eclipse) and the .NET code and > see that the flow runs as expected. When this gets deployed to Tomcat, > however, I receive an exception: > > org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader, > > with a long stack trace down to the cause: > > javax.xml.stream.XMLStreamException: ParseError [row,col]:[1,1] > > (Sorry about not being able to provide the full output, but I'm in a very > disconnected environment with this application.) > > Doing research on this error, I came across a lot of discussion suggesting > the inclusion of the LoggingFeature (via > @org.apache.cxf.feature.Features(features="org.apache.cxf.feature.LoggingFeature")) > and have done so. The resulting output shows two 'calls' out to the web > service -- i.e., there are two outbound/inbound message traces. The second > inbound message, however, contains an empty payload, and I suspect that that > is the cause of the above error. > > I have scoured Google with as many permutations of my question as I know how > but have had no success with any instruction provided. Are there any > suggestions on how I might get past this issue? > > > Best regards, > > Mat > > -- > View this message in context: > http://www.nabble.com/Questions-re%3A-Error-reading-XMLStreamReader-tp19514863p19514863.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
