Hi Saminda, all:
> Do we expect Synapse to have a concept of
> MessageExchange / Operation?
> In other words a place to store state and behavior
> along the lines of
> AxisOperation in Axis2?
>
> IMHO prior comes into picture when using <send/> and MEP is
> dynamic. So i guess we need the prior behavior {may be with
> DynamicAxisOperation}. IMO this would quite useful when
> implementing fail over recovery with <send/>.
I'd like to suggest that we focus this week's chat on how Synapse deals
with sending/receiving in various contexts.
In particular:
- Passthrough one-ways (log, xform)
- Passthrough req-resp (Synapse as proxy - both sync and async)
- Fault generation
- More complex MEPs (Synapse as WS-Notification proxy, etc)
- Synapse calling out to other services
- Relationship of MEPs to process and correlation within Synapse
I think we need a cleaner and more comprehensive model, and we should
have use-cases in mind to vet against as we go.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
