[
https://issues.apache.org/jira/browse/GERONIMO-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006625#comment-13006625
]
Jarek Gawor commented on GERONIMO-5764:
---------------------------------------
I am also in favor of creating a separate bundle deployer. But in my mind that
deployer is totally separate deployer from the existing API (something like a
PluginInstaller GBean?) to avoid all the Configuration/ConfigurationManager API
which should be totally unnecessary in this case.
As to the bundle persistence and updating config.xml. I don't think we have to
do anything to add the bundle names to config.xml. We could just create a GBean
that would maintain a list of bundles to start as an attribute for example. The
bundle deployer would communicate with that GBean and just add a bundle
name/location to the list.
> Support Bundles Deployment in deployment command line
> -----------------------------------------------------
>
> Key: GERONIMO-5764
> URL: https://issues.apache.org/jira/browse/GERONIMO-5764
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: commands
> Affects Versions: 3.0-M2, 3.0
> Reporter: viola.lu
> Priority: Minor
> Fix For: 3.0-M2, 3.0
>
>
> Now we have to deploy a regular bundle via karaf shell: osgi:install
> file:/[bunlde_path], not deployer command line, so open this jira to track
> this feature enablement.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
