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

David Jencks commented on MYFACES-2976:
---------------------------------------

I added the export for the org.apache.myfaces.config.impl.digester.elements 
because digester wasn't working and I didn't want to investigate why at that 
moment :-).  We might need to do some adjustment of the classloading 
environment for digester if we don't export these classes.  I hope that can be 
made to work, I might have time to investigate more in the next couple days.

> Support hiding myfaces impl classes in osgi, and provide a single osgi bundle 
> for api + impl
> --------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2976
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2976
>             Project: MyFaces Core
>          Issue Type: Improvement
>          Components: Extension Feature
>    Affects Versions: 2.0.3-SNAPSHOT
>            Reporter: David Jencks
>            Assignee: Jakob Korherr
>         Attachments: MYFACES-2976.diff
>
>
> The current osgi solution of using require-bundle between the api and impl 
> jars is generally thought of as osgi worst-practice and just doesn't work 
> with snapshot versions (presumably a bug in the bundle plugin).
> Also this does not easily support hiding the impl classes.
> Geronimo would like to use a single bundle containing both api and impl and 
> hide the impl classes as much as possible.  This requires some slight 
> modifications to the FactoryFinder so that impl classes can be loaded from 
> the same classloader as FactoryFinder if they are not visible to the context 
> class loader.
> I think myfaces would be the best place for this combined bundle but geronimo 
> can build it if necessary.  The FactoryFinder classloader changes are 
> therefore more important.
> I've suggested a module name which maps to the bundle symbolic name well, as 
> this seems to be the preferred maven/osgi strategy at apache.

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