Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.0-beta-1
-
None
-
Linux x86
Description
The stack trace is given below. The error is happening because the maximum property in org.apache.myfaces.trinidad.validator.ByteLengthValidator does not follow convention and is called "maximumBytes" instead of "maximum". This is also causing issues with af:validateByteLength.
java.lang.IllegalArgumentException: Invalid attribute name maximum
at org.apache.myfaces.trinidad.validator.ValidatorUtils._getPropertyKey(ValidatorUtils.java:116)
at org.apache.myfaces.trinidad.validator.ValidatorUtils.setValueExpression(ValidatorUtils.java:80)
at org.apache.myfaces.trinidad.validator.ByteLengthValidator.setValueExpression(ByteLengthValidator.java:288)
at org.apache.myfaces.trinidadinternal.taglib.validator.ValidateByteLengthTag._setProperties(ValidateByteLengthTag.java:82)
at org.apache.myfaces.trinidadinternal.taglib.validator.ValidateByteLengthTag.createValidator(ValidateByteLengthTag.java:71)
at org.apache.myfaces.trinidad.webapp.TrinidadValidatorELTag.doStartTag(TrinidadValidatorELTag.java:54)
at jsp_servlet._test1_jspx._jspx_tag4(_test1_jspx.java:293)
at jsp_servlet._test1_jspx._jspx_tag3(_test1_jspx.java:256)
at jsp_servlet._test1_jspx._jspx_tag2(_test1_jspx.java:205)
at jsp_servlet._test1_jspx._jspx_tag1(_test1_jspx.java:155)
at jsp_servlet._test1_jspx._jspx_tag0(_test1_jspx.java:104)
at jsp_servlet._test1_jspx._jspService(_test1_jspx.java:65)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:12