Shall we finalize the things that are going to deprecate in ESB 5?
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Hi Amila,
On Fri, Dec 18, 2015 at 11:12 AM, Amila Maha Arachchi
wrote:
> Have you seen *Enqueue* and *RMSequence* mediators being used when
> implementing mediation logics?
>
We have already removed RMSequence mediator in 4.9.0.
I haven't seen anyone using Enqueue Mediator in a
Hi Kasun/Isuru,
Yes, we will verify the NTLM use cases with call mediator blocking behavior
and do more comparison before deprecate in 4.10. Yes, we use same blocking
sender.
Thanks,
Kathees
On Wed, Dec 16, 2015 at 12:05 PM, Cyril Rognon
wrote:
> Hi
>
> DB mediator can
@Kathees : Can we verify NTLM use cases with Call mediator + blocking
behavior? I guess it should work out of box as we also reuse the same
blocking sender code?
For DB* mediators, I guess we can clearly mention in the docs that these
mediators can be only used for very limited kind of DB
Hi
DB mediator can be handy as you said but it is a bad practice to query the
DB right from the Esb. It is against the low coupling principles that makes
integration layer agile and thin and scalable etc.
DSS is setup in two minutes and can fulfill your needs out of the box.
Maybe we
Is it possible to provide sufficient documentation to help the customers
who would be migrating in future.
Thanks,
Yumani
On Wed, Dec 9, 2015 at 1:45 PM, Chanaka Fernando wrote:
> *- Callout mediator :*
> All the callout functionality is supported with 'call' mediator with
On Wed, Dec 9, 2015 at 3:32 PM, Malaka Silva wrote:
> +1 except DBReport/DBLookup mediators
>
> DBReport and DBLookup only offer a very limited set of capabilities. IMO,
for any real integration scenario, we can't use them. :).
> On Wed, Dec 9, 2015 at 2:00 PM, Yumani
In my experience using DB mediator we can cover some of the use cases
using ESB out of the box, which I find very handy.
Also use case of integrating with stored procs can easily covered with
this.
However there are limits like batch update or getting multiple rows.
I guess we can argue both
IMO best option in that case is have connectors supporting different spring
versions, similar to what we are doing for EJBs. Having a mediator will
only limit for single version.
On Thu, Dec 10, 2015 at 11:35 AM, Maheeka Jayasuriya
wrote:
> Hi,
>
> I've observed spring
Hi,
I've observed spring mediator being used extensively in situations where
maintaining the domain model useful (class mediators are the alternative
with a POJO domain model). This allows maintainability and is easily
extensible. However, Spring mediator right now does not explore best of
Spring
10 matches
Mail list logo