[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3252) org.jboss.seam.core.Validators not JSF 1.1 compliant
Pete Muir (JIRA)
jira-events at lists.jboss.org
Mon Aug 11 03:48:49 EDT 2008
[ https://jira.jboss.org/jira/browse/JBSEAM-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir closed JBSEAM-3252.
-----------------------------
Resolution: Rejected
Assignee: Pete Muir
Seam 2 requires JSF 1.2
> org.jboss.seam.core.Validators not JSF 1.1 compliant
> ----------------------------------------------------
>
> Key: JBSEAM-3252
> URL: https://jira.jboss.org/jira/browse/JBSEAM-3252
> Project: Seam
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.2.SP1, 2.0.3.CR1, 2.1.0.A1
> Environment: Any
> Reporter: Richard Kennard
> Assignee: Pete Muir
> Priority: Minor
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> org.jboss.seam.core.Validators.validate() seems to work by:
> a) wrapping a custom ValidatingResolver over the existing ELContext
> b) calling setValue
> c) relying on setValue triggering ValidatingResolver.setValue
> d) ValidatingResolver.setValue calls Hibernate Validator
> This works fine if the ValueExpression is a com.sun.facelets.el.TagValueExpression, as created by Facelets or some other JSF 1.2 framework.
> However, if the ValueExpression is a javax.faces.component.ValueExpressionValueBindingAdapter (a compatibility wrapper from a JSF 1.1 component) then steps c) and d) do not happen: the value is set without going through ELContext or ValidatingResolver, and so passes successfully without ever being validated.
> Perhaps an earlier version of Seam used a JSF 1.1-based approach?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list