URI/URN soapAction incompatibility with BizTalk receive port Operation Name?

hi,

i'm trying expose a wcf service in biztalk according swedish national standard service definition healtchare interoperability (a wsdl provided, , ran bpel import schemas , orchestration wsdl in biztalk, built , exposed through wcf adapter publishing wizard in bts 2006 r2). 

here part of wsdl. note soapaction below.

<wsdl:binding name="getalltimetypesresponderbinding" type="tns:getalltimetypesresponderinterface">
  <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  <wsdl:operation name="getalltimetypes">
   <soap:operation soapaction="urn:riv:crm:scheduling:getalltimetypesresponder:1:getalltimetypes"/>
   <wsdl:input>
    <soap:header use="literal" message="tns:getalltimetypesrequest" part="logicaladdress"/>
    <soap:body use="literal" parts="parameters"/>
   </wsdl:input>
   <wsdl:output>
    <soap:body use="literal"/>
   </wsdl:output>
  </wsdl:operation>
 </wsdl:binding>

when call wcf service a client, uses soapaction, but i error biztalk can not find right method call in its orchestration for the getalltimetypes service. it seems to compare incoming xml soap element 'soapaction' (see above) attribute name of biztalk receive port operation name (actually, id of receive port, set 'getalltimetypes'). i'm trying to set operation name in biztalk receiveport namespace + method name in wsdl above, but the special characters in namespace aren't allowed, , reveice location fails receive message.

 

as see it, according the ws-i basic profile, both wcf adapter and biztalk violates rule r1127: "a receiver must not rely on value of soapaction http header correctly process message".

my question is:

is there way map incoming uri soapaction to receive port operation name? seems possible using consume web service wizard within biztalk project, i'm not trying consume web service, i'm trying expose orchestration web service (wcf actually). 

i'm thinking custom pipeline, custom wcf adapter, or more simple mechanism i've foreseen.

thanks!

/niklas

ok, tried make bpel import did using richard seroter's article. did not succeed. attribute inability.

i got thinking though , ended @ this: configure orchestration not use tightly bound port rather direct bound port. can set filter property of activating receive shape correspond request message wcf service.

this uncouples operation name biztalk orchestration port.

let me know how goes.

---

//mikael sand (mcts) - http://tinyurl.com/mikaelsand logica sweden

BizTalk Server  >  BizTalk Server General