Hi Kasun, Please see the comments inline.
Thanks and Regards, Harshana -- Harshana Eranga Martin Committer - Eclipse ECF: http://www.eclipse.org/ecf/ Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 On 9 December 2015 at 17:41, Kasun Indrasiri <ka...@wso2.com> wrote: > Shall we deprecate following mediators in 4.10 release. > > *- Callout mediator :* > All the callout functionality is supported with 'call' mediator with > blocking=true. Having two similar mediators will be create a bit of a > confusion. > Can we use the Call mediator with blocking=true instead of Callout mediator for the NTLM scenarios? I have tried a NTLM scenario recently with Call mediator and blocking=true in ESB 4.9.0 but it didn't work while the Callout mediator works fine for the same scenario. I also assumed Call mediator would work but it didn't. Can you please check and verify? > *- DBReport/DBLookup mediator* > These mediators offer very limited functionality and we always recommend > to integrate with databases with the use of DSS (using a separate DSS or > using DSS features inside ESB) > > *- Bean, POJOCommand, Spring* : Rarely used mediators and no active > development happens on these. > *- Router* : Same as filter mediator, so no use of having this. > *- In, Out * : Rarely used and often not required with the new > call/respond mediator approach. > > Any comments on these or any other features that we should deprecate from > 4.10 release? > > Thanks, > Kasun. > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
