- Figure out how to find and register custom
ConfigurationResourceProvider
implementations. The idea behind this SPI is to allow a pluggable
way
to return URLs to faces-config files from non-standard locations.
This
feature was started per a private discussion between myself and
representatives
from OSGI. Right now, the SPI is in place, but that's about it.
==> Why not use the jar-file/META/INF/services mechanism as used (eg) by
commons-logging
to configure the logger-factory. Drop in the jar-file and you have a
provider specified...
- Implement a feature to expose the result of parsing all resources in
the form
of a merged DOM which application developers may make use of
(originally I had
thought of just pushing an array of DOMs that developers could sift
through, but
it was pointed out that a merged dom would be more useful)
==> as JMX-ManagedBean? Please, please, please...
As for the rest of the code... no comment as of now.
regards
Alexander
-----Original Message-----
From: Ryan.Lubke_at_Sun.COM [mailto:Ryan.Lubke_at_Sun.COM]
Sent: Thursday, April 19, 2007 9:26 PM
To: dev_at_javaserverfaces.dev.java.net
Subject: [REVIEW] New configuration and managed bean code
Change bundle and new source files are attached.
Looking for any/all feedback ;)