Did some monitoring using TCPMon and saw that axis2 was sending the request as multipart. This particular .Net websvc call did not have any attachments and hence did not need to be send as multipart - I think the .Net side service was assuming it would not be multipart. I set MTOM to off in axis2.xml and that particular call worked. I will now try to turn MTOM back on in axis2.xml and try to see if I can set it on and off at the call level.
- Vish. ________________________________ From: Pantvaidya, Vishwajit Sent: Tuesday, December 04, 2007 1:25 PM To: [email protected] Subject: RE: [Axis2] "WstxEOFException: Unexpected EOF in prolog error" while calling .NET2.0 webservice from Axis2 webservice Attaching the wsdl and aar and axis2.xml file for my axis2 service (ECMServiceSoap) and the wsdl for the .NET service (CPMPDFToWord.wsdl). I am running tomcat and have deployed the axis2 1.3 webapp in an exploded format. So my lib folder has axis2 1.3 xerces 2.8.1, xalan 2.7.0, wstx-asl-3.2.1.jar, xml-apis-1.3.03.jar among others. I am using jdk1.5.0. - Vish. ________________________________ From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 04, 2007 7:23 AM To: [email protected] Subject: Re: [Axis2] "WstxEOFException: Unexpected EOF in prolog error" while calling .NET2.0 webservice from Axis2 webservice Please post WSDL also please post location and version-number of your xml parsers such as xerces/jax M-- ----- Original Message ----- From: Pantvaidya, Vishwajit<mailto:[EMAIL PROTECTED]> To: [email protected]<mailto:[email protected]> Sent: Monday, December 03, 2007 11:04 PM Subject: RE: [Axis2] "WstxEOFException: Unexpected EOF in prolog error" while calling .NET2.0 webservice from Axis2 webservice I tried calling the .NET service with a coded Axis2 client that does not use the stub code I generated from the .NET wsdl earlier (code is enclosed at end of this posting) - but I get same exception. However when I try calling the .NET service from some UI based client like SoapUI (that is independent of axis) the call to the .NET service works. So I presume there is something wrong in the way in the way my client code is invoking the .NET service. Tomorrow I will try seeing the messages with soapmonitor. String pingURL = "http://192.168.254.151/SCPMPDFToWord/Services/CPMPDFToWord.asmx";; Options options = new Options(); options.setTo(new EndpointReference(pingURL)); String methodName = "SetWorkingFolder"; String methodNameSpaceURI = "http://ws.selectica.com/ecm1/";; OMFactory fac = OMAbstractFactory.getOMFactory(); OMNamespace ns = fac.createOMNamespace(methodNameSpaceURI, "ns1"); OMElement payload = fac.createOMElement(methodName, ns); OMElement value = fac.createOMElement("ClientWorkingFolderOnServer", ns); value.addChild(fac.createOMText(value, clientWorkingFolderOnServer)); payload.addChild(value); ServiceClient client = new ServiceClient(); client.setOptions(options); OMElement result = client.sendReceive(payload); ________________________________ From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED] Sent: Monday, December 03, 2007 6:09 PM To: [email protected] Subject: [Axis2] "WstxEOFException: Unexpected EOF in prolog error" while calling .NET2.0 webservice from Axis2 webservice I am using Axis1.3 and have deployed an Axis2 webservice which calls a .NET2.0 webservice. I got the wsdl for the .NET service and used wsdl2java to generate the client code (stub) for calling it. I am calling that stub from my deployed axis2 service. This stub call returns the following exception: Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661) at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134) at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:153) Any idea what this signifies? To me it seems like there is no reply from the .NET side. - Vish.
