[wildfly-dev] update on WildFly NoSQL prototype integration...

[Gunnar Morling]

If OGM should be able to work with connections managed by the container,
some sort of "neutral" SPI is needed IMO. Otherwise we'd have to create
some sort of abstraction *in* OGM to ensure it still can be used in other
environments than WF.

I think best would be to start with a PoC and see things are going to look
like. Then we still can decide where it'd be best located or whether it's
better to avoid re-use and accept some duplication.




2016-05-12 13:24 GMT+02:00 Emmanuel Bernard <emmanuel at hibernate.org>:

>
>
> On 11 mai 2016, at 16:02, Scott Marlow <smarlow at redhat.com> wrote:
>
> >> Hibernate OGM should still be usable without WF; So maybe there should
> >> be a separate project/repo which defines an SPI to obtain/manage
> >> connections and implementations for different NoSQL stores?
> >
> > Excellent suggestion,  perhaps the SPI could be under
> > https://github.com/jboss, which is a common area for sharing.  Possible
> > locations for creating the per NoSQL store implementations could be
> > https://github.com/jboss or https://github.com/hibernate or
> > https://github.com/wildfly.
>
> I'm starting to think that this might be way overkill. If we are creating
> a sub project just to share between 20 and 50 lines of code per provider
> and the overhead code to abstract property configuration to plus OGM and WF
> ones, we are losing more than gaining.
>
> Thoughts ?
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20160512/1d160488/attachment-0001.html