[
https://issues.apache.org/jira/browse/MYFACES-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908185#comment-13908185
]
Moritz Bechler commented on MYFACES-3856:
-----------------------------------------
maven-bundle-plugin will generate a package list from the wildcard (only
packages with contents). If those do overlap with packages from other bundles
this will be a mess - if not the .* export should be ok.
The following packages seem to be also required here for session
deserialization to work:
org.apache.myfaces.view,
org.apache.myfaces.view.facelets.el,
org.apache.myfaces.view.facelets.component,
org.apache.myfaces.view.facelets.tag.jsf
What I also use right now:
org.apache.myfaces.view.facelets.tag (MethodRule)
org.apache.myfaces.context (this may be very specific)
> myfaces-bundle OSGI imports/exports
> -----------------------------------
>
> Key: MYFACES-3856
> URL: https://issues.apache.org/jira/browse/MYFACES-3856
> Project: MyFaces Core
> Issue Type: Wish
> Affects Versions: 2.2.0
> Reporter: Moritz Bechler
> Attachments: MYFACES-3856-2.patch, MYFACES-3856.patch
>
>
> The OSGI bundle currently has very restrictive exports. This causes issues in
> our environment (customized WAB, importing myfaces using require bundle). At
> least everything that might need serialization in the session should be made
> accessible. Also the CDI bean classes. It's probably easier to just export
> everything and maybe blacklist some stuff that you really want to hide.
> On another note: the bundle current imports
> javax.persistence;resolution:=optional;version="[1.0.0,2.1)
> JPA 2.1 has been out a while and shouldn't cause issues with the two used
> annotations.
> Suggested patch (exporting everything) attached.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
