[
https://issues.apache.org/jira/browse/OPENEJB-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated OPENEJB-1322:
---------------------------------
Attachment: 0001-module-parent-isstandalone-refactor.patch
0001-module-parent-isstandalone-refactor.patch
1st try to add AppModule reference to module to provide the standalone state.
There are 2 ways to do this:
1, Add appmodule to constructor of module classes.
2, Add a setParent(AppModule app) to module classes.
#1 need to change a lot of existing client code because the api changes. But
I think it's natural way to force the client side set a immutable parent
explicitly.
#2 is to add a mutable appModule field for Module classes but will keep the
existing code happy.
This patch is using #1 way. Please suggest.
> BundleFinderFactory needs a better way to filter scans
> ------------------------------------------------------
>
> Key: OPENEJB-1322
> URL: https://issues.apache.org/jira/browse/OPENEJB-1322
> Project: OpenEJB
> Issue Type: Bug
> Components: osgi
> Affects Versions: 4.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 4.0
>
> Attachments: 0001-module-parent-isstandalone-refactor.patch,
> 0001-module-parent-isstandalone-refactor.patch
>
>
> BundleFinderFactory needs to be able to look at anything in the bundle
> classpath of a single module such as a war but needs to be able to look in
> only one module at a time in an ear where everything is mushed together into
> one bundle. I'm not sure there is currently enough information in
> DeploymentModule to adequately do this.
> Right now we need to look at all of a war file with ejbs inside. I've hacked
> up something that doesn't install a filter if the jarLocation ends in ".war".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
