Hi,
I have been doing a direct port binding with the message box. But if I do
this the orchestration reads the message over and over again. I understand
this is a problem with the direct port binding. Can someone suggest how to
get over this?

The use of direct port binding with teh message box is something I can't do
away with.

Thanks and Regards,
Sovon.

[ Post a follow-up to this message ]

Okay friends,
I figured it out.

What I was doing is like this.

1. I had a file adapter from which I am reading a file.
2. This file adapter was being used by orchestration 1. Which subscribes for
message type M1.
3. This message was being used but not transformed by orchestration 1. It
wrote back the message M1 to message box for Orchestration 2 to subscribe it
.
4. Here is the flaw. Now this newly written message M1 is getting subscribed
by Orchestration 1 as well as 2. So we were geting multiple instances.

Hope this would help others.

Regards,
Sovon

"Sovon" wrote:

> Hi,
> I have been doing a direct port binding with the message box. But if I do
> this the orchestration reads the message over and over again. I understand
> this is a problem with the direct port binding. Can someone suggest how to
> get over this?
>
> The use of direct port binding with teh message box is something I can't d
o
> away with.
>
> Thanks and Regards,
> Sovon.

[ Post a follow-up to this message ]

Closing as the problem is resolved.

Thanks,
MRoze

This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team

--------------------[vbcol=seagreen] 
for[vbcol=seagreen] 
it.[vbcol=seagreen] 
subscribed[vbcol=seagreen] 
do[vbcol=seagreen] 
understand[vbcol=seagreen] 
to[vbcol=seagreen] 
can't do[vbcol=seagreen] 

[ Post a follow-up to this message ]