chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sascha Homeier (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CMIS-878) Allow loading classes from other OSGi Bundles in OSGi Client Wrapper
Date Mon, 11 May 2015 15:30:00 GMT

    [ https://issues.apache.org/jira/browse/CMIS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538054#comment-14538054
] 

Sascha Homeier edited comment on CMIS-878 at 5/11/15 3:29 PM:
--------------------------------------------------------------

Sounds reasonable. The solution above just helps if using two (or more) different types/classes
of AuthenticationProvider and/or ObjectFactory.
A ManagedServiceFactory (which passes an own instance to every service) also does not help
us here because we only have one SessionFactory service.

Back to ClassLoader ;) ...


was (Author: shomeier):
Sounds reasonable. The solution above just helps if using two (or more) different types/classes
of AuthenticationProvider and/or ObjectFactory.
A ManagedServiceFactory (which passes an own instance to the every service) also does not
help us here because we only have one SessionFactory service.

Back to ClassLoader ;) ...

> 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
>            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)

Mime
View raw message