[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13010597#comment-13010597
]
Han Hong Fang commented on GERONIMODEVTOOLS-718:
------------------------------------------------
The solution is to keep the updated bundle only in the geronimo server cache
instead of geronimo server repository. So in following cases the updated bundle
will be lost, and the original bundle included in EBA archive file comes back.
1. Start geronimo server with --clean option
2. Restart EBA application in Admin console -> Application EBAs
BTW, the feature is not enabled by default. User can turn it on/off in server
editor section named "Refresh OSGi bundle within OSGi application".
> Update a bundle within an EBA
> -----------------------------
>
> Key: GERONIMODEVTOOLS-718
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718
> Project: Geronimo-Devtools
> Issue Type: New Feature
> Components: eclipse-plugin
> Affects Versions: 3.0-M2
> Reporter: Jarek Gawor
>
> Some EBAs might be huge and contain many bundles. Right now whenever a bundle
> in a EBA is updated, the entire EBA is re-assembled and re-deployed to the
> server. That of course, can be expensive if the application is big. So it
> would be nice if only the updated bundle was re-deployed to the server.
> This feature will probably require changes to the server's deployer code or
> might need a new set of API for deploying & managing bundles within or
> outside of EBAs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
