Ok. I can see a few scenarios where this might be useful, but in general if there are a well-defined set of XSLTs (e.g. say we are choosing between 10) it would be more efficient to have separate mediators because they will do the initialization and this might include a compilation step for the XSLT.
Paul On Thu, Jan 6, 2011 at 10:03 AM, Supun Kamburugamuva <supu...@gmail.com> wrote: > As an example lets take a XSLT transformation. > > Depending on the message content user may have several XSLT > transformations specified. > > With the current language user has to have several XSLT mediators > refereeing these XSLT's. > > But by calculating the XSLT key dynamically based on the message > content, user can use only one XSLT mediator. > > Thanks, > Supun.. > > On Thu, Jan 6, 2011 at 2:24 PM, Paul Fremantle <pzf...@gmail.com> wrote: >> Can you give an example use-case? >> >> Thanks >> Paul >> >> On Thu, Jan 6, 2011 at 7:18 AM, Ranga Siriwardena <ra...@wso2.com> wrote: >>> Hi All, >>> >>> Currently we are supporting only static registry keys with mediators. >>> For an example, XSLT Mediators only allows static keys when creating >>> the mediator. How about having dynamic keys with these kind of >>> mediators. In that case we can support dynamic keys and with that, >>> user will able to use XPath kind of approach to dynamically generate >>> the key instead of a static key. WDYT? >>> >>> Following is an example for that. >>> >>> <!-- using static key --> >>> <xslt key="xslt-key-req"/> >>> >>> <!-- using Dynamic key --> >>> <xslt key={ } /> >>> >>> If we are supporting this kind of dynamic key approach, what should be >>> the proper way of representing the dynamic key? >>> Thoughts are welcome. >>> >>> Thank You. >>> >>> -- >>> Ranga Siriwardena >>> Software Engineer >>> WSO2 Inc. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org >>> For additional commands, e-mail: dev-h...@synapse.apache.org >>> >>> >> >> >> >> -- >> Paul Fremantle >> Co-Founder and CTO, WSO2 >> Apache Synapse PMC Chair >> OASIS WS-RX TC Co-chair >> >> blog: http://pzf.fremantle.org >> p...@wso2.com >> >> "Oxygenating the Web Service Platform", www.wso2.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org >> For additional commands, e-mail: dev-h...@synapse.apache.org >> >> > > > > -- > Technical Lead, WSO2 Inc > http://wso2.org > supunk.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org > For additional commands, e-mail: dev-h...@synapse.apache.org > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org p...@wso2.com "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org