From dev-return-77986-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Fri Nov 06 03:40:58 2009 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 51337 invoked from network); 6 Nov 2009 03:40:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Nov 2009 03:40:58 -0000 Received: (qmail 74599 invoked by uid 500); 6 Nov 2009 03:40:58 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 74426 invoked by uid 500); 6 Nov 2009 03:40:57 -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 74412 invoked by uid 99); 6 Nov 2009 03:40:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 03:40:57 +0000 X-ASF-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of genspring@gmail.com designates 209.85.216.181 as permitted sender) Received: from [209.85.216.181] (HELO mail-px0-f181.google.com) (209.85.216.181) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 03:40:55 +0000 Received: by pxi11 with SMTP id 11so504139pxi.26 for ; Thu, 05 Nov 2009 19:40:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=vK3y+E5eaNigYGJglPYJaO3hRRBHKe/wTeLEKLEuCqc=; b=oor99knB73mYmaxjO/9Uk7ZvnANHyrtUjQUGHO/AZE/yJn7b9Bw2Yz3DYcrPKfllzn E3QiJvdUcBbCm2WQ51KYu6E6oukezkgo7/b37y8oFR1/AvNCoZe8q+pChbTMQ8O643ra fhqIOAg+pqSvlcoidMKqm/MukmiSPGgTZS8TY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nBftE8+6hW7VxqZzcZsoyzYfMZ9XTUf6/ObizsAs/lo+9o9rDDfZcJHIG/Q4cTFPQd JY+vntItmOJ5bFCMlq2qwcnTOMkVAFINX8CVybBq3/V5hS1UrUg8hKPICuy6qFdnJCeo MeGRWZ7pncz14prZUO4R2YQ0GSvdCA16kU8Fg= MIME-Version: 1.0 Received: by 10.141.49.21 with SMTP id b21mr218540rvk.196.1257478834951; Thu, 05 Nov 2009 19:40:34 -0800 (PST) In-Reply-To: References: Date: Fri, 6 Nov 2009 11:40:34 +0800 Message-ID: Subject: Re: Is there any plan to migrate existing geronimo shell commands from gshell to karaf shell in geronimo 3.0 ? From: Shawn Jiang To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=000e0cd2be984516020477ab9bb5 --000e0cd2be984516020477ab9bb5 Content-Type: text/plain; charset=ISO-8859-1 Currently, here are different opinions on how G3.0 shell should go: *1*, Remove gshell completely, migrate all existing commands to karaf console. *Pros*: Minimize the server size. Bring a clean, easy to use command program model. *Cons*: Break users existing shell. *2*, Keep gshell as it was, add a gshell-karaf bridge to call karaf commands in gshell. *Pros*: Enlarge the server size. Bring a more complex command infrastructure. *Cons*: Without breaking users existing shell. Does anyone have another thoughts on this ? Maybe we need a vote for this someday. On Wed, Nov 4, 2009 at 11:40 AM, Shawn Jiang wrote: > Now we are using karaf as OSGI runtime. Karaf has its own shell which is > based on RFC 139 command service. Karaf shell uses blueprint and a set of > util abstract classes to provide a easy to use program model for new > commands. > > > Geronimo 2.x has its own shell which > > - bases on gshell > - uses groovy to define commands.(I don't kown why but I don't like > this) > - uses classworld to bootstrap itself > - uses a serverProxy to provide geronimo server startup/stop commands. > - uses JMX to invoke jsr88 implementation to provide applications > deploy/undeploy/distribution commands. > - uses JMX to get plugin installer GBean instance to provide plugin > install and customized assemblely commands. > > > I found that all the gshell bootstrap files in geronimo_home/etc has been > removed in geronimo 3.0 framework. Is there any plan to migrate existing > geronimo shell commands from gshell to karaf shell in geronimo 3.0 ? > > > -- > Shawn > -- Shawn --000e0cd2be984516020477ab9bb5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Currently, here are different opinions on how G3.0 shell should go:

= 1, Remove gshell completely, migrate all existing commands to karaf = console.
=A0=A0=A0=A0=A0 Pros:=A0 Minimize the server size.=A0 Br= ing a clean, easy to use command program model.
=A0=A0=A0=A0=A0 Cons: Break users existing shell.

2, K= eep gshell as it was, add a gshell-karaf bridge to call karaf commands in g= shell.
=A0=A0 =A0=A0 Pros:=A0 Enlarge the server size. Bring a mo= re complex command infrastructure.
=A0=A0=A0=A0=A0 Cons: Without breaking users existing shell.

= Does anyone have another thoughts on this ?=A0 Maybe we need a vote for thi= s someday.

On Wed, Nov 4, 2009 at 11:40 A= M, Shawn Jiang <genspring@gmail.com> wrote:
Now we are using = karaf as OSGI runtime. Karaf has its own shell which is based on RFC 139 co= mmand service.=A0 Karaf shell uses blueprint and a set of util abstract cla= sses to provide a easy to use program model=A0 for new commands.


Geronimo 2.x has its own shell which
  • bases on gshell
  • uses groovy to define commands.(I don't kown why but I don't= like this)
  • uses classworld to bootstrap itself
  • uses a ser= verProxy to provide geronimo server startup/stop commands.
  • uses JMX to invoke jsr88 implementation to provide applications deploy/= undeploy/distribution commands.
  • uses JMX to get plugin installer GB= ean instance to provide plugin install and customized assemblely commands.<= /li>

I found that all the gshell bootstrap files in geronimo_home/etc h= as been removed in geronimo 3.0 framework.=A0=A0 Is there any plan=A0 to mi= grate existing geronimo shell commands from gshell to karaf shell in geroni= mo 3.0 ?


--
Shawn



--
Shawn
--000e0cd2be984516020477ab9bb5--