09-03-04 10:49 PM
I believe there is an understood relationship with the web services receive
and orchestrations that are bound to them where they need to use the pass
through pipeline. So, while I think you could do something with a custom
pipeline and add your own components to it, but you wouldn't want to use the
xml disassembler.
On another note, when you publish the web service, you generally publish a
message type so you won't need to have an xml disassembler in the pipeline.
Matt
"Toni" <tylarinn@cc.hut.fi> wrote in message
news:ulfcyZakEHA.3428@TK2MSFTNGP14.phx.gbl...
> Hello!
>
> I have problems with web services receive location with custom pipeline
> component.
>
> First of all I made very simple custom pipeline with XML disassembler. In
> that project I have my document and envelope schemas. One of each. This
> pipeline works fine with File receive location.
>
> Then I published that same envelope schema from that same assembly with
> Biztalk Web Services Publishing Wizard. Publishing wizard worked fine. WS
> runs in its own apppool and I can send messages to it with my test client.
>
> First Error message in Event Viewer was:
>
> "There was a failure executing the receive pipeline:
> "Pipeline.Project_ReceivePipeline" Source: "mscorlib" Receive Location:
> "/BizTalkWebService/WebService1.asmx" Reason: Cannot find the assembly
> Microsoft.BizTalk.Pipeline.Components, Version=3.0.1.0, Culture=neutral,
> PublicKeyToken=31bf3856ad364e35."
>
> I added the Microsoft.BizTalk.Pipeline.Components.dll from pipeline
projects
> \bin\development -directory to GAC and then I got new error message:
>
> "There was a failure executing the receive pipeline:
> "Pipeline.Project_ReceivePipeline" Source: "XML disassembler" Receive
> Location: "/BizTalkWebService/WebService1.asmx" Reason: Unexpected event
> ("eos") in state "processing_header"."
>
> I tried also to modify the generated Web project.
> (ms-help://BTS_2004/SDK/htm/ebiz_prog_webservices_jbrf.htm Publishing
> envelope schemas)
>
> Same error message again.
>
> What is the solution? Route the message through File Receive Location is
of
> course one. How can I use custom pipeline components in my WS receive
> Locations?
>
> Toni Ylärinne
>
>
>
[ Post a follow-up to this message ]
|