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
JNX has been properly open source for a little while now, and it'd be good to convert the NoSQL driver to use it.
There'll be some fiddly aspects: JNX has a number of transitive dependencies, and developers who use XPages JEE may also have their own JNX installation. Accordingly, JNX and its dependencies should be hidden inside a bundle and not exposed to the rest of the environment. Tycho will make this a little annoying but not impossible.
Moreover, other parts of the stack may want to use some JNX-exposed capabilities, like access to the statistics store. It would probably make sense to create an API shim layer like NSF ODP uses to paper over the differences and allow a hiding JNX bundle to contribute the API without worry of contamination.
The text was updated successfully, but these errors were encountered:
JNX has been properly open source for a little while now, and it'd be good to convert the NoSQL driver to use it.
There'll be some fiddly aspects: JNX has a number of transitive dependencies, and developers who use XPages JEE may also have their own JNX installation. Accordingly, JNX and its dependencies should be hidden inside a bundle and not exposed to the rest of the environment. Tycho will make this a little annoying but not impossible.
Moreover, other parts of the stack may want to use some JNX-exposed capabilities, like access to the statistics store. It would probably make sense to create an API shim layer like NSF ODP uses to paper over the differences and allow a hiding JNX bundle to contribute the API without worry of contamination.
The text was updated successfully, but these errors were encountered: