Dear Wiki user, You have subscribed to a wiki page or wiki category on "Shale Wiki" for change notification.
The following page has been changed by CraigMcClanahan: http://wiki.apache.org/shale/ShaleViewController The comment on the change is: Add some notes about what is changing in 1.0.4 ------------------------------------------------------------------------------ == Configuration == - The jsf configuration files included in the shale-core jarfiles automatically registers the necessary shale objects with + The jsf configuration files included in the shale-core jarfile automatically registers the necessary shale objects with - the JSF implementation, so no changes need to be made to web.xml; just placing the shale jarfile in the webapp's WEB-INF/lib + the JSF implementation, so no changes need to be made to web.xml; just placing the shale-core jarfile in the webapp's WEB-INF/lib - directory is sufficient. + directory is sufficient. (NOTE -- as of version 1.0.4, this logic will be factored out into the new shale-view jarfile, and this refactoring exists in current nightly buids.) The `ViewViewHandler` class implements the JSF standard `ViewHandler` class. It is installed as a wrapper around the `ViewHandler` implementation provided by the underlying JSF implementation. It is this class that invokes the setPostBack method on the @@ -30, +30 @@ which introduces undesirable coupling. The trunk code as at 2006-11-07 contains some code that appears to support a separate ViewController managed bean for each f:subview - in the page by overriding the renderer for subviews to invoke preprocess on processDecodes and prerender on encodeBegin. + in the page by overriding the renderer for subviews to invoke preprocess on processDecodes and prerender on encodeBegin. (NOTE - as of version 1.0.4, subview lifecycle events will be fully supported, and this support exists in current nightly builds.) == Tiger ==
