[ https://issues.apache.org/jira/browse/CMIS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563234#comment-14563234 ]
Sascha Homeier commented on CMIS-878: ------------------------------------- Hmm...yes thats also nice. I first had the class loading logic in an own Class in the *.osgi package (where the Activator resides). But this introduced a dependency from SessionFactoryImpl and the Android Client code did not work anymore without also shipping this class from *.osgi package (which seemed weird to me). Thx for your work/expertise. Will take a look at it soon. > Allow loading classes from other OSGi Bundles in OSGi Client Wrapper > -------------------------------------------------------------------- > > Key: CMIS-878 > URL: https://issues.apache.org/jira/browse/CMIS-878 > Project: Chemistry > Issue Type: Improvement > Components: opencmis-client > Affects Versions: OpenCMIS 0.12.0 > Environment: OSGi > Reporter: Sascha Homeier > Assignee: Florian Müller > Priority: Minor > > When using the OpenCMIS OSGi Client Wrapper it is hard to load classes from > other bundles. For example if you specify an own Authentication Provider > class as Session Parameter then the Wrapper will not find this class when it > is located inside another bundle. Same problem should occur when defining an > own Cache. > *1)* > It would be nice if other bundles could register their Classloaders so that > ClassLoaderUtil can use it when trying to load classes. > *2)* > Another simpler option would be to simply add "DynamicImport-Package: *" to > the Manifest of the Wrapper. By doing this the Wrapper will find all classes > which are exported by other bundles. Though this approach feels more like a > hack since it breaks modularity. > What do you think about it? > Cheers > Sascha -- This message was sent by Atlassian JIRA (v6.3.4#6332)