If I have a need for C# classes that have similar functionality for majority
of the time, I can use inheritance so that I can abstract the most of the
functionality into base class and override some of its methods in derived
classes.

Is there such a thing in orchestration? If so, how do I go about it? If not,
what is the next closest thing that I can use in orchestration?

Thanks.
Raghu/..

[ Post a follow-up to this message ]

Well, one can debate whether inheritance is a good way of achieving reuse,
but...

In the world of orchestrations, you might be best served by relying on
pub/sub.   You can have a "base class" orchestration that contains most of
your reusable functionality -- that publishes messages to the messagebox at
particular points of desired extension, with some content/context in the
messages that allows them to be subscribed to by specific "overrides".

You can also do the "opposite" - you can encapsulate reusable functionality
in orchestrations that are called via the Call Orchestration shape.  (Put
these reusable orchestrations in a common assembly and mark them public.)

Scott Colestock
www.traceofthought.net


"Raghu" <Raghu@Nospam.com> wrote in message
news:ukRcq8iYFHA.2420@TK2MSFTNGP12.phx.gbl...
> If I have a need for C# classes that have similar functionality for
> majority
> of the time, I can use inheritance so that I can abstract the most of the
> functionality into base class and override some of its methods in derived
> classes.
>
> Is there such a thing in orchestration? If so, how do I go about it? If
> not,
> what is the next closest thing that I can use in orchestration?
>
> Thanks.
> Raghu/..
>
>

[ Post a follow-up to this message ]