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: domain of fmeschbe@adobe.com designates
 64.18.1.21 as permitted sender)
From: Felix Meschberger <fmeschbe@adobe.com>
To: Apache Felix Dev List <dev@felix.apache.org>
Date: Mon, 19 Nov 2012 09:38:14 +0000
Subject: ServiceGraph
Thread-Topic: ServiceGraph
Thread-Index: Ac3GOZkGv78UJuuHQUqUzTD9ECgUig==
Message-ID: <61695164-E935-4E95-A18F-EB08B5F00B33@adobe.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi

I tried to tackle FELIX-3764 [1] just to realize that this plugin IMHO is n=
ot properly integrated with the web console:

  * registers a /servicegraph/json servlet
  * registers /servicegraphe resources

The problem with this is, that it doesn't account for non-root servlet cont=
exts, is not integrated with the URL space and does not leverage the Web Co=
nsole access control mechanisms.

I suggest to change this plugin as follows:

  * Handle the .../json request as part of the WebConsolePlugin.service met=
hod
  * Implement a URL getResource [2] method in the WebConsolePlugin class

This allows for full integration, leveraging access control and URL space i=
ntegration plus also allows for using the appRoot and pluginRoot Web Consol=
e properties [3].

Does this make sense ?

Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-3764
[2] http://felix.apache.org/site/providing-resources.html
[3] http://felix.apache.org/site/providing-web-console-plugins.html=