On Sun, 2005-11-13 at 09:55 +0000, Anthony Elder wrote:
> Ajith, I don't think you're deeply mislead, it seems there's quite a lot of
> us who can't understand what's wrong with having a Synapse specific message
> which delegates some calls to an Axis2 MessageContext.
>
> interface SynapseMessage {
> String getTo();
> ...
> }
>
> SynapseMessageImpl {
> MessageContext mc;
> public SynapseMessage(MessageContext mc) {this.mc = mc}
> String getTo() { return mc.geTo(); }
> ...
> }
>
> This way the SynapseMessage interface can include methods that are on the
> Axis2 MC and also have additional methods specific to Synapse. I don't see
> this as reinventing Axis2 or wasteful inefficient doubling up of method
> calls,looks more like standard OO design to me.
Ant, shouldn't this be discussed and decided on synapse-dev? As you know
there are quite a few synapse dev types who are not here.
If that decision is made on synapse-dev then there is nothing to discuss
on axis-dev relative to that; Synapse simple encapsulates Axis MC and
goes on.
I agree this is a better model because then we don't have to deal with
how Synapse will work if its handed a different implementation of
SOAPMessageContext. Right now we have a kinda weird model where we have
a SOAPMessageContext concept but it'll only work with the Axis2 MC being
the implementation of that. That's quite misleading to someone coming in
new to Synapse.
Sanjiva.
