Description
WebWork The framework adds support for client-side validation on top of XWork's the standard validation framework.
Client-side validation It can be enabled on a per-form basis by specifying validate="true"
in the form tag:.
Code Block | ||||
---|---|---|---|---|
| ||||
<ww<s:form name="test" action="javascriptValidation" validate="true"> ... </wws:form> | ||||
Note |
If a name
for the form
...
is not given, the action mapping name will be used as the form name.
...
A Otherwise, a correct action
and namespace
attributes must be provided to the <ww <saf:form>
tag. For example, the Action named
Code Block | ||||||
---|---|---|---|---|---|---|
|
...
|
...
<s | ||
Code Block | ||
---|---|---|
html | html | <ww:form namespace="/user" action="submitProfile" validate="true"> ... </wws:form> |
While the following will "work" in the sense that the form will function correctlyTechnically, the form's action attribute can refer to a "path" that includes the namespace and action as a URI. But, client-side validation will not. That is because WebWork must know the exact namespace and action (rather than a URL) to properly support validation requires that the action name and namespeact to be set separately.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<s <ww:form action="/user/submitProfile.action" validate="true"> ... </wws:form> |
All the standard usual validation configuration steps still apply to client-side validation. Client-side validation uses the same validation rules as server-side validation. If server-side validation doesn't work, then client-side validation won't work either.
Info | ||
---|---|---|
| ||
The | ||
Note | ||
Note that the |
Client Side Validation Types
There are two styles of client side validation:.
Used by the xhtml theme and css_xhtml theme | |
Used by the ajax theme |