Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 41111 invoked from network); 26 Jan 2010 09:12:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 26 Jan 2010 09:12:31 -0000 Received: (qmail 66907 invoked by uid 500); 26 Jan 2010 09:12:31 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 66801 invoked by uid 500); 26 Jan 2010 09:12:30 -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 66791 invoked by uid 99); 26 Jan 2010 09:12:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jan 2010 09:12:30 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of chirunhua@gmail.com designates 209.85.216.203 as permitted sender) Received: from [209.85.216.203] (HELO mail-px0-f203.google.com) (209.85.216.203) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jan 2010 09:12:22 +0000 Received: by pxi41 with SMTP id 41so3402417pxi.27 for ; Tue, 26 Jan 2010 01:12:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=661zFK4HkcOBx171YTOyCRIh33EWyF0jcHuxCyllhJ4=; b=WnmYFS2z0jLLzIjhbgGQnJF1f2879qvEkhrnHLUhVPRs3tic2wB1boMpjez3823qsW 0SfwhxxyK58Z0EyUl8f03mAHuWl5v93uQfCDkIkE3sIA2dL2KxQ5G2N7/gYFLrTPrLNH H4PzETkX8hrqb3jaqNQ6wyjqxb4xg/JnIkF6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ugIzkcEcM7uWfE1tHMtx5FuKbrAIGCcyIxOfeYU1WnS6bj+j1SGH249hJFUElfM38j oBYtzmOTHlqrMmmkZoBFXvLwGF1j2dV0sVcrjqbdMz4vFmyGlRu6Ix/k14ayO8QVOe0v Vq6t7072uQpUUQKp0vRVdyGlBm7nkMrPB2Cww= MIME-Version: 1.0 Received: by 10.140.55.14 with SMTP id d14mr5497687rva.74.1264497120660; Tue, 26 Jan 2010 01:12:00 -0800 (PST) Date: Tue, 26 Jan 2010 17:12:00 +0800 Message-ID: <98a659de1001260112m6d8dcfcdm33d6d00d7c5da11f@mail.gmail.com> Subject: OSGi features on Admin Console From: chi runhua To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary=0016369207ffb24cbb047e0dad62 X-Virus-Checked: Checked by ClamAV on apache.org --0016369207ffb24cbb047e0dad62 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, With the progress of OSGi implementation for G3.0, I think we can start thinking about which features we will provide to users via Admin Console. IMHO, there would be 2 options to present the new features: 1. Use an independent section for OSGi part and keep Java EE parts as is. 2. Integrate OSGi features into existing portlets If we choose option 1, I can think of following new portlets to be appended to the navigation item(might be more, you are welcome to append the list): 1.a. OSGi Framework information; 1.b. Bundle management, which is only used to install/uninstall bundles; 1.c. Blueprint management, which Rex and Delos are working on, but resides in Debug Views section temporarily. 1.c. OBR management, which is used to Add/Browse repositories and install bundles from repos. Other than the portlets above, there are 2 more features: User Admin and Lo= g Service, which can be integrated with existing portlets like Security&Log viewers. I can see a lot of overlaps between Java EE and OSGi related portlets, it would be nice to have them consolidated as one, for example=EF=BC=9B Bundle management v.s Deploy New OBR management v.s Install Plugins from repositories OSGi Framework info v.s Java System Info But thinking of the resource available, I'd like to suggest we choose optio= n 1 for G3.0 console. Any comments? Jeff C --0016369207ffb24cbb047e0dad62 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all,

With the progress of OSGi implementation for G3.0, I think = we can start thinking about which features we will provide to users via Adm= in Console. IMHO, there would be 2 options to present the new features:
=C2=A0=C2=A0 1.=C2=A0 Use an independent section for OSGi part and keep Jav= a EE parts as is.
=C2=A0=C2=A0 2.=C2=A0 Integrate OSGi features into exi= sting portlets

If we choose option 1, I can think of following new p= ortlets to be appended to the navigation item(might be more, you are welcom= e to append the list):
=C2=A0=C2=A0=C2=A0=C2=A0 1.a.=C2=A0 OSGi=C2=A0 Framework information;
= =C2=A0=C2=A0=C2=A0=C2=A0 1.b.=C2=A0 Bundle management, which is only used t= o install/uninstall bundles;
=C2=A0=C2=A0=C2=A0=C2=A0 1.c.=C2=A0 Bluepri= nt management, which Rex and Delos are working on, but resides in Debug Vie= ws section temporarily.
=C2=A0=C2=A0=C2=A0=C2=A0 1.c.=C2=A0 OBR management, which is used to Add/Br= owse repositories and install bundles from repos.
=C2=A0=C2=A0=C2=A0=C2= =A0
Other than the portlets above, there are 2 more features: User Admi= n and Log Service, which can be integrated with existing portlets like Secu= rity&Log viewers.

I can see a lot of overlaps between Java EE and OSGi related portlets, = it would be nice to have them consolidated as one, for example=EF=BC=9B
= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Bundle management=C2=A0=C2=A0 v.= s=C2=A0 Deploy New
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OBR manage= ment=C2=A0=C2=A0=C2=A0 v.s=C2=A0=C2=A0 Install Plugins from repositories =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OSGi Framework info=C2=A0 v.s=C2=A0 Ja= va System Info

But thinking of the resource available, I'd like = to suggest we choose option 1 for G3.0 console.

Any comments?

Jeff C
--0016369207ffb24cbb047e0dad62--