synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Fremantle" <>
Subject Re: New classes quick comment / suggestion
Date Tue, 09 May 2006 06:33:51 GMT

I'm also completely confused by the changes around context and message.

The original model was this:

SynapseMessage = the message and any context associated with the message
plus a pointer to
SynapseEnvironment = the binding into Axis2 and any global (per-engine)

The proposal that I thought we agreed to on last weeks chat was:

SynapseMessage = The message + context associated with that message +
pointers to both:
SynapseEnvironment = the binding into Axis2 (i.e. a set of static methods if
Java allowed interfaces with static methods)
SynapseContext = the global per-engine context.


On 5/8/06, Glen Daniels <> wrote:
> I don't like the name "SynapseContext" for what really seems to be a
> MessageContext... anyone familiar with the Axis-style model will feel a
> little odd with that name, I think (in other words, SynapseContext feels
> like it should be Synapse-wide).  Can we name that
> SynapseMessageContext, or just org.apache.synapse.MessageContext?
> 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?
> --Glen
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

"Oxygenating the Web Service Platform",

View raw message