Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Amila Maha Arachchi]

Have you seen *Enqueue* and *RMSequence* mediators being used when
implementing mediation logics?

On Wed, Dec 9, 2015 at 12:11 PM, Kasun Indrasiri  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.
>
> *- 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
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Vidura Gamini Abhaya]

Hi Isuru,

I've used it in a mediation sequence where I use a POJO to generate a
unique customer id given a couple of parameters and there's a checksum
added to the end. I already had written this code and it was quite simple
and straightforward to reuse it with a POJOCommand mediator. I feel the
simplicity of it is a welcome feature, where reading and setting values in
MessageContext is automatically handled for me.

I don't know whether a single usage case is enough to make the case to keep
it. However, if we decide to keep it though, I suggest that we improve the
documentation on it. I had to dig around to find out how the what the
different actions mean. It wasn't clear to me in the docs (I believe most
of the content is carried forward from Syanpse).

Thanks and Regards,

Vidura



On 10 December 2015 at 10:57, Isuru Udana  wrote:

> Hi Kathees,
>
> I think we should do a comparison once more to make sure that we have
> covered everything before removing Callout. NTLM one which Harshana pointed
> out may be due to absence of initClientOptions configuration option.
>
> Hi Vidura,
> Point you raised on the POJOCommand mediator is really interesting. We
> haven't seen any usage of that over years. But now we found at least one
> user who has found it useful. Thanks for pointing that out. So we should
> reconsider how useful it is.
>
> Thanks.
>
>
>
> On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
> wrote:
>
>> +1 to deprecate Callout mediator since we have the Callout mediator
>> functionalities in Call mediator.
>>
>> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
>> wrote:
>>
>>> I've found DBReport / DBLookup to be quite useful for simple DB
>>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>>> limited in it's ability to only being able to return a single row of data,
>>> DB Report mediator is still quite useful in writing to a database,
>>> especially when we use a DB as part of the mediation sequences.
>>>
>>> I also feel it is worth continuing with POJOCommand, as it is the most
>>> simplest way of executing some custom code as part of a sequence. Although
>>> it is possible to do the same with a Class mediator, one doesn't have to
>>> worry about adding the proper jars, working with MessageContext etc. with
>>> the POJOCommand. I think we should retain it for the sake of simplicity of
>>> use.
>>>
>>> I'm +1 to deprecate the rest of the mediators.
>>>
>>> Thanks,
>>>
>>> Vidura
>>>
>>>
>>>
>>> On 9 December 2015 at 12:11, Kasun Indrasiri  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.

 *- 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
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Vidura Gamini Abhaya, Ph.D.
>>> Director of Engineering
>>> M:+94 77 034 7754
>>> E: vid...@wso2.com
>>>
>>> WSO2 Inc. (http://wso2.com)
>>> lean.enterprise.middleware
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Kathees
>> Software Engineer,
>> email: kath...@wso2.com
>> mobile: +94772596173
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vidura Gamini Abhaya, Ph.D.
Director of Engineering
M:+94 77 034 7754
E: vid...@wso2.com

WSO2 Inc. (http://wso2.com)
lean.enterprise.middleware
___

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Viraj Senevirathne]

Hi,

I think we will have to test call mediator in blocking mode for some
different use cases. Then we will have to update Documentation about
blocking capability of call mediator. For example the Call Mediator
Documentation for ESB 4.9.0 [1] does not contain any information about
blocking behavior of the call mediator. I think most of the people do not
know about this feature because of that. In any case we will have to test
blocking behavior more as there are some complains about it.

[1] https://docs.wso2.com/display/ESB490/Call+Mediator
Thank you,

On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
wrote:

> +1 to deprecate Callout mediator since we have the Callout mediator
> functionalities in Call mediator.
>
> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
> wrote:
>
>> I've found DBReport / DBLookup to be quite useful for simple DB
>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>> limited in it's ability to only being able to return a single row of data,
>> DB Report mediator is still quite useful in writing to a database,
>> especially when we use a DB as part of the mediation sequences.
>>
>> I also feel it is worth continuing with POJOCommand, as it is the most
>> simplest way of executing some custom code as part of a sequence. Although
>> it is possible to do the same with a Class mediator, one doesn't have to
>> worry about adding the proper jars, working with MessageContext etc. with
>> the POJOCommand. I think we should retain it for the sake of simplicity of
>> use.
>>
>> I'm +1 to deprecate the rest of the mediators.
>>
>> Thanks,
>>
>> Vidura
>>
>>
>>
>> On 9 December 2015 at 12:11, Kasun Indrasiri  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.
>>>
>>> *- 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
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Vidura Gamini Abhaya, Ph.D.
>> Director of Engineering
>> M:+94 77 034 7754
>> E: vid...@wso2.com
>>
>> WSO2 Inc. (http://wso2.com)
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Viraj Senevirathne
Software Engineer; WSO2, Inc.

Mobile : +94 71 958 0269
Email : vir...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Kathees,

I think we should do a comparison once more to make sure that we have
covered everything before removing Callout. NTLM one which Harshana pointed
out may be due to absence of initClientOptions configuration option.

Hi Vidura,
Point you raised on the POJOCommand mediator is really interesting. We
haven't seen any usage of that over years. But now we found at least one
user who has found it useful. Thanks for pointing that out. So we should
reconsider how useful it is.

Thanks.



On Thu, Dec 10, 2015 at 10:39 AM, Kathees Rajendram 
wrote:

> +1 to deprecate Callout mediator since we have the Callout mediator
> functionalities in Call mediator.
>
> On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
> wrote:
>
>> I've found DBReport / DBLookup to be quite useful for simple DB
>> operations as they are easy to do OOTB. While DB Lookup mediator maybe
>> limited in it's ability to only being able to return a single row of data,
>> DB Report mediator is still quite useful in writing to a database,
>> especially when we use a DB as part of the mediation sequences.
>>
>> I also feel it is worth continuing with POJOCommand, as it is the most
>> simplest way of executing some custom code as part of a sequence. Although
>> it is possible to do the same with a Class mediator, one doesn't have to
>> worry about adding the proper jars, working with MessageContext etc. with
>> the POJOCommand. I think we should retain it for the sake of simplicity of
>> use.
>>
>> I'm +1 to deprecate the rest of the mediators.
>>
>> Thanks,
>>
>> Vidura
>>
>>
>>
>> On 9 December 2015 at 12:11, Kasun Indrasiri  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.
>>>
>>> *- 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
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Vidura Gamini Abhaya, Ph.D.
>> Director of Engineering
>> M:+94 77 034 7754
>> E: vid...@wso2.com
>>
>> WSO2 Inc. (http://wso2.com)
>> lean.enterprise.middleware
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Kathees Rajendram]

+1 to deprecate Callout mediator since we have the Callout mediator
functionalities in Call mediator.

On Thu, Dec 10, 2015 at 1:18 AM, Vidura Gamini Abhaya 
wrote:

> I've found DBReport / DBLookup to be quite useful for simple DB operations
> as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
> ability to only being able to return a single row of data, DB Report
> mediator is still quite useful in writing to a database, especially when we
> use a DB as part of the mediation sequences.
>
> I also feel it is worth continuing with POJOCommand, as it is the most
> simplest way of executing some custom code as part of a sequence. Although
> it is possible to do the same with a Class mediator, one doesn't have to
> worry about adding the proper jars, working with MessageContext etc. with
> the POJOCommand. I think we should retain it for the sake of simplicity of
> use.
>
> I'm +1 to deprecate the rest of the mediators.
>
> Thanks,
>
> Vidura
>
>
>
> On 9 December 2015 at 12:11, Kasun Indrasiri  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.
>>
>> *- 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
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Vidura Gamini Abhaya, Ph.D.
> Director of Engineering
> M:+94 77 034 7754
> E: vid...@wso2.com
>
> WSO2 Inc. (http://wso2.com)
> lean.enterprise.middleware
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Vidura Gamini Abhaya]

I've found DBReport / DBLookup to be quite useful for simple DB operations
as they are easy to do OOTB. While DB Lookup mediator maybe limited in it's
ability to only being able to return a single row of data, DB Report
mediator is still quite useful in writing to a database, especially when we
use a DB as part of the mediation sequences.

I also feel it is worth continuing with POJOCommand, as it is the most
simplest way of executing some custom code as part of a sequence. Although
it is possible to do the same with a Class mediator, one doesn't have to
worry about adding the proper jars, working with MessageContext etc. with
the POJOCommand. I think we should retain it for the sake of simplicity of
use.

I'm +1 to deprecate the rest of the mediators.

Thanks,

Vidura



On 9 December 2015 at 12:11, Kasun Indrasiri  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.
>
> *- 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
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vidura Gamini Abhaya, Ph.D.
Director of Engineering
M:+94 77 034 7754
E: vid...@wso2.com

WSO2 Inc. (http://wso2.com)
lean.enterprise.middleware
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Vanjikumaran Sivajothy]

Is it going to be complete functional Deprecate? If yes, there will be not
forward compatibility during the upgrades.

On Wed, Dec 9, 2015 at 10:23 AM, Isuru Udana  wrote:

> Hi Harshana,
>
> On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin <
> harshan...@gmail.com> wrote:
>
>> 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  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?
>>
>> If that the case, we need to fix that bug.
>
>>
>>
>>> *- 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
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Vanjikumaran Sivajothy
*Associate Technical Lead*
*WSO2 Inc. http://wso2.com *
*USA Mobile **+1-812-361-1286*
*Srilanka Mobile:+94-777-219-209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]


This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Isuru Udana]

Hi Harshana,

On Wed, Dec 9, 2015 at 6:46 PM, Harshana Eranga Martin  wrote:

> 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  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?
>
> If that the case, we need to fix that bug.

>
>
>> *- 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
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Harshana Eranga Martin]

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  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
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] [ESB] Deprecated features in ESB 4.10

[Chanaka Fernando]

*- 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.

It will make a lot of confusion when we have more than one mediators to do
the same thing. Therefore, better to deprecate this mediator.

*- 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)

Even though this mediator has been used by some customers, they are using
that for very limited functionality and we always suggest them to use DSS
as Kasun mentioned. If users really want to connect to a database, they can
easily write a simple class mediator.

*- 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.

+1 for deprecating these mediators.

With the new DAS integration, we can deprecate BAM mediator since we have
the PublishEvent mediator.

On Wed, Dec 9, 2015 at 6:41 AM, Kasun Indrasiri  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.
>
> *- 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/
>



-- 
Thank you and Best Regards,
Chanaka Fernando
Senior Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] [ESB] Deprecated features in ESB 4.10

[Kasun Indrasiri]

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.

*- 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
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture