signing message element by id / no namespace

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Stewart Bourke (stewartbourke_nospam_at_eircom_dotnet)
Date: 07/09/04 

Date: Fri, 9 Jul 2004 10:27:04 +0100

wse 1.01, vs.net 2003 c#

IS it possible to sign an element of a soap message using an Id attribute
without prefixing the Id attribute with a namespace. wse seems to call for
a namespace referring to ws-utility, but I need to be able to sign the Id
without the namespace - as the webservice I am consuming will not accept the
Id with a NS prefix:

Currently I have:

    <soap:Header>
      <Operation d3p1:Id="MsgOperation"
xmlns:d3p1="http://schemas.xmlsoap.org/ws/2002/07/utility"
xmlns="http://www.ros.ie/schemas/service/">Inbox/List</Operation>
    </soap:Header>
    <soap:Body wsu:Id="MsgBody"
xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
      <DocumentSearch xmlns="http://www.ros.ie/schemas/inbox/" />
    </soap:Body>

but I need:

    <soap:Header>
      <Operation Id="MsgOperation"
xmlns="http://www.ros.ie/schemas/service/">Inbox/List</Operation>"
    </soap:Header>
    <soap:Body Id="MsgBody" >
      <DocumentSearch xmlns="http://www.ros.ie/schemas/inbox/" />
    </soap:Body>

Thanks,

Stewart Bourke

Relevant Pages

  • Re: signing message element by id / no namespace
    ... I take it that this is not possible with wse... ... > IS it possible to sign an element of a soap message using an Id attribute ... > without prefixing the Id attribute with a namespace. ... > a namespace referring to ws-utility, but I need to be able to sign the Id ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: signing message element by id / no namespace
    ... My idea was to add a 2nd attribute without the namespace. ... Note that WSE will add an wsu:Id automatically to ... SoapEnvelope env = new SoapEnvelope; ... SoapEnvelope response = ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSS Namespace Conflicts between IBM/MS
    ... WSE 2.0 has moved to the official Oasis namespace, the IBM namespace is ... You could always try WSE 1.0. ... > When I change the wsse definition to what IBM is expecting everything works ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSS Namespace Conflicts between IBM/MS
    ... WSE 2.0 has moved to the official Oasis namespace, the IBM namespace is ... You could always try WSE 1.0. ... > When I change the wsse definition to what IBM is expecting everything works ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Cannot Start Custom Token Manager
    ... I don't know if this will solve the entire issue, but the namespace looks ... If you are using the production build of WSE 2.0 then it uses the OASIS ... > namespace WebService1 ... There was an error loading the microsoft.web.services2 configuration ...
    (microsoft.public.dotnet.framework.webservices)