geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GERONIMO-4972) Nested child configurations from ears don't work well with osgi
Date Wed, 09 May 2012 00:11:50 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks resolved GERONIMO-4972.
------------------------------------

    Resolution: Fixed

We "solved" this by turning an ear into only one bundle.
                
> Nested child configurations from ears don't work well with osgi
> ---------------------------------------------------------------
>
>                 Key: GERONIMO-4972
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4972
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: deployment, osgi
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> Right now we are generating "nested bundles" inside plugins for ear files with web modules.
 These don't quite work.  One code problem is that the SimpleConifgurationManager tries to
start the child bundles before the configuration for the parent/containing bundle is registered,
so a getConfiguration call to find the parent config fails.  This is probably easy to fix.
> However a bigger issue is that there's no way to tell the osgi framework about the nested
bundle.  Three possible solutions:
> 1. stop having nested bundles, just use one bundle per ear.  This is a 1-line change
 in AbstractWebModuleBuilder so I expect to use this until we can actually solve the problem
> 2. modify the pax mvn url handler to deal with urls to nested bundles inside the car.
> 3. modify the ear deployer to create more than one bundle from an ear.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message