Am 25.09.2015 um 17:42 schrieb Edward Burns <edward.burns_at_oracle.com>:
EB> I'm going to invoke executive authority here and insist the solution be
EB> done with Bean Validation. This is the platform. If people want JSF
EB> specific solution, it can certainly be done, and has been done.
>>>>> On Fri, 25 Sep 2015 21:14:18 +0200, Frank Caputo <frank_at_frankcaputo.de> said:
FC> I totally understand this.
EB> Frank, your point about implementation details leaking out is well
EB> taken. I'll see what I can do about that.
FC> Maybe you can still do something like, what I have proposed:
FC> <f:validateWholeBean value="#{backingBean}">
FC> <input jsf:id="password1" jsf:value="#{backingBean.password1}"/>
FC> <input jsf:id="password2" jsf:value="#{backingBean.password2}"/>
FC> </f:validateWholeBean>
Thanks for the feedback. I was able to move it to be entirely an
implementation detail and the spec is much cleaner for it. I'm pretty
happy with the API now, but I haven't merged it to master because I'm
waiting for some apparent breakage from of the ADF tests to clear out.
This means more time for comments!
Thanks,
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 29 Business days til JavaOne 2015
| 44 Business days til DOAG 2015