Viewing the SOAP call with the Web service stage

MrBlack · Post by **MrBlack** » Tue Jul 16, 2013 3:53 pm

Does anyone know how to see the actual SOAP call the web service stage constructs? I'm doing some debugging why I'm getting an error like this:

Code: Select all

com.ascentialsoftware.wsclient.ServiceInvocationException: Service invocation exception: 
	at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1602)
	at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1544)
	at com.ascentialsoftware.wspack.Transformer.process(Transformer.java:104)
	at com.ascentialsoftware.jds.StageFactory.runStage(StageFactory.java:544)
	at com.ascentialsoftware.jds.StageFactory.runTarget(StageFactory.java:348)
Caused by: java.lang.NullPointerException
	at java.io.FilterInputStream.read(FilterInputStream.java:89)
	at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source)
	at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
	at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
	at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationContextImpl.java:242)
	at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538)
	at org.apache.axis.Message.getSOAPEnvelope(Message.java:376)
	at com.ascentialsoftware.wsclient.OperationCall.handleRemoteException(OperationCall.java:366)
	at com.ascentialsoftware.wsclient.OperationCall.invoke(OperationCall.java:274)
	at com.ascentialsoftware.wsclient.WebService.callServiceInternal(WebService.java:1685)
	at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1591)
	... 4 more

ray.wurlod · Post by **ray.wurlod** » Tue Jul 16, 2013 6:42 pm

I've always used a tool such as XMLSpy.

MrBlack · Post by **MrBlack** » Wed Jul 17, 2013 8:45 am

Just so I can mark this topic as resolved the bug with the webservice was a namespace in the XML of my payload. So the XML SOAP object was all correct but then the payload that was being delivered, an XML document, that document need it's namespace declared in it. So the best explanation I can provide is the webservice stage would connect up and start delivering the payload and then the webservice would error out and the stage would capture that error and record it in the log.