I'm having a problem with what seems to be an easy task.  Until now, all of
our orchestrations exposed as a web service returned an error description
within its response message when encountered a business exception.

I now need to return a SOAP fault for some of our partners instead.  So, I
created a fault message (system.string), added a fault message to the
operation of my request/response port for my web service.  Easy enough...so 
I
thought.

Well, I'm getting a build error "must receive before sending a fault message
on an implemented port".  I searched BTS2004 documentation, google and this
newsgroup but no luck.  I'm hoping someone can shed a light on this problem.

Thanks in advance

[ Post a follow-up to this message ]

Basically, this means that the compiler is finding that it is possible that
you'll send both the response and the fault.  You need to make it very
explicit that you'll only send the response or the fault.  Two ways to do
this:

1) Use a decide shape to determine if you are sending a fault and send the
fault on one branch and the response on the other.
2) Send your fault from an exception handler block and test to see if the
earlier send happened before sending the fault (I usually do this by using
the succeeded operator and wrapping my send in a transactional scope.

HTH,
Matt


"Hideshi" <Hideshi@discussions.microsoft.com> wrote in message
news:15EC5364-84B1-4E1E-93F6-08AD2500EF67@microsoft.com...
> I'm having a problem with what seems to be an easy task.  Until now, all
> of
> our orchestrations exposed as a web service returned an error description
> within its response message when encountered a business exception.
>
> I now need to return a SOAP fault for some of our partners instead.  So, I
> created a fault message (system.string), added a fault message to the
> operation of my request/response port for my web service.  Easy
> enough...so I
> thought.
>
> Well, I'm getting a build error "must receive before sending a fault
> message
> on an implemented port".  I searched BTS2004 documentation, google and
> this
> newsgroup but no luck.  I'm hoping someone can shed a light on this
> problem.
>
> Thanks in advance

[ Post a follow-up to this message ]

Matt,

Thanks for your reply.  I was taking a long weekend (hope you had a nice one
too).

My orchestration is using #2 via exception handler and I'm sending (or
attempting to) a fault message within the exception block (a logical choice
or I thought).  I'll use the decision block to see if I can at least compile
the thing.

Thanks again

[ Post a follow-up to this message ]