[esb-java-user] NPE when using a Spring Mediator

[stlecho]

Asankha,

I've been doing some additional testing and removed the SOAPAction and
Content-Type headers from the HTTP request but this does not solve the
problem.

Information captured from TCPMon:
POST /soap/Spring-Proxy HTTP/1.1
User-Agent: Jakarta Commons-HttpClient/3.0.1
Content-Length: 127
Host: localhost:9290

<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><TestFromWSO2ESBSenderTestCase/></soapenv:Envelope>

Regards, Stefan Lecho.

asankha wrote:
> 
> Hi Ruwan
>> Well, not really. I think you forgot that we did an improvement before 
>> the 1.7 release so that you do not need to specify any outSequence and 
>> it defaults to send the response back to the caller. At the same time 
>> endpoint is optional provided that you do a send in the inSequence 
>> providing the endpoint there if you need to forward the message to an 
>> endpoint.
>>   
> Ok.. you are right.. Looking at the code, the NPE is caused by the line 
> below:
> 
> boolean isFault = synCtx.getEnvelope().getBody().hasFault();
> 
> Stefan, can you send your request to the ESB through TCPMon and capture 
> the message, and share with us?
> 
> asankha
> -- 
> Asankha C. Perera
> 
> WSO2 - http://wso2.org
> http://esbmagic.blogspot.com
> 
> 
> _______________________________________________
> Esb-java-user mailing list
> Esb-java-user at wso2.org
> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
> 
> 

-- 
View this message in context: http://www.nabble.com/NPE-when-using-a-Spring-Mediator-tp19184059p19195531.html
Sent from the WSO2 ESB Users mailing list archive at Nabble.com.