Arun Gupta wrote:
> For oneway tests, Packet.getMessage() returns null and thus
> SEIInvokerPipe is throwing an NPE as shown:
Thanks. But I think we need a test case for this. SEIInvokerPipe line 75
is looking at the request message, not response. Even for one way tests
we do expect a request message to be there.
So someone (encoder?) must be incorrectly handling the request message,
but I can't spot anything obvious from the source code.
> java.lang.NullPointerException
> at
> com.sun.xml.ws.server.sei.SEIInvokerPipe.process(SEIInvokerPipe.java:75)
> at
> com.sun.xml.ws.addressing.jaxws.WsaServerPipe.process(WsaServerPipe.java:75)
> at
> com.sun.xml.ws.server.WSEndpointImpl$1.process(WSEndpointImpl.java:102)
> at
> com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:99)
> at
> com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:155)
> at
> com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:77)
> at
> com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:163)
> at
> com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:47)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>
> Even the WS-A pipe (which is before SeiInvokerPipe) gets the message as
> null.
>
> Any ideas ?
>
> -Arun
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com