Showing results for 
Search instead for 
Did you mean: 

Null pointer exception in findOperationForRequest


Null pointer exception in findOperationForRequest

I have a simple WSDL (see end of post) and when I create a mock service from it and try to invoke the only opertion I get the following exception stack, any ideas what could be causing this ?

SOAP UI seems to happy to create a sample response but it does not make a sample request, just an empty soap body in the envelope.

Mon Sep 01 12:05:18 BST 2008:ERROR:com.eviware.soapui.impl.wsdl.mock.DispatchException: java.lang.NullPointerException
   com.eviware.soapui.impl.wsdl.mock.DispatchException: java.lang.NullPointerException
    at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchMockRequest(
    at com.eviware.soapui.monitor.MockEngine$ServerHandler.handle(
    at org.mortbay.jetty.handler.HandlerWrapper.handle(
    at org.mortbay.jetty.Server.handle(
    at org.mortbay.jetty.HttpConnection.handleRequest(
    at org.mortbay.jetty.HttpConnection$RequestHandler.content(
    at org.mortbay.jetty.HttpParser.parseNext(
    at org.mortbay.jetty.HttpParser.parseAvailable(
    at org.mortbay.jetty.HttpConnection.handle(
    at org.mortbay.thread.BoundedThreadPool$
   Caused by: java.lang.NullPointerException
    at com.eviware.soapui.impl.wsdl.mock.WsdlMockRunner.dispatchMockRequest(
    ... 11 more

The WSDL is shown below


Re: Null pointer exception in findOperationForRequest

Doh, found the issue. My WSDL was incorrect in the message definiton for the input.


This should not contain an xs:element but a wsdl:part

Apart from my dumb mistake I am surprised that XML spy would validate the wsdl.
New Here?
Join us and watch the welcome video: