-
1. Re: Couchbase data source configuration in WildFly
jesper.pedersen Nov 9, 2015 8:08 AM (in response to arungupta)The :datasources: is a JDBC based subsystem backed by a JCA container; IronJacamar.org in this case.
Couchbase uses a proprietary API, so you would need to implement a :couchbase: subsystem that exposes the user API and management API that makes sense.
Alternative, you could try and use a JDBC driver - like daschl/couchbase-jdbc-driver · GitHub - for Couchbase, but your mileage may vary.
HTH
-
2. Re: Couchbase data source configuration in WildFly
smarlow Nov 9, 2015 8:43 AM (in response to arungupta)You may also want to follow this prototype https://github.com/scottmarlow/wildfly/tree/nosql-dev5, which is targeted at a future WildFly release. The idea is to expose NoSQL (client driver) subsystems that manage access to the NoSQL server(s). We will do a few NoSQL database subsystems (MongoDB + Cassandra + JDG) and see how popular the idea is. We hope to have a WildFly pull request based on a nosql-devN topic branch.
-
3. Re: Couchbase data source configuration in WildFly
arungupta Nov 14, 2015 3:06 PM (in response to jesper.pedersen)Jesper,
There are no releases for this driver and the workspace is not even building at this time. Once that is resolved, can NoSQL database be configured like any other JDBC resource?
-
4. Re: Couchbase data source configuration in WildFly
arungupta Nov 14, 2015 3:07 PM (in response to smarlow)Scott,
Which exact module am I looking at? Is there any configuration option that I need to look at?
Arun
-
5. Re: Couchbase data source configuration in WildFly
jesper.pedersen Nov 24, 2015 9:30 AM (in response to arungupta)Each NoSQL implementation will requires its own integration - likely even at version level, since their API changes.
So no, it won't be like a JDBC integration (e.g. :datasources:).