> On 31 May 2016, at 13:33, Galder Zamarreño <gal...@redhat.com> wrote:
>
>> In the past there has been talk of representing a connection to
>> Infinispan using a URL, in particular for HotRod.
>> The Hibernate OGM team is now working on adding NoSQL datasources to
>> WildFly, and they've asked for they should represent connections to
>> various of these.
>
> ^ What's this trying to solve exactly?
The reasoning is as follows in a nutshell.
If Infinispan wants to be treated as a database, it needs to be friendly
towards its client and offer a proper simple access. A driver + a URL scheme is
a common scheme across the RDBMS and NoSQL space these days.
If we have this, then Wildfly users can start separating the data source
configuration from their application deployment like they have been able to for
RDBMSes (or other JCA deployment AFAIR).
The main difference is that we will not return javax.sql.DataSource objects but
the natural native object of the driver. We are setting these approaches in
Wildfly for various NoSQL solutions already. Infinispan is the remaining
outlier.
Emmanuel
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
