This content has been marked as final.
Show 2 replies
-
1. Re: s:validateEquality vs. s:decorate (with workaround)
joblini Nov 23, 2008 1:59 AM (in response to joblini)Problem is that EqualityValidator line 74 cannot find the component
UIComponent otherComponent = component.findComponent(forId);
As per JSF 1.2 API, findComponent will
search up the parents of this component. If a NamingContainer is encountered, it will be the base for the search.Since s:decorate implements the NamingContainer interface, findComponent fails to locate the forId, and returns null, resulting in the exception seen above.
A workaround is to specifiy the full client id, with a leading
:
, like this:<s:validateEquality for=":#{rich:clientId('password')}" />
This results in something similiar to for=":user:j_id174:password"
-
2. Re: s:validateEquality vs. s:decorate (with workaround)
joblini Nov 23, 2008 5:15 AM (in response to joblini)Noticed that this has previously been reported in JBSEAM-3676.