[
https://issues.apache.org/jira/browse/GERONIMO-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015581#comment-13015581
]
Jarek Gawor commented on GERONIMO-5861:
---------------------------------------
A few comments:
1) Is there a reason why EBADeploymentManager.updateEBAContent() takes a File
which is converted to an URI in ExtendedDeploymentManager and then converted
back to File in ApplicationGBean? Maybe the API should be just passing an
InputStream around.
2) The FileInputStream in ApplicationGBean is not closed
3) The bundle refresh should only really need to happen if bundle update is
successful. Right not the code is looking up the PackageAdmin service before
the update() call.
4) Will this code be committed to M2 branch?
> Update a bundle within an EBA
> -----------------------------
>
> Key: GERONIMO-5861
> URL: https://issues.apache.org/jira/browse/GERONIMO-5861
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: deployment
> Reporter: Han Hong Fang
> Assignee: Rex Wang
>
> 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 JIRA is for probably required changes to the server's deployer code for
> deploying & managing bundles within or outside of EBAs. And GEP JIRA is here:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-718
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
