[
https://issues.apache.org/jira/browse/GORA-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709858#comment-13709858
]
Scott Stults commented on GORA-257:
-----------------------------------
That's probably the crux of the issue right there: Either massive
reorganization around OSGi, or rebuilding a lot of the OSGi facilities like
dependency import/export, packaging, and registration.
Is there a "lighter" path to OSGi goodness? Maybe Apache Aries?
> Use separate class loaders for each module
> ------------------------------------------
>
> Key: GORA-257
> URL: https://issues.apache.org/jira/browse/GORA-257
> Project: Apache Gora
> Issue Type: Improvement
> Components: gora-core, maven, storage
> Reporter: Scott Stults
> Fix For: 0.5
>
>
> Some modules require conflicting versions of dependent libraries. For
> example, HBase and Solr require conflicting versions of the Zookeeper client
> library. In order to use both stores in the same VM they should each load and
> use their own version of the library. Decoupling the module dependencies from
> the core of Gora allows for independent versioning as well as multiple
> versions.
> To accomplish this, each module needs its own class loader. I think this
> could be done in one of two places: Either Gora core creates the class loader
> and assigns it to a module, or each module starts with a pared-down class
> with no external library dependencies and creates a class loader for the rest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
