i have problem our webservice client. used send data webservice no problem, migrated geronimo weblogic, , ws client stopped work. have investigated data, being sent:
<?xml version='1.0' encoding='utf-8'?><soapenv:envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:header><ns1:logindata xmlns:ns1="http://xxxxxx.xx/xxx/xx/xxxx/webservice/xxxxxx/auction/types" soapenv:mustunderstand="0"><ns1:anonymous>false</ns1:anonymous></ns1:logindata></soapenv:header><soapenv:body><ns1:offerssend xmlns:ns1="http://xxxxxx.xx/xxx/xx/xxxx/webservice/xxxxxx/auction/types"><ns1:http://xxxxxx.xx/xxx/xx/xxxx/webservice/etrace/auction/types>...... http://xxxxxx.xx/xxx/xx/xxxx/webservice/xxxxxx/auction/types>
returned error message is:
soapenv:server.userexception</faultcode><faultstring>org.xml.sax.saxparseexception: <line 1, column 426>: xml-20201: (fatal error) expected name instead of :.</faultstring><detail><ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">xxxx.xxxxxx.xxx</ns1:hostname></detail> i'm curious wrong, axis configuration? possibilities working?
edit: have found problem lies in part:
<ns1:http://xxxxxx.xx/xxx/xx/xxxx/webservice/etrace/auction/types> old working xml looked this:
<ns1:entitydata> but how possible, axis doing call different?
this caused axiom-421. issue occurs axiom versions in combination stax implementations. after migrating geronimo weblogic, stax implementation used application different.
the solution either upgrade newer axiom version or add woodstox application used instead of weblogic's stax implementation.
Comments
Post a Comment