You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Bryan Field-Elliot <br...@netmeme.org> on 2003/01/16 20:38:19 UTC

Call.invoke deserializer messing up QName namespaces

I'm using Axis 1.0.

When I issue a "Call.invoke()", the response message coming from the
server is being deserialized into a DOM strangely. Namely, it is
declaring a new namespace prefix for QNames, when the QName's namespace
has already been declared in a parent node.

This is a problem because the result messages in question also have
digital signatures, and this namespace remapping of the QNames is
throwing off the digests.

For example, this fragment of a response message from the server:

<samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"><samlp:StatusCode Value="samlp:Success"></samlp:StatusCode></samlp:Status>


is being translated into this by the time Call.invoke() returns:


<samlp:Status><qns:StatusCode Value="qns:Success" xmlns:qns="urn:oasis:names:tc:SAML:1.0:protocol"/></samlp:Status>


Is there a way I can control this behavior?

Thank you,

Bryan

Re: Call.invoke deserializer messing up QName namespaces

Posted by Davanum Srinivas <di...@yahoo.com>.

Bryan,

Does this happen with latest 1.1beta or nightly build as well?

Thanks,
dims

--- Bryan Field-Elliot <br...@netmeme.org> wrote:
> I'm using Axis 1.0.
> 
> When I issue a "Call.invoke()", the response message coming from the
> server is being deserialized into a DOM strangely. Namely, it is
> declaring a new namespace prefix for QNames, when the QName's namespace
> has already been declared in a parent node.
> 
> This is a problem because the result messages in question also have
> digital signatures, and this namespace remapping of the QNames is
> throwing off the digests.
> 
> For example, this fragment of a response message from the server:
> 
> <samlp:Status xmlns:samlp="urn:oasis:names:tc:SAML:1.0:protocol"><samlp:StatusCode
> Value="samlp:Success"></samlp:StatusCode></samlp:Status>
> 
> 
> is being translated into this by the time Call.invoke() returns:
> 
> 
> <samlp:Status><qns:StatusCode Value="qns:Success"
> xmlns:qns="urn:oasis:names:tc:SAML:1.0:protocol"/></samlp:Status>
> 
> 
> Is there a way I can control this behavior?
> 
> Thank you,
> 
> Bryan
> 


=====
Davanum Srinivas - http://xml.apache.org/~dims/

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com