geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GERONIMO-6132) Not search wired bundles in bundle classloader by default
Date Fri, 21 Sep 2012 00:12:07 GMT

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

Jarek Gawor updated GERONIMO-6132:
----------------------------------

    Comment: was deleted

(was: I discovered two problems with the current implementation:

1) As introduced as part of this work the following change http://svn.apache.org/viewvc?view=revision&revision=1146683
has a side effect of starting any bundles and not just bundles installed via the install-bundle
function. That means that this code can attempt to start bundles of an OSGi application which
should not start at that time.

2) Since BundleRecorderGBean was updating etc/startup.properties with the installed bundles
that means that "deploy" or "client" tools would start these bundles as well.
)
    
> Not search wired bundles in bundle classloader by default
> ---------------------------------------------------------
>
>                 Key: GERONIMO-6132
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6132
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Jarek Gawor
>             Fix For: 3.0
>
>
> From the testing result, it seems that all the functions works well without searching
wired bundles. Also, considering that all kinds of Java EE applications are installed as one
bundle, including EAR package, it should not an issue for user application to finding the
resources in the same application.
> I am thinking to change the codes in xbean and geronimo-hook, by default, wired bundles
will not be searched.

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

Mime
View raw message