Re: New classes quick comment / suggestion

[Asankha C. Perera]

Paul / Glen I'm sorry for any confusion caused.. I agree with the suggestion to rename SynapseContext as SynapseMessageContext, and will do the needful As for the SynapseContext/SynapseMessageContext, SynapseEnvironment and SynapseConfiguration I have currently implemented is as per Sanjiva's comment to the mailing list (copied) below. Lets discuss and decide if this is acceptable to move forward, and change if necessary. asankha - SynapseConfig - contains the model of the definitions & rules to execute - contains named global properties and their values - no xml stuff; that's a way of creating this config - SynapseContext - running context for any message - contains message - contains ref to SynapseConfig - contains ref to SynapseEnvironment - contains named local properties and their values; these props are only good for the current message - property lookup cascades - if its not found here it looks in the parent config .. that way you don't have to worry whether its a local or a global property - SynapseEnvironment - has methods for doing stuff (like sending a message) - is stateless; all those methods take a SynapseContext in - is not used except by programmers implementing mediators - I guess we could just use a set of static methods to achieve this too! Paul Fremantle wrote: Glen 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) context 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. Paul On 5/8/06, Glen Daniels <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]