Hi all, I'm having this problem after upgrading from axis2 1.1.1 to axis2 1.3
Before for a simple object it returned the following xml - <ns:getAuthXResponse xmlns:ns="http://edge.avaya.com/xsd"> - <ns:return> <errorCode xmlns="http://edge.avaya.com/xsd">0</errorCode> <errorMsg xmlns="http://edge.avaya.com/xsd">Success</errorMsg> </ns:return> </ns:getAuthXResponse> Now it adds more namespace definitions that seem to be incompatible with some of my clients. - <ns:getAuthXResponse xmlns:ns="http://edge.avaya.com/xsd"> - <ns:return xmlns:ax22="http://core.springframework.org/xsd" xmlns:ax23="http://context.springframework.org/xsd" xmlns:ax21="http://beans.springframework.org/xsd" type="com.avaya.edge.ResultBean"> <ns:errorCode>0</ns:errorCode> <ns:errorMsg>Success</ns:errorMsg> </ns:return> </ns:getAuthXResponse> as you will notice that the springframework xmlns are being added to this and the errorCode and errorMsg fields have ns: pre-pended to them. I want to find out why this has changed in axis2 1.3 and is there anyway I can configure it so that those headers dont get sent back and my xml transaction back to the client is exactly the same as what it was with axis2 1.1.1 Please help!! Samir ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
