doc improvements
This commit is contained in:
@@ -30,7 +30,7 @@ Bug Fixes
|
||||
* Fixed a bug resulting in loss of JSF ExternalContext state during execution of the JSF Lifecycle.
|
||||
This bug was effecting integration of the Trindad component library, which requires a special Response object to be set for its Ajax support to work.
|
||||
* Fixed a bug preventing resolution of flow-local messages for flows launched as subflows.
|
||||
* Fixed a bug where field errors recorded using Errors.rejectValue were not being associated with the source field properly.
|
||||
* Fixed a bug where field errors recorded using Errors.rejectValue were not being associated with the source field.
|
||||
|
||||
Documentation
|
||||
* Added documentation on Spring Faces integration with Rich Faces, Trindad, and IceFaces.
|
||||
@@ -38,6 +38,7 @@ Documentation
|
||||
* Added documentation on accessing Web Flow artifacts from Maven Central.
|
||||
* Clarified the conversation-scoped and view-state managed persistence context patterns will be considered for implementation in future Web Flow releases.
|
||||
* Removed unnecessary note about special Spring MVC and JSF model binding semantics; the semantics should be equal between view technologies, even if the underlying technologies differ.
|
||||
* Improved documentation on model validator conventions.
|
||||
|
||||
Changes in version 2.0.0 (29.04.2008)
|
||||
-------------------------------------
|
||||
|
||||
@@ -128,9 +128,9 @@
|
||||
<security:intercept-url pattern="/spring/logout*" access="ROLE_USER" />
|
||||
|
||||
<security:form-login login-page="/spring/login"
|
||||
login-url="/spring/login-process"
|
||||
default-target-url="/spring/main"
|
||||
authentication-failure-url="/spring/login?login_error=1" />
|
||||
login-processing-url="/spring/loginProcess"
|
||||
default-target-url="/spring/main"
|
||||
authentication-failure-url="/spring/login?login_error=1" />
|
||||
|
||||
<security:logout logout-url="/spring/logout" logout-success-url="/spring/logout-success" />
|
||||
</security:http>
|
||||
|
||||
@@ -23,7 +23,7 @@
|
||||
<bookinfo>
|
||||
<title>Spring Web Flow 2 Reference Guide</title>
|
||||
<subtitle>Reference Documentation</subtitle>
|
||||
<releaseinfo>Version 2.0.0</releaseinfo>
|
||||
<releaseinfo>Version 2.0.1</releaseinfo>
|
||||
<pubdate>April 2008</pubdate>
|
||||
<authorgroup>
|
||||
<author>
|
||||
|
||||
@@ -231,6 +231,11 @@ public class BookingValidator {
|
||||
<para>
|
||||
A Validator can also accept a Spring MVC <code>Errors</code> object, which is required for invoking existing Spring Validators.
|
||||
</para>
|
||||
<para>
|
||||
Validators must be registered as Spring beans employing the naming convention <code>${model}Validator</code> to be detected and invoked automatically.
|
||||
In the example above, Spring 2.5 classpath-scanning would detect the @Component and automatically register it as a bean with the name <code>bookingValidator</code>.
|
||||
Then, anytime the <code>booking</code> model needs to be validated, this <code>bookingValidator</code> instance would be invoked for you.
|
||||
</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
Reference in New Issue
Block a user