[ 
https://issues.apache.org/jira/browse/MYFACES-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846515#action_12846515
 ] 

Werner Punz commented on MYFACES-2290:
--------------------------------------

Leonardo, as an outsider on the OSGI thing, we route already everything through 
our shared ClassUtils.forName.
I added a pluggable loading architecture to that one to bypass the classloader 
issues in web containers, you might use
the loader plugin mechanism which allows to plug in other loaders from outside 
at startup (or manually by using the api)
for the OSGI classloading issues as well, because then you can route the 
forName through the OSGI loading mechanism instead of having
a fixed dependency into the context loaders.



> Add OSGi bundle information and bundle classloader / activator
> --------------------------------------------------------------
>
>                 Key: MYFACES-2290
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2290
>             Project: MyFaces Core
>          Issue Type: New Feature
>          Components: General
>    Affects Versions: 1.2.8-SNAPSHOT
>         Environment: OSGi (Equinox, Apache Felix, ...)
>            Reporter: Felix Röthenbacher
>            Assignee: Leonardo Uribe
>            Priority: Critical
>         Attachments: allow-ee6-versioned-apis.diff, 
> MYFACES-2290-no-activator-2.patch, MYFACES-2290-no-activator.patch, 
> myfaces-core.diff.txt, myfaces-shared.diff.txt, 
> myfaces-test-helloworld-osgi-pax-web.zip, 
> myfaces-test-helloworld-osgi-springdm.zip
>
>
> The provided patch will add OSGi information to bundle manifest. A bundle 
> activator class makes the MyFaces framework aware that it is running in a 
> bundle environment. A bundle classloader is used to load classes and 
> resources from the bundle classpath. The patch doesn't require any new 
> runtime dependencies and doesn't affect class loading in a non-OSGi 
> environment. Though, small modifications to classloading were needed. This 
> was mainly replacing Thread.currentThread.getContextClassLoader() with 
> ClassUtils methods.
> To run MyFaces in an OSGi environment both bundles (myfaces-api and 
> myfaces-impl) have to be started in the OSGi container. Additionally, the 
> myfaces-impl bundle has to be made available to myfaces-api. Use a fragment 
> bundle with myfaces-api as Fragment-Host and myfaces-impl as Required-Bundle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to