Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 738CD42DC for ; Wed, 13 Jul 2011 09:57:34 +0000 (UTC) Received: (qmail 42246 invoked by uid 500); 13 Jul 2011 09:57:27 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 41756 invoked by uid 500); 13 Jul 2011 09:57:07 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 41741 invoked by uid 99); 13 Jul 2011 09:57:05 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 09:57:05 +0000 X-ASF-Spam-Status: No, hits=2.7 required=5.0 tests=FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of xiaoyijhondevelop@gmail.com designates 209.85.220.182 as permitted sender) Received: from [209.85.220.182] (HELO mail-vx0-f182.google.com) (209.85.220.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jul 2011 09:56:57 +0000 Received: by vxg33 with SMTP id 33so5607977vxg.13 for ; Wed, 13 Jul 2011 02:56:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mzzjJ+QRVtEFO5OWhMmG6Dvxoy+k6n83uHhDlc9b3Ro=; b=VcOG8la9ChlAsCOvzhPXwLxoABjb7ODhO+6HuVCJi24rBynpZGAnSJTqqZ5fEa9j8m E1qhbISuPJ7EI3LY9mnW1W/xznBWKjTbNdX/LwdPAZZkfX82Sfvn57vQfUlyTTanP4I2 wWsM0TxeBQFdkwPxK91WeI+4rBtTko/lO/cGk= MIME-Version: 1.0 Received: by 10.52.25.201 with SMTP id e9mr888865vdg.404.1310550996574; Wed, 13 Jul 2011 02:56:36 -0700 (PDT) Received: by 10.220.185.11 with HTTP; Wed, 13 Jul 2011 02:56:36 -0700 (PDT) In-Reply-To: <1741069705.9147.1310543759905.JavaMail.tomcat@hel.zones.apache.org> References: <15513872.54781295425243278.JavaMail.jira@thor> <1741069705.9147.1310543759905.JavaMail.tomcat@hel.zones.apache.org> Date: Wed, 13 Jul 2011 17:56:36 +0800 Message-ID: Subject: Re: [jira] [Commented] (GERONIMO-5764) Support Bundles Deployment in deployment command line From: Yi Xiao To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=20cf307ca33a9c636e04a7f06e49 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307ca33a9c636e04a7f06e49 Content-Type: text/plain; charset=ISO-8859-1 I thought in the GEP side, can provide two way to resolve the second issue: 1 As Rex mentioned, add a section in GEP's server page to control all the bundles' start level, the default value is startlevel + 10 or higher 2 Provide a menu Item like start, stop module when right click the module in server view, named "change bundle start level" to control the specific bundle's start level. But in this scenario, need to save every bundle's start level in GEP side. On Wed, Jul 13, 2011 at 3:55 PM, Rex Wang (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-5764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064415#comment-13064415] > > Rex Wang commented on GERONIMO-5764: > ------------------------------------ > > fix #1 at revision: 1145896, we won't start the fragment bundle when launch > the framework. > > For #2, I agree with you. Currently we install car's dependent bundles in > car's activator, which is not that osgi-friend. That is, if the recorded > bundle has the same start level with the car, there is no guarantee which > one will start first. This could cause the recorded bundle fail to resolve > and start. I believe setting the startlevel properly can resolve this. > On the other hand, GEP need find a place to record each bundle's start > level, or just by default use the initial bundle startlevel + 10 ? > > -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-install-uninstall-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 > > > -- Best regards! John Xiao --20cf307ca33a9c636e04a7f06e49 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I thought in the GEP side, can provide two way to resolve the second issue:=

1 As Rex mentioned, add a section in GEP's server page to= control all the bundles' start level, the default value is startlevel = + 10 or higher
2 Provide a menu Item like start, stop module when right click the mod= ule in server view, named "change bundle start level" to control = the specific bundle's start level. But in this scenario, need to save e= very bundle's start level in GEP side.=A0

On Wed, Jul 13, 2011 at 3:55 PM, Rex Wang (J= IRA) <jira@apache.o= rg> wrote:

=A0 =A0[ https://issu= es.apache.org/jira/browse/GERONIMO-5764?page=3Dcom.atlassian.jira.plugin.sy= stem.issuetabpanels:comment-tabpanel&focusedCommentId=3D13064415#commen= t-13064415 ]

Rex Wang commented on GERONIMO-5764:
------------------------------------

fix #1 at revision: 1145896, we won't start the fragment bundle w= hen launch the framework.

For #2, I agree with you. Currently we install car's dependent bundles = in car's activator, which is not that osgi-friend. That is, if the reco= rded bundle has the same start level with the car, there is no guarantee wh= ich one will start first. This could cause the recorded bundle fail to reso= lve and start. I believe setting the startlevel properly can resolve this.<= br> On the other hand, GEP need find a place to record each bundle's start = level, or just by default use the initial bundle startlevel + 10 ?

-Rex

> Support Bundles Deployment in deployment command line
> -----------------------------------------------------
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: GERONIMO-5764
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/= jira/browse/GERONIMO-5764
> =A0 =A0 =A0 =A0 =A0 =A0 Project: Geronimo
> =A0 =A0 =A0 =A0 =A0Issue Type: New Feature
> =A0 =A0 =A0Security Level: public(Regular issues)
> =A0 =A0 =A0 =A0 =A0Components: commands, console, deployment
> =A0 =A0Affects Versions: 3.0
> =A0 =A0 =A0 =A0 =A0 =A0Reporter: viola.lu
> =A0 =A0 =A0 =A0 =A0 =A0Assignee: Rex Wang
> =A0 =A0 =A0 =A0 =A0 =A0Priority: Critical
> =A0 =A0 =A0 =A0 =A0 =A0 Fix For: 3.0
>
> =A0 =A0 =A0 =A0 Attachments: GERONIMO-5764-install-bundle.patch, GERON= IMO-5764-install-uninstall-bundle.patch, GERONIMO-5764-record-bundle.patch,= GERONIMO-5764.patch
>
>
> Now we have to deploy a regular bundle via karaf shell: osgi:install f= ile:/[bunlde_path], not deployer command line, so open this jira to track t= his feature enablement.

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





--
Best regard= s!

=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0John Xiao
=
--20cf307ca33a9c636e04a7f06e49--