Are we sure about this ? I am really -1 on removing custom mediators in general.
For me custom mediators are about providing a reusable way of executing the same stuff again and again (and gives you more power, reusability than scripting) - Granted, they have been used to do connectors work, but is that the only thing they are used for ? Plus say I did create some custom mediators already - they are proven and I need to reuse them. So what happens in I *want* to use a custom mediator in DevS 3.3 and ESB 4.8 - What's my workaround ? Isabelle. __________________________________________________ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ On Nov 7, 2013, at 9:17 PM, Selvaratnam Uthaiyashankar <[email protected]> wrote: > Yes, I think, we discussed about deprecating custom mediators and use only > connectors? Kasun, is that the plan? > > Regards, > Shankar > > On Thursday, November 7, 2013, Kasun Indrasiri wrote: > With the connectors.. we hardly need custom mediators. Isn't it? I guess no > user will try to write mediator factories/serializers and write custom > mediator, when he can do the same thing with templates with zero Java code. :) > > > On Wed, Nov 6, 2013 at 10:17 PM, Sanjiva Weerawarana <[email protected]> wrote: > +1. > > > On Wed, Nov 6, 2013 at 11:39 PM, Harshana Martin <[email protected]> wrote: > Hi All, > > Currently if you include an ESB configuration with elements introduced using > an ESB Custom mediator, ESB Graphical Editor will wipe them out since it > cannot identify the custom elements from it's core model. With ESB Cloud > connector framework in DevS, we have introduced the capability for the editor > to validate configuration elements loaded from extensions to the editor other > than it's core element model. > > With this same concept we can further extend the Graphical editor easily to > support ESB Custom mediators as well by populating the Custom mediators in to > the tool pallet by reading the custom mediator configurations inside the Jar > file. This will allow users to use the Custom mediators as well. > > Since 99% of the use cases won't need a new Custom mediator, we will not add > this feature to DevS 3.3.0 (since it is already feature complete) and > schedule this for DevS 3.4.0. > > WDYT? > > Thanks and Regards, > Harshana > -- > > Harshana Martin > Associate Technical Lead > WSO2 Inc. : http://wso2.com > > Mobile: +94 775 998 115 > Profile: https://www.google.com/profiles/harshana05 > Blog: http://harshana05.blogspot.com > Twitter: http://twitter.com/harshana05 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > > -- > S.Uthaiyashankar > VP Engineering > WSO2 Inc. > http://wso2.com/ - "lean . enterprise . middleware" > > Phone: +94 714897591 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
