Can you tell us a little more about the message path? How you're
invoking the service? At what stage you create the signature? How you
attach the signature, etc?

Anne

On 6/16/05, Laura Baño <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> Hi there, 
> 
>   
> 
> Some days ago, I sent a mail explaining a problem with axis. The problem is
> the next one: 
> 
>   
> 
> I send a request to a web service 
> 
>   
> 
> <dss:VerifyRequest xmlns:ds="
> http://www.w3.org/2000/09/xmldsig#";   
> xmlns:dss="http://ea.carm.es/schemas/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";
> 
>     xmlns:ns="http://www.openuri.org/";
> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"> 
> 
> <dss:SignatureObject>…</dss:SignatureObject> 
> 
> <dss:InputDocuments> 
> 
>         <dss:Document> 
> 
>                 <dss:XMLData><prueba
> xmlns:ns="http://www.openuri.org/";>prueba</prueba></dss:XMLData> 
> 
>         </dss:Document> 
> 
> </dss:InputDocuments> 
> 
> </dss:VerifyRequest> 
> 
>   
> 
> But, when I receive the request in the web service, I receive: 
> 
>   
> 
> <dss:VerifyRequest 
> xmlns:ds="http://www.w3.org/2000/09/xmldsig#";
> xmlns:dss="http://ea.carm.es/schemas/efirma/oasis-dss-1.0-core-schema-cd-02.xsd";
> 
>     xmlns:ns="http://www.openuri.org/"; 
> xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"> 
> 
> <dss:SignatureObject>…<dss:SignatureObject> 
> 
> <dss:InputDocuments> 
> 
> <dss:Document><dss:XMLData><prueba>prueba</prueba></dss:XMLData>
> 
> </dss:Document> 
> 
> </dss:InputDocuments> 
> 
> </dss:VerifyRequest> 
> 
>   
> 
> So, I wonder if there is some way of preserving the xml data. Is this a bug?
> 
>   
> 
> Thanks in advance. 
> 
>   
> 
> Laura 
> 
>

Reply via email to