|
»
»
»
Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (empty parameters)
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (empty parameters)
by SGE0
::
Rate this Message:
Hi,
we are upgrading from Axis/Java 1.4.1. to 1.5.1 and having some problems. We encounter that a passed soapmessage (same that works correctly under 1.4.1): <?xml version='1.0' encoding='utf-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsa:MessageID>urn:uuid:DD04F12C3872B6578F1234360243487</wsa:MessageID> <wsa:Action>urn:upload</wsa:Action> </soapenv:Header> <soapenv:Body> <ns1:upload xmlns:ns1="http://services.test.be"> <ns1:pdfdocument>JVBER...Cg==</ns1:pdfdocument> <ns1:documentURI/Example.pdf</ns1:documentURI> </ns1:upload> </soapenv:Body> </soapenv:Envelope> returns following error: <?xml version='1.0' encoding='utf-8'?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server</faultcode> <faultstring>document is null</faultstring> <detail /> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> At the server side we check if the incoming document is empty and throw the error 'document is null'. Obviously it is not: <ns1:pdfdocument>JVBER...Cg==</ns1:pdfdocument> Any idea what must be changed to the codebase for v1.5.1 to make this work ? Are there any release notes describing the upgrade process from 1.4.1. tot 1.5.1 so we know if something must be changed from our side. S. |
|
|
Re: Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (empty parameters)
by SGE0
::
Rate this Message:
All,
it was a problem at our site so this can be closed.
|
|
|
Re: Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (empty parameters)
by Ellecer Valencia
::
Rate this Message:
Just so your post wouldn't have been a total waste of time, could you
say what was the cause of the problem you were experiencing? It may help someone else who experiences the same issues. On Thu, Nov 5, 2009 at 7:56 PM, SGE0 <stefangeelen@...> wrote: > > All, > > it was a problem at our site so this can be closed. > > SGE0 wrote: >> >> Hi, >> >> we are upgrading from Axis/Java 1.4.1. to 1.5.1 and having some problems. >> >> We encounter that a passed soapmessage (same that works correctly under >> 1.4.1): >> >> <?xml version='1.0' encoding='utf-8'?> >> <soapenv:Envelope >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> >> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> >> >> <wsa:MessageID>urn:uuid:DD04F12C3872B6578F1234360243487</wsa:MessageID> >> <wsa:Action>urn:upload</wsa:Action> >> </soapenv:Header> >> <soapenv:Body> >> <ns1:upload xmlns:ns1="http://services.test.be"> >> <ns1:pdfdocument>JVBER...Cg==</ns1:pdfdocument> >> <ns1:documentURI/Example.pdf</ns1:documentURI> >> </ns1:upload> >> </soapenv:Body> >> </soapenv:Envelope> >> >> returns following error: >> >> >> <?xml version='1.0' encoding='utf-8'?> >> <soapenv:Envelope >> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> >> <soapenv:Body> >> <soapenv:Fault> >> <faultcode>soapenv:Server</faultcode> >> <faultstring>document is null</faultstring> >> <detail /> >> </soapenv:Fault> >> </soapenv:Body> >> </soapenv:Envelope> >> >> At the server side we check if the incoming document is empty and throw >> the error 'document is null'. >> >> Obviously it is not: >> >> <ns1:pdfdocument>JVBER...Cg==</ns1:pdfdocument> >> >> >> Any idea what must be changed to the codebase for v1.5.1 to make this work >> ? >> >> Are there any release notes describing the upgrade process from 1.4.1. tot >> 1.5.1 so we know if something must be changed from our side. >> >> S. >> >> > > -- > View this message in context: http://old.nabble.com/Problem-upgrading-from-Axis2-Java-1.4.1-to-1.5.1-%28empty-parameters%29-tp26200269p26208629.html > Sent from the Axis - User mailing list archive at Nabble.com. > > |
|
|
Re: Problem upgrading from Axis2/Java 1.4.1 to 1.5.1 (empty parameters)
by SGE0
::
Rate this Message:
Hi Ellecer ,
no problem: - In 1.4.1 we modify the wsdl files via our release system (the http:address location is mofied). - In our hurry we forgot to modify this hence the addrress locatoin was pointing to a non existing location) That's way we got the 'null' error. Now this does not explain why in 1.5.1 we do no longer get a soap env header (see example below or one of my other posts). Regards, S.
|
| Free embeddable forum powered by Nabble | Forum Help |
