09-23-04 10:51 PM
I might be wrong here but I don`t think what you are trying to achieve
here is possible. Think of how you really would expose a parameterized
orchestration as a web service - you would not have an input recieve
port, as the orchestration expects input from another orchestration..
But - I might be wrong here.. I`ve only worked with calling
parameterized orchestrations from other orchestrations.
If you need to have orchestration 2 as a standalone orchestration
exposed as a web service, why not consume the web service from
orchestration 1?
HTH,
Asbjørn
Guru wrote:
> Hi
>
> I have a orchestration[No 2] with the following details
> One Receive [ Activate= true ] and one Send Shape
> One Input Orchestration message Parameter.
>
> This orchestration will be published as a webservice in the later stage.
> It should work as a standalone orchestration as well.
>
> The above orchestration will be called from another orchestration[No 1
]
> using "Start orchestration" shape
>
> When i try to build the 2nd orchestration with Receive [ Activate= tru
e ] ,
> i get the following build error
> a schedule 'Orchestration2(message )'
> with parameters cannot have an activatable receive
>
> with Receive [ Activate= false ] , i get the following build error
> you must specify at least one already-initialized correlation set for a
> non-activation receive that is on
> a non-selfcorrelating port
>
> How to make this work ?
>
> Regards
> Guru
[ Post a follow-up to this message ]
|