Oh I see. I think it might be better to use the dynamic config model for the moment.
Paul On 7/26/07, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Paul, > > I don't think this will be use full in the cluster scenario if we are using > a registry based resources for all the configuration. But if we do not have > a registry based configuration for a particular element and if that resource > has changed by an administrator then it should be able to notify the > configuration to the other nodes in the cluster as well. > > But obviously this is less important since we always go with the registry > approach. > > Thanks, > Ruwan. > > > On 7/26/07, Paul Fremantle < [EMAIL PROTECTED]> wrote: > > Ruwan > > > > When we renew the mediators (through the cache timeout on the > > registry), remind me how this works? How does it fit with the notify > > you are proposing? > > > > Paul > > > > On 7/26/07, Ruwan Linton <[EMAIL PROTECTED]> wrote: > > > I think this is use full. As Paul suggested we can keep the Mediator > > > interface and derive an another interface from Mediator having the init > and > > > shutdown methods. > > > > > > In addition to that how about having a notify method to change the > Mediator > > > parameters at the runtime. This will be help full when Synapse instances > are > > > running in a cluster and if we want to change the parameters of a set of > > > mediators in the cluster. Or may be in case of a presence of mediator > > > dependency with each other. > > > > > > Thanks, > > > Ruwan > > > > > > > > > On 7/25/07, ant elder <[EMAIL PROTECTED]> wrote: > > > > I think an init method that provided access to the > SynapseConfiguration > > > would be useful, for one thing it would avoid having to have > synchronized > > > code in things like the ScriptMediator (prepareExternalScript method) > and > > > XSLTMediator (in performXLST), at least when not using dynamic entries > > > anyway. And that may squeeze out a bit more performance. > > > > > > > > ...ant > > > > > > > > > > > > > > > > On 7/25/07, Paul Fremantle < [EMAIL PROTECTED] > wrote: > > > > > I haven't really thought properly about shutdown. But I guess when > or > > > > > if we switch configurations dynamically there may be mediators that > > > > > will not be used anymore and we should try to ensure they get > cleaned > > > > > up and GCed. > > > > > > > > > > My real issue right now is the startup tho, because I need to pass > the > > > > > SynapseEnv to a callback class, and I need to pass the SynapseEnv to > > > > > the callback before any messages come through the mediator. > > > > > > > > > > Paul > > > > > > > > > > On 7/25/07, Asankha C. Perera < [EMAIL PROTECTED]> wrote: > > > > > > Paul > > > > > > > > > > > > Paul Fremantle wrote: > > > > > > > I'm looking at interfacing Synapse with a stateful engine. In > other > > > > > > > words, I'd like for my mediator to get notified before any > messages > > > > > > > get passed to it, and when no more messages will be passed to > it. > > > > > > How can one decide that no more messages will be passed to it? is > it > > > > > > when Synapse is shutdown? > > > > > > > PS do we ever use mediator.getType()? > > > > > > Yes, as per the Javadoc, its for logging purposes only > > > > > > > > > > > > asankha > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Paul Fremantle > > > > > Co-Founder and VP of Technical Sales, WSO2 > > > > > OASIS WS-RX TC Co-chair > > > > > > > > > > blog: http://pzf.fremantle.org > > > > > [EMAIL PROTECTED] > > > > > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Ruwan Linton > > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > > > -- > > Paul Fremantle > > Co-Founder and VP of Technical Sales, WSO2 > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Ruwan Linton > http://www.wso2.org - "Oxygenating the Web Services Platform" -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
