[
http://jira.jboss.com/jira/browse/JBSEAM-1667?page=comments#action_12370346 ]
Norman Richards commented on JBSEAM-1667:
-----------------------------------------
I think this is a problem with trinidad in that the value expression class created by
trinidad (org.apache.myfaces.trinidad.bean.ValueBindingValueExpression) does not used the
ELContext that is
passed in to it. (the use of ValueBinding instead of ValueExpression, obviously causes
this) It's definitely possible to work around this issue with some reflection to
reach down and pull out the target value expression, but I'm not sure this is
important enough to introduce such a big hack. (It does, work, though)
On a related note, I compared the latest trinidad code to the 1.2.1 code. The
ValueBindingValueExpression class has been removed. I don't know if the new code has
a similar problem or not. There's still a number of troubling references to
ValueBinding, so I suspect it might be a lost cause.
Validators not working for ValueBindings from Trinidad
------------------------------------------------------
Key: JBSEAM-1667
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1667
Project: JBoss Seam
Issue Type: Bug
Components: Core, EL, JSF
Affects Versions: 2.0.0.BETA1
Reporter: Pete Muir
Fix For: 2.0.0.CR1
When a ValueBinding from Trinidad is run through Validators invalidValues=null (even when
there are invalidValues).
Easy to replicate, just add @Length(max=5) to
org.jboss.seam.example.seamdiscs.model.Artist.name, start up the seamdiscs example, log
in, click on any artist from the Artists page, make sure they have a name longer than 5,
and hit save.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira