[
https://issues.apache.org/jira/browse/ADFFACES-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated ADFFACES-391:
--------------------------------
Resolution: Fixed
Fix Version/s: 1.0.1-incubating-core-SNAPSHOT
Assignee: Adam Winer
Status: Resolved (was: Patch Available)
Checked in patch, after:
- Used trinidad-config.xml instead of web.xml with new <client-validation>
element
and RequestContext.getClientValidation() method
- Fixed rendering to support table messages
- Don't change rendering unless inline validation is on
- Temporarily made the validateInput() method private until
we have a good strategy for namespacing JS
> Client-side validation - enhance to match server-side
> -----------------------------------------------------
>
> Key: ADFFACES-391
> URL: https://issues.apache.org/jira/browse/ADFFACES-391
> Project: MyFaces ADF-Faces
> Issue Type: Improvement
> Components: Components
> Affects Versions: 1.0.1-incubating-core-SNAPSHOT
> Reporter: Danny Robinson
> Assigned To: Adam Winer
> Priority: Minor
> Fix For: 1.0.1-incubating-core-SNAPSHOT
>
> Attachments: inlineValidationPatch.patch,
> inlineValidationPatch.patch, inlineValidationPatch.patch,
> inlineValidationPatch.patch
>
>
> Enhance the current client-side validation mechanism to emulate the
> server-side. Instead of poping the javascript alert, instead dyamically
> insert the error messages into the page in the same way it appears when
> server-side validation is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
