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,
You were right about the qualified vs unqualified issue. The weird thing
is, if I deploy in tomcat or jetty as a WAR it works fine, but if I deploy
in jetty embedded it fails. The message being sent was this:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<ns2:createPersonTypeInfo
xmlns:ns2="http://myNamespace";>
<personTypeInfo name="PersonType1">
and it causes null parameters, so using soap UI I changed the message by
adding a namespace prefix:
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";>
<soap:Body>
<ns2:createPersonTypeInfo
xmlns:ns2="http://myNamespace";>
<ns2:personTypeInfo name="PersonType1">
and it worked.
I then removed @XmlRootElement from my PersonTypeInfo class and it works
without using the namespace prefix. I wonder why jetty embedded is causing
problems!
Thanks again,
-Daniel
dkulp wrote:
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
