Hi,

I am sending an attachment to another system via a SOAP with attachemnt.
However i am using wm 6.1. Still know that it do not support SWA.
I have a service that sends an attachement with SOAP data.
I get a SOAP response as:

 
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="[URL="http://schemas.xmlsoap.org/soap/envelope/"]http://schemas.xmlsoap.org/soap/envelope/[/URL]" xmlns:xsd="[URL="http://www.w3.org/2001/XMLSchema"]http://www.w3.org/2001/XMLSchema[/URL]" xmlns:xsi="<A href="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.NullPointerException</faultstring><detail><ns1:hostname">http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>java.lang.NullPointerException</faultstring><detail><ns1:hostname xmlns:ns1="<A href="http://xml.apache.org/axis/">TWAPP03</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope">http://xml.apache.org/axis/">TWAPP03</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

I think that the data is not going to the service being invoked.

Any suggestions and advice, why?

Many Thanks

So, let me get this straight, you are aware that IS 6.1 (and IS 6.5 for that matter) do not support Soap With Attachment (SWA), (nor Soap with MIME / DIME nor MTOM for that matter) but you are wondering why you get a soap fault when you try to use Soap With Attachment?

I’m not sure, I can help you further. Not supported means, well, not supported. The only way I know to support SWA in IS 6.x is to embed a Glue server and use Glue.

IS 7.1 will support (finally) SWA and MTOM without the need for Glue.

Mark

Hi Mark,

I am not using the option of Soap with attachment, but having a utility service that creates Mime and envelope and http’s

The null pointer exception in the soap fault would suggest that your utility service may not be working. You will have to examine the stacktrace logged on the service provider’s side to determine the root cause.

You shoudl probably need to get the service working with a tool like CrossCheck’s SOAP Sonar Personal Edition and then determine what it would take for IS to create a similar message.