You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Rex Wang (JIRA)" <ji...@apache.org> on 2011/06/19 07:53:47 UTC

[jira] [Issue Comment Edited] (GERONIMO-5764) Support Bundles Deployment in deployment command line

    [ https://issues.apache.org/jira/browse/GERONIMO-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051650#comment-13051650 ] 

Rex Wang edited comment on GERONIMO-5764 at 6/19/11 5:53 AM:
-------------------------------------------------------------

Just upload a new patch: GERONIMO-5764-install-bundle.patch
I modified the design as the following:
1. Only one cli is kept. That is:
  deploy install-bundle --inplace --start --startLevel 90 D:\BlueprintSample\SampleBundles\HelloWorld.jar
This cli will install the bundle to osgi framework and record it in the var/config/bundle-records.csv file. If "--start" option is specified, the command uses the OSGi's FrameworkMBean to start the bundle.

2. Use a BundleTracker to track Uninstalled bundles, if the bundle is listed in the bundle-records.csv, the tracker will erase it. That is, user can use the normal osgi uninstall command to uninstall a recorded bundle and its record will be automatically erased in back.

3. Modified the BundleRecorder interface, only one API is exposed: 
 public long recordInstall(File bundleFile, boolean inplace, int startLevel)
So, if GEP want to start/stop a bundle, it could use the OSGi's FrameworkMBean, like what does in install-bundle cli.


-Rex


      was (Author: rwonly):
    Just upload a new patch: GERONIMO-5764-install-bundle.patch
I modified the design as the following:
1. Only one cli is kept. That is:
  deploy install-bundle --inplace --start --startLevel 90 D:\BlueprintSample\SampleBundles\HelloWorld.jar
This cli will install the bundle to osgi framework and record it in the var/config/bundle-records.csv file. 

2. Use a BundleTracker to track Uninstalled bundles, if the bundle is listed in the bundle-records.csv, the tracker will erase it. That is, user can use the normal osgi uninstall command to uninstall a recorded bundle and its record will be automatically erased in back.

3. Modified the BundleRecorder interface, only one API is exposed: 
 public long recordInstall(File bundleFile, boolean inplace, int startLevel)
So, if GEP want to start/stop a bundle, it could use the OSGi's FrameworkMBean, like what does in install-bundle cli.


-Rex

  
> 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, console, deployment
>    Affects Versions: 3.0
>            Reporter: viola.lu
>            Assignee: Rex Wang
>            Priority: Critical
>             Fix For: 3.0
>
>         Attachments: GERONIMO-5764-install-bundle.patch, GERONIMO-5764-record-bundle.patch, GERONIMO-5764.patch
>
>
> 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