--
View this message in context:
http://www.nabble.com/Webservice-client-sending-null-parameters-to-host-tp15368060p16447092.html
Sent from the cxf-user mailing list archive at Nabble.com.
FYI, the jetty engine is just used for implementing the http transport,
it will not modify any of the Request or Response message.
I think there may be different xml library in the WAR class path and the
in the jetty embedded class path.
Willem
depstei2 wrote:
Hi Dan, thanks for your help,
--
View this message in context:
http://www.nabble.com/Webservice-client-sending-null-parameters-to-host-tp15368060p16424980.html
Sent from the cxf-user mailing list archive at Nabble.com.
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
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));
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
@incubator.apache.org
Sent: Friday, February 8, 2008 10:09:35 PM
Subject: Webservice client sending null parameters to host
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
://www.nabble.com/Webservice-client-sending-null-parameters-to-host-tp15368060p15368060.html
Sent from the cxf-user mailing list archive at Nabble.com.
