You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2013/05/27 14:35:44 UTC

[jira] [Updated] (GERONIMO-4974) ee apps or other plugins can't contain gbeans

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

Forrest Xia updated GERONIMO-4974:
----------------------------------

    Fix Version/s:     (was: 3.0.1)
                   3.0.2
    
> ee apps or other plugins can't contain gbeans
> ---------------------------------------------
>
>                 Key: GERONIMO-4974
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4974
>             Project: Geronimo
>          Issue Type: Sub-task
>      Security Level: public(Regular issues) 
>          Components: deployment, osgi
>    Affects Versions: 3.0.0
>            Reporter: David Jencks
>             Fix For: 3.0.2
>
>
> right now the deployer adds packages it can detect as used in a gbean to the Import-Packages.  However it never populares Export-Package.  This causes problems if the class is actually in the plugin/bundle we are constructing.  If a bundle contains a class, if it lists the package in Import-Package, it won't satisfy the constraint itself unless the package is also listed in Export-Package.
> So, we need to make the deployer list all the packages contained in the bundle  in Export-Package.  This might be a challenge in case there are embedded jars and a complicated Bundle-Classpath.
> For now the workaround appears to be to move any classes used in gbeans to another bundle rather than packing them in a javaee app.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira