+1 this is doable and will be a good addition. Senaka, you may go ahead and create a JIRA issue for this... :-)
Thanks, Ruwan Indika Kumara wrote: > Hi Paul > > Even with the current implementation as the provider class within a > class mediator is a mediator implementation, within its mediation, it > can access MessageConext and as a reason, it can access registry > resources. Our many of built-in mediators have attributes whose values > are loaded from the registry, current message, etc. Therefore, it is > worth enabling to specify the class mediator properties to be loaded > from the registry. > > Thanks > Indika > > > Paul Fremantle wrote: >> Indika >> >> >>> Properties of the class mediator are only literal values. But for >>> POJOCommand mediator, you can specify the properties to be loaded from >>> synapse message context, axis2 message context ,transport headers or >>> from the registry (you have to use get-property XPath function. Please >>> look at the Synapse_Configuration_Language.html for details about >>> synapse:get-property() and synapse xpath and there are samples using those). >>> >> >> Should we allow Class mediator properties to be loaded from the Registry? >> >> Paul >> >> > > ------------------------------------------------------------------------ > > _______________________________________________ > Esb-java-dev mailing list > [email protected] > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > _______________________________________________ Esb-java-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
