I'm pretty sure that if your hitting this, the soap message is invalid for the service. Usually, it's one of two things:
1) A qualified vs unqualified issue. The elements are coming in non-qulalified when the service is expecting qualified or vice-versa. 2) The elements are coming in the wrong order. I think one of the perl soap toolkits does this sometimes. In anycase, a testcase would be a big help. Dan On Tuesday 01 April 2008, depstei2 wrote: > I am getting the same error, and after debugging I have come to the > same piece of code in DocLiteralInInterceptor. Has anyone come up > with a solution? > > Mayank Mishra-2 wrote: > > G'day all, > > > > I faced the same problem using JAXB binding, I debuged it, > > > > The code in method getPara() of DocLiteralInInterceptor class > > > > parameters.put(part, null); > > <<< > > > > puts null parameters in the MessageContentsLists instance. > > > > replacing it with, > > > > <<< > > parameters.put(part, dr.read(part, xmlReader)); > > > > > > results in right behavior. > > > > I may be wrong, but sharing my own experience with you all. > > > > With Regards, > > Mayank > > > > Daniel Kulp wrote: > >> Any chance you can send a sample project that shows the problem? > >> Kind of hard to diagnos this without more details. What version > >> of CXF? Code first/wsdl first? Can I see the wsdl? Can you > >> capture the soap message? JAXB/Aegis? etc.... > >> > >> > >> > >> Dan > >> > >> On Friday 08 February 2008, mrsv wrote: > >>> I have a cxf webservice and a client generated using wsdl2java. > >>> When the client tries to contact the service the parameters are > >>> being null. I am unable to figure out the reason.Tried including > >>> all the jars from cxf. > >>> > >>> Any answers are appreciated. > >>> > >>> Thanks -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
