We're updating the issue view to help you get more done. 

Create a property to look up native nosql connection via JNDI

Description

This will help the integration with WildFly swarm.

An extract form a conversation on HipChat:

[3:43 PM] Scott Marlow: There was a wildfly-swarm user asking how they could use ogm, the answer was to just use it, but still, it was difficult for them.  We recently updated the wildfly-nosql feature packs to not include the native NoSQL drvers, instead, we updated the Swarm NoSQL fractions to expect the application pom.xml to specify the NoSQL driver dependencies (apps bring their own NoSQL driver, the same way that apps bring their own JDBC driver).
[3:44 PM] Scott Marlow: I think that once we integrate OGM + wildfly-nosql, it should be easier for wildfly-swarm users to use ogm
[3:46 PM] Scott Marlow: Swarm is looking to move to use WildFly 11 as its base, around June (which was mentioned in their google groups forum),I'd like to release an initial wildfly-nosql (alpha perhaps) and wildfly-swarm fractions around then (time permitting).
[3:47 PM] Scott Marlow: so that we can start getting community feedback.

Something else to keep in mind:

[4:19 PM] Sanne Grinovero: we could start with JNDI but I had the impression that JNDI would not be available in all server editions, thinking e.g. a slim version of thorntail
[4:20 PM] Sanne Grinovero: but let's just do it to begin with
remember there's a jipijapa adaptor in the OGM tree. Start there to keep it easy?

Environment

None

Status

Assignee

Fabio Massimo Ercoli

Reporter

Davide D'Alto

Labels

None

Worked in

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Community Help Wanted

None

Suitable for new contributors

Yes, likely

Requires Release Note

None

backportDecision

None

backportReEvaluate

None

Fix versions

Priority

Major