Hi guys,
interesting idea, Martin. If anything, it should work the same for
components and validators - I don´t see why the artifacts should be
treated differently.
best regards,
Martin
On Sat, Jul 10, 2010 at 8:37 PM, Jakob Korherr <jakob.korh...@gmail.com> wrote:
> Hi Martin,
>
> Unfortunately I think it means only the "speced" attributes are wired.
> However it is not really clear, because this would only work on facelets
> (because on JSP you have to specify all attributes), but f:validator is only
> described in detail for JSPs in the spec pdf. Maybe you could ask the EG
> about this or you could raise a spec issue for JSF 2.1.
>
> Currently the setting of custom properties is prevented in
> org.apache.myfaces.view.facelets.tag.jsf.core.ValidateDelegateHandler.createMetaRuleset(),
> because this one does super.createMetaRuleset() and calls ignoreAll() on the
> result. Thus it would be very easy to change ;)
>
> Regards,
> Jakob
>
> 2010/7/9 Martin Koci <martin.k...@aura.cz>
>>
>> Hi,
>>
>> javadoc for javax.faces.view.facelets.ValidatorHandler contains this
>> sentence:
>>
>> "Will wire all attributes set to the Validator instance
>> created/fetched". Based on that one our developer tried this:
>>
>> <f:validator binding="#{aValidator}" property="#{expression}" />
>>
>> Expected result was to put a value into validator via setter
>> setProperty(). But "all attributes set" means binding, for,
>> disabled, ... only the specified ones, right?
>>
>> Thanks,
>>
>>
>> Martin Kočí
>>
>>
>>
>
>
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at
>
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
