Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4E6A37E3.7090408@prosyst.bg>
Date: Fri, 09 Sep 2011 18:59:31 +0300
From: Valentin Valchev <v_valchev@prosyst.bg>
Reply-To: v.valchev@prosyst.bg
Organization: ProSyst Labs Bulgaria Ltd
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:6.0.1) Gecko/20110830 Thunderbird/6.0.1
MIME-Version: 1.0
To: dev@felix.apache.org
CC: Felix Meschberger <fmeschbe@adobe.com>
Subject: Re: [WebConsole] Breaking out plugins (was Re: [jira] [Created]
 (FELIX-3105)
 WebConsole bundle should export packages from embedded jars)
References: 
 <2074323890.23638.1315376112161.JavaMail.tomcat@hel.zones.apache.org>
 <4E673ACB.4080808@adobe.com> <4E67651D.6080501@prosyst.bg>
 <4E678674.9060608@adobe.com> <4E67B751.4060101@prosyst.bg>
 <4E6865EE.80805@adobe.com>
In-Reply-To: <4E6865EE.80805@adobe.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigD8ADEFDA315134B4E6ACFA1F"

--------------enigD8ADEFDA315134B4E6ACFA1F
Content-Type: multipart/mixed;
 boundary="------------010906080700060605070706"

This is a multi-part message in MIME format.
--------------010906080700060605070706
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello,
On 8.9.2011 =D0=B3. 09:51 =D1=87., Felix Meschberger wrote:
> Hi all,
>
> On 07.09.2011 20:26, Valentin Valchev wrote:
>> Btw what about the OBR plugin? Shall it remain build-in or moved as
>> separate plugin?
> Now, this starts to be an interesting discussion ;-)
>
> This is the current plugin setup in the Web Console:
>
> (1) Plugins I consider core and which should be kept:
> - Bundle
> - Services
> - License
> - System Properties
Thinking of that, maybe we can add also another one - Framework
Properties, that the user can obtain from
BundleContext.getProperty(String key), since framework properties are
important, but it's not actually necessary to be system properties.
>
> (2) Plugins already considered for breaking out
> - Deployment Admin -- FELIX-3099
> - DS - FELIX-3100
> - Shell - FELIX-3107
>
> (3) Plugins still in the Web Console which might/should be split off
> - Configuration Admin
> - LogService
I think that these should be build-in. Configuration and Log service are
so common, that we can make them available by default.
> - Preferences Service
> - Wire Admin
Could go into common bundle 'compendium plugins'. So with one bundle you
can install almost all OSGi-related plugins/printers.
> - Thread
> - OBR
>
> The idea of also breaking out the Thread configuration printer is to
> easier support thread dump funcitonality introduced with Java 5 and 6
> through the JMX Thread API. Also this could be aligned with the Apache
> Kato project, particularly KATO-14.
Yes, but still Thread information is general information, that can be
used for system analysis and the information will be still usable, if
you  don't have that JMX API. So I vote for leaving Thread info into the
main web console. Additional functionality could be provided by separate
bundle - like that memory plugin, that already uses the JMX API I think.
>
> Now, that we started breaking out plugins, we should probably be
> consequent and break out non-central plugins.
>
> Regards
> Felix
>
>


--=20

-------------------------------------------------
Valentin Valchev =C2=B7 Lead Software Engineer
ProSyst Labs EOOD
1606 Sofia, Bulgaria =C2=B7 48 Vladajska Str.
Tel. +359 (0)2 952 35 81; Fax +359 (0)2 953 26 17
http://www.prosyst.com =C2=B7 v.valchev@prosyst.bg
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------


--------------010906080700060605070706
Content-Type: text/x-vcard; charset=utf-8;
 name="v_valchev.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="v_valchev.vcf"

YmVnaW46dmNhcmQNCmZuOlZhbGVudGluIFZhbGNoZXYNCm46VmFsY2hldjtWYWxlbnRpbg0K
b3JnOlByb1N5c3QgTGFicyBFT09EO0VtYmVkZGVkIFNvZnR3YXJlDQphZHI6OztWbGFkYWpz
a2EgNDggU3RyO1NvZmlhOzsxNjA2O0J1bGdhcmlhDQplbWFpbDtpbnRlcm5ldDp2LnZhbGNo
ZXZAcHJvc3lzdC5iZw0KdGl0bGU6TXINCnRlbDt3b3JrOiszNTkgKDApMiA5NTIzNTgxDQp4
LW1vemlsbGEtaHRtbDpGQUxTRQ0KdXJsOmh0dHA6Ly93d3cucHJvc3lzdC5jb20vDQp2ZXJz
aW9uOjIuMQ0KZW5kOnZjYXJkDQoNCg==
--------------010906080700060605070706--

--------------enigD8ADEFDA315134B4E6ACFA1F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5qN+MACgkQu0KfchdrIxdGawCcCaB9hC3zSG0galmFDSSw2E2X
D4oAniRATURGdShXn4BTyjhsVgMQgOzN
=oDc3
-----END PGP SIGNATURE-----

--------------enigD8ADEFDA315134B4E6ACFA1F--