You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 2, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 2, 2023. It is now read-only.
I want starter code that is configured to talk to Cloudant database. This involves grabbing all the ektorp jars and setting up the server.xml with the right features and shared lib definition.
I was trying to stay consistent with Liberty CF on Bluemix. I guess the real problem is with the liberty buildpack in Bluemix. If it detects a Cloudant service is bound to a Liberty application, it will automatically generate a server.xml with couchdb feature and a large set of jars as a shared libraries. If the users packages the official java-cloudant library in their war, it causes class conflicts.
This work was done before java-cloudant library existed. We need to update the liberty buildpack to not do the auto-configuration when the cloudant libs are provided.
The buildpack adding the couchdb feature causes expected results as most users are not using it in their dev environment.
Activity
NottyCode commentedon Jan 11, 2017
Why wouldn't you want to use the java cloudant api?
rvennam commentedon Jan 12, 2017
I was trying to stay consistent with Liberty CF on Bluemix. I guess the real problem is with the liberty buildpack in Bluemix. If it detects a Cloudant service is bound to a Liberty application, it will automatically generate a server.xml with couchdb feature and a large set of jars as a shared libraries. If the users packages the official java-cloudant library in their war, it causes class conflicts.
This work was done before java-cloudant library existed. We need to update the liberty buildpack to not do the auto-configuration when the cloudant libs are provided.
The buildpack adding the couchdb feature causes expected results as most users are not using it in their dev environment.