[
https://issues.jboss.org/browse/RF-13648?page=com.atlassian.jira.plugin.s...
]
Juraj Húska commented on RF-13648:
----------------------------------
I have tried to reproduce the issue on this branch of Metamer:
https://github.com/richfaces/richfaces-qa/tree/RF-13648
I *can not* reproduce it.
When {{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is true, submitted
empty strings are coerced to the empty {{String}} according to the EL specification. See
the [
comment|https://issues.apache.org/bugzilla/show_bug.cgi?id=56522#c1] in the mentioned
jasper issue. If {{Object}} type is used instead of {{String}}, then empty fields remains
{{null}} as expected (however graph validator does not support Object properties).
I have tried it both with graph validator and client side validation.
Graph Validator files:
*
[
facelet|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b...]
*
[
bean|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0...]
CSV:
*
[
facelet|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b...]
*
[
bean|https://github.com/richfaces/richfaces-qa/blob/e2cbfcc00937ede44b0d0...]
Graph Validator + Tomcat 8.0.8: interpret empty strings as null is
ignored
--------------------------------------------------------------------------
Key: RF-13648
URL:
https://issues.jboss.org/browse/RF-13648
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.7
Environment: Tomcat 8.0.8, OpenJDK 7, OpenSuse 13.1 x64
Reporter: Tony Cramer
Assignee: Juraj Húska
{{javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL}} is ignored during Graph
validating.
Some debugging info:
Object being validated ({{value}} argument) in method
{{org.richfaces.validator.BeanValidatorServiceImpl.validateObject}} contains empty strings
("").
Expected behavior: There should be nulls in properties, because interpreting empty
strings as null is enabled.
This causes validation to not pass.
Something has changed in _jasper-el_ in Tomcat 8.0.8 which I updated recently from 8.0.5.
If I replace _jasper-el.jar_ from Tomcat 8.0.5, everything works.
Tomcat bug or RF bug?
Edit:
It's definitely JSF/RF's issue. Tomcat EL has changed to meet EL spec.
https://issues.apache.org/bugzilla/show_bug.cgi?id=56522
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)