https://bz.apache.org/bugzilla/show_bug.cgi?id=66161
--- Comment #1 from [email protected] --- Some additions: maybe the current wrong behaviour (for us) resulted due to updates and we missed something updating from EL2.x to EL3.0. And the tomcat update and the resulting error was just a "by-product". We also set <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> and currently still provide a own EmptyNullStringResolver¹ (which might be the problem here). Without the Resolver, an empty string is passed to concat. I will take a look into removing the custom resolver. ¹ see eg. https://balusc.omnifaces.org/2015/10/the-empty-string-madness.html So this bug simple might be invalid. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
