I was able to expose an orchestration as a web service. I have a
Receive-Send port which takes input, passes it to Receive shape, the
orchestration does something and then passes the output to the same port.
This makes sense because it fits the paradigm of web service.

But I am curious about a few things
1. Do we always have to have a two-way port in an orchestration that we want
to expose as a web service?

2. If the answer is No, then how do you configure the Send port? Assume we
have an orchestration with one incoming port and one outgoing port. It is
easy to configure the incoming (receive) port. But how do I configure the
send port? I don't know what URL to specify in SOAP configuration for send
port?

Does this even make sense? AFAIK Web Services are synchronous. So I think it
may not make sense to have a send port.

3. I can think of a 'fire and forget' type of web service to which you just
send message and don't expect a return.

Prash

[ Post a follow-up to this message ]

Can't you use Request - Response receive port for the Orchestration web
service. In this you just have to specify url in the receive port and dont
worry about any send port urls. May be I am wrong.

"Prash" wrote:

> I was able to expose an orchestration as a web service. I have a
> Receive-Send port which takes input, passes it to Receive shape, the
> orchestration does something and then passes the output to the same port.
> This makes sense because it fits the paradigm of web service.
>
> But I am curious about a few things
> 1. Do we always have to have a two-way port in an orchestration that we wa
nt
> to expose as a web service?
>
> 2. If the answer is No, then how do you configure the Send port? Assume we
> have an orchestration with one incoming port and one outgoing port. It is
> easy to configure the incoming (receive) port. But how do I configure the
> send port? I don't know what URL to specify in SOAP configuration for send
> port?
>
> Does this even make sense? AFAIK Web Services are synchronous. So I think 
it
> may not make sense to have a send port.
>
> 3. I can think of a 'fire and forget' type of web service to which you jus
t
> send message and don't expect a return.
>
> Prash
>
>
>

[ Post a follow-up to this message ]

Sujesh,

That is what I am using and it works. In this arrangement, there is just one
port that accepts a request and sends a response. I am wondering how to
manage if you have one port that does only receive and another that does
only send. You can hook the receive port to the web service, but what do you
do with the send port?

Prash


"Sujesh" <Sujesh@discussions.microsoft.com> wrote in message
news:FEAE9150-EE9B-40D3-9A99-E4A5D499B948@microsoft.com...[vbcol=seagreen]
> Can't you use Request - Response receive port for the Orchestration web
> service. In this you just have to specify url in the receive port and dont
> worry about any send port urls. May be I am wrong.
>
> "Prash" wrote:
> 

[ Post a follow-up to this message ]

Sujesh,

That is what I am using and it works. In this arrangement, there is just one
port that accepts a request and sends a response. I am wondering how to
manage if you have one port that does only receive and another that does
only send. You can hook the receive port to the web service, but what do you
do with the send port?

Prash

"Sujesh" <Sujesh@discussions.microsoft.com> wrote in message
news:FEAE9150-EE9B-40D3-9A99-E4A5D499B948@microsoft.com...[vbcol=seagreen]
> Can't you use Request - Response receive port for the Orchestration web
> service. In this you just have to specify url in the receive port and dont
> worry about any send port urls. May be I am wrong.
>
> "Prash" wrote:
> 

[ Post a follow-up to this message ]

Make the send port of the orchestration dynamic and assign the destination
location inside the orchestration.

"Prash" wrote:

> Sujesh,
>
> That is what I am using and it works. In this arrangement, there is just o
ne
> port that accepts a request and sends a response. I am wondering how to
> manage if you have one port that does only receive and another that does
> only send. You can hook the receive port to the web service, but what do y
ou
> do with the send port?
>
> Prash
>
> "Sujesh" <Sujesh@discussions.microsoft.com> wrote in message
> news:FEAE9150-EE9B-40D3-9A99-E4A5D499B948@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]