[ 
https://issues.apache.org/jira/browse/AXIS2-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238938#comment-17238938
 ] 

Robert Lazarski commented on AXIS2-5988:
----------------------------------------

You don't describe your previous environment or your current environment but 
anyways I am guessing the namespaces are defined in an autogenerated wsdl that 
you can see for your service by clicking on it here:

localhost:8080/axis2/services/listServices

Keep in mind though that there was probably some Jira issue that changed 
behavior, and we only support the latest release.

 

> axis wsdl namespace prefixes are changing in the response
> ---------------------------------------------------------
>
>                 Key: AXIS2-5988
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5988
>             Project: Axis2
>          Issue Type: Bug
>          Components: wsdl
>            Reporter: Sivaramakrishnan Raghavan
>            Priority: Major
>
> ax25 namespace prefix got changed to ax21 prefix.. we would like to know the 
> axis2 behavior causing this:
> Our system was sending a soap response like this until now:
> <soapenv:Body> <ns:Response xmlns:ns="http://com.service/xsd";> <ns:return 
> xmlns:ax25="http://service.com/xsd"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="ax25:Result"> 
> <ax25:returnCode>TEST</ax25:returnCode> </ns:return> </ns:Response> 
> </soapenv:Body>
> Now after deploying to a new environment, It got changed to:
> <soapenv:Body> <ns:Response xmlns:ns="http://com.service/xsd";> <ns:return 
> xmlns:ax21="http://service.com/xsd"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:type="ax21:Result"> 
> <ax21:returnCode>TEST</ax21:returnCode> </ns:return> </ns:Response> 
> </soapenv:Body>



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to