|
Home > Archive > BizTalk Server Orchestration > January 2006 > Calling Webservice problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Calling Webservice problem
|
|
| Anonymous 2006-01-09, 2:54 am |
| Hi,
I just created a biztalk orchestration and deployed it,this publishes the
request schema to biztalk.Next i published it as a webservice.I want to
write a client orchestration which would invoke this orchestration as a
webservice.Now when i add a reference to the webservice it includes the
request schema as 'localhost.Reference.xsd' which is the same as the request
schema which got deployed earlier. Now there when i deploy the client
orchestration 2 schemas get deplpyed to biztalk and i get the error 'More
than one schema deployed when i try to execute the workflow'.Am i doing
anything wrong.How can i stop the 'Reference.xsd' from getting
deployed.Anybody who faced this problem can please help me out.
TIA
| |
|
|
I haven't tried but a suggestion, why don't you refer the Orchestration in
your project and use a call orchestration. Let you know if I try the WebSrvc
approach.
Ren
"Anonymous" wrote:
> Hi,
> I just created a biztalk orchestration and deployed it,this publishes the
> request schema to biztalk.Next i published it as a webservice.I want to
> write a client orchestration which would invoke this orchestration as a
> webservice.Now when i add a reference to the webservice it includes the
> request schema as 'localhost.Reference.xsd' which is the same as the request
> schema which got deployed earlier. Now there when i deploy the client
> orchestration 2 schemas get deplpyed to biztalk and i get the error 'More
> than one schema deployed when i try to execute the workflow'.Am i doing
> anything wrong.How can i stop the 'Reference.xsd' from getting
> deployed.Anybody who faced this problem can please help me out.
>
> TIA
>
>
>
| |
| Matt Milner 2006-01-09, 5:57 pm |
| Why not use direct messaging instead of calling the orchestration through a
service? If you are on the same BizTalk group, this is a more performant
way and easier to program.
Matt
"Ren" <Ren@discussions.microsoft.com> wrote in message
news:52128A4E-6269-4F4A-AA2C-3A6D2A38A5C5@microsoft.com...[vbcol=seagreen]
>
> I haven't tried but a suggestion, why don't you refer the Orchestration in
> your project and use a call orchestration. Let you know if I try the
> WebSrvc
> approach.
>
> Ren
>
>
> "Anonymous" wrote:
>
|
|
|
|
|