I'm successfully running a soap transaction, but on the way out, when the code
tries to create the response xml, it's failing with a NullPointerException. I
have debugged through the soap transaction, and have worked out where it is
coming from.
In SOAPService, line 184 there is a call to
m_context.marshalSOAP(rsp.getOutputStream()); This is raising a null pointer
exception. If I debug down further, line 149 of SOAPContext calls
m_sendPayload.marshal(m_marshaller); This goes into the binding code (that I
obviously don't have source of, but can access debug variables in). After
stepping a couple of times in the code I can't see, a NullPointerException is
thrown and I am returned back to the exception block in SOAPService, for the if
(rsp.isCommitted()) { call, with e as a NullPointerException. The cause of
this exception is the exception itself, and there is no stack trace.
I am aware that I have nulls in my object constellation being marshalled, but
they are all marked as optional. Is this part of the problem? It would be
nice (if possible) to get a better error message coming out of the code, with
some idea of which field was in error.
I do have a successful login transaction working, this is the second
transaction in the flow that is failing.
Any ideas anyone?
Cheers,
Tim.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
