Ok, thank you Simon.
-Jörg
[EMAIL PROTECTED] schrieb:
[EMAIL PROTECTED] schrieb:
Volker Weber schrieb:
[...]
The http://java.sun.com/dtd/web-facesconfig_1_1.dtd support property
on validator:
<!--
The "validator" element represents a concrete Validator
implementation
class that should be registered under the specified validator
identifier.
Validator identifiers must be unique within the entire web
application.
Nested "attribute" elements identify generic attributes that may be
configured on the corresponding UIComponent in order to affect the
operation of the Validator. Nested "property" elements identify
JavaBeans
properties of the Validator implementation class that may be
configured
to affect the operation of the Validator.
-->
<!ELEMENT validator (description*, display-name*, icon*,
validator-id, validator-class, attribute*, property*)>
It appears that whoever implemented the faces-config parsing didn't
know that either. Here's code from
DigesterFacesConfigUnmarshallerImpl.java (core/trunk12):
digester.addCallMethod("faces-config/validator",
"addValidator", 2);
digester.addCallParam("faces-config/validator/validator-id", 0);
digester.addCallParam("faces-config/validator/validator-class", 1);
So it looks like at the moment the only supported child elements of
<validator> are validator-id and validator-class.
Note that in the same method, the <converter> tag does appear to be
handled correctly, with digester rules existing for nested attribute
and property elements.
I've created a JIRA issue for this:
https://issues.apache.org/jira/browse/MYFACES-1892
However it will be a reasonable amount of work to fix this, so I would
suggest using a workaround rather than waiting for this to be
implemented..
Regards,
Simon
