Ok guys I posted an initial proposal in issue
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=774
you also can download the proposal directly from
http://people.apache.org/~werpu/Proposal%20Configuration.pdf
It is just a proposal for 2 extension points first an extension point which gives read and write access to the configuration
(although it is up to the implementation whether the right access is granted and in which state of the application)
Secondly system events all extensions and also the implementation must use as extension point
to get configuration write and read behavior in. This notification system uses the existing system events to perform that
but more details in the PDF.
Btw. can someone please close https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=765 since I cannot do it, it is oviously now covered by the proposal and the unload itself is part of a connecting extension framework or the respective implementation.
Werner
On Tue, Mar 16, 2010 at 12:07 PM, Martin Marinschek <mmarinschek@apache.org> wrote:Hi guys,
just so that I can add my 2cents as well: I believe it would be a
valuable addition to JSF if we had some standardized hooks into the
configuration management - that was really missing from the beginning.
I believe it was also discussed from early on, but always delayed to a
later version.That later version needs to be JSF 2.1. Time to make it happen :)-Dan--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen