geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <>
Subject [jira] Commented: (GERONIMO-5761) map the bundle resolved state to configuration load status
Date Mon, 07 Mar 2011 02:24:59 GMT


Ivan commented on GERONIMO-5761:

Attached the two updated files, DependencyManager and ConfigurationExtender, now the appclient
should work well, I could run the appname case in our testsuite.
Based on ours and OSGi implementations, RESOLVED events are not delivered in our expected
order, actually, from the JavaDoc, there is no guarantee for it. Also, while trying to resolve
the bundle using bundle.loadClass or packageAdmin, OSGi framework will try to resolve bundles
as many as possible (Guess that it is implementation depends). Sometimes, the child car bundle
would be resolved before its dependent bundles, if no implicit import packages from that bunde
is used. Now, I only trigger the resolved action after all the required bundles are installed,
also an EventListener is added in the ConfigurationExtender. I am thinking that since the
classloader arch in OSGi is not parent-child, maybe we could try to change our dependency
mechanism to other ways.  

> map the bundle resolved state to configuration load status
> ----------------------------------------------------------
>                 Key: GERONIMO-5761
>                 URL:
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 3.0
>            Reporter: Ivan
>            Assignee: Ivan
>         Attachments:,, GERONIMO-5761-02.patch,
> Will provide a proposed patch later.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message