Axis1.4 generates empty string namespaces in client request which fails in
Server side resulting Null Pointer Exception
-----------------------------------------------------------------------------------------------------------------------
Key: AXIS-2798
URL: https://issues.apache.org/jira/browse/AXIS-2798
Project: Axis
Issue Type: Bug
Environment: Client -Axis1.4 or lower versions
WebService deployed in XFIRE SOAP Framework on server side
Reporter: Pradeep Selvaraj
I'm writing some code to use the web services exposed by Server with XFire
Framework . I face some problems when I try to use Apache Axis (I use 1.4
version) as the SOAP framework to communicate with server. But when i use XFire
in client side,it works fine. In the SOAP request sent by Axis, I find empty
string as the namespace value for some elements. If I remove those attributes
(xmlns="") manually from all the elements the program works fine. Could you
tell why this could be happening?
I use the following ant task to generate the Java code from WSDL files.
<axis-wsdl2java all="true" deployscope="Application" output="${generated.src}"
verbose="true" url="${wsdl}/Provisioning.wsdl">
</axis-wsdl2java>
Request:
<soapenv:Body>
<GetServiceSettingInfoRequest
xmlns="http://www.xxx.com/webservices/xxx/provisioning/v1_0_types/";>
<accountIdentifier xmlns="">
<account>root</account>
</accountIdentifier>
<serviceTypeCollection xmlns=""
xmlns:ns1="http://www.xxx.com/webservices/xxx/servicetypes/v1_0_types/";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
soapenc:arrayType="ns1:ServiceType[1]" xsi:type="soapenc:Array">
<ns2:serviceType
xmlns:ns2="http://www.xxx.com/webservices/xxx/provisioning/v1_0_types/";>VOICEMAIL_SERVICE</ns2:serviceType>
</serviceTypeCollection>
</GetServiceSettingInfoRequest>
</soapenv:Body>
</soapenv:Envelope>
I get a Null Pointer Exception response from the server
Is there any way i can avoid this empty string namespaces in generated
request?Any configuration needs to be done or what?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
