Jesse Alexander (KSFD 121) wrote:
> - 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...
>
Yes, that was my initial thought, but I was concerned about order, if
there were multiple entries.
I suppose it could be set up similar to META-INF/faces-config.xml
processing, but was going
to troll for other ideas.
> - 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 ;)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net
>
>