geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] [Commented] (GERONIMODEVTOOLS-759) Using the new APIs to manage the bundles status both in GEP and Server side
Date Wed, 24 Aug 2011 14:28:29 GMT


Jarek Gawor commented on GERONIMODEVTOOLS-759:

Again, you CANNOT save bundle ids because you might end up updating / deleting a wrong bundle.
You could re-check a bundle id every time but what's the point of doing that if you can just
as well look it up each time. The problem of changing the bundle symbolic name and version
(without bundle id persistence) is much less severe than deleting a wrong bundle (with bundle
id persistence). 

> Using the new APIs to manage  the bundles status both in GEP and Server side
> ----------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-759
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Improvement
>          Components: eclipse-plugin
>    Affects Versions: 3.0
>         Environment: WinXP sp3 32bit& Win7 64bit, Oracle JDK 1.6, Eclipse3.6SR1&SR2
>            Reporter: Yi Xiao
>            Assignee: Jarek Gawor
>              Labels: OSGI, bundle
>             Fix For: 3.0
>         Attachments: OSGIBundleDeploy.patch, OSGIBundleDeploy_759_persistence.patch,
OSGIBundleDeploy_changeAPI.patch, OSGIBundleDeploy_changeAPI2_759.patch, OSGIBundleDeploy_changePOM_759.patch
> This improvement depends on the server's modules, so, if the server side does not update
timely, it may cause the GEP compile failure!

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


View raw message