---------- Forwarded message ----------
From:
Ed Burns <Ed.Burns@sun.com>Date: Fri, Mar 6, 2009 at 3:41 PM
Subject: [426-BeanValidation] Default Enablement Change
To:
JSR-314-OPEN@jcp.orgChange 1
When sitting down to move the content out of Appendix C and into the
spec proper, I came across this statement, currently in setion 2.3.2 of
Appendix C.
If Beans Validation is present in the environment (i.e., the
javax.validation.Validation class is available on the classpath), the
validator with javax.faces.Bean is considered the default validator if
no default validators are defined.
I would like to remove this statement and replace it with.
If running in a container that supports Beans Validation, adding the
validator with id "javax.faces.Bean" to the default-validator section
enables Beans Validation integration.
Change 2
In section 11.1.3, where we declare the context-params and how to handle
them, this text appears:
* javax.faces.VALIDATE_EMPTY_FIELDS -- If this param is set, and calling
toLowerCase().equals("true") on a String representation of its value
returns true, all submitted fields will be validated. This is
necessary to allow the model validator to decide whether null or empty
values are allowable in the current application. If the value is
"false", null or empty values will not be passed to the validators. If
the value is the string "auto", the runtime must check if JSR-303
Beans Validation is present in the current environment. If so, the
runtime must proceed as if the value "true" had been specified. If
JSR-303 Beans Validation is not present in the current environment,
the runtime most proceed as if the value "false" had been specified.
I would like to add the following after the last sentance above. If the
param is not set, the system must behave as if the param was set with
the value "false"
ACTION: please reply my 0900 EST Monday 20090309.
Thanks,
Ed
--
| ed.burns@sun.com | office: 408 884 9519 OR x31640
| homepage: | http://ridingthecrest.com/