geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "viola.lu (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GERONIMO-5786) The double refresh problem with EBAs
Date Wed, 24 Aug 2011 07:33:29 GMT

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

viola.lu closed GERONIMO-5786.
------------------------------


close it.

> The double refresh problem with EBAs
> ------------------------------------
>
>                 Key: GERONIMO-5786
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5786
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: osgi
>    Affects Versions: 3.0
>            Reporter: viola.lu
>            Assignee: David Jencks
>            Priority: Minor
>             Fix For: 3.0
>
>
> - deploy an EBA: A@1.0.0 = WAB@1.0.0 + bundle@1.0.0
> - add bundle v1.0.1 via osgi:install bundle@1.0.1
> My expectation was that if I did osgi:refresh [WAB] it would re-resolve and pick up the
new bundle (1.0.1). Instead, I find that I need to do osgi:refresh TWICE for it to pick up
the new bundle version! 
> If the WAB was deployed as a standalone entity outside EBA, then it takes only one osgi:refresh
for it to pick up the new dependent bundle version...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message