You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Kentaro Kinebuchi (JIRA)" <de...@myfaces.apache.org> on 2011/01/04 20:29:45 UTC
[jira] Updated: (TRINIDAD-1993) Setting tr:validateByteLength
maximum property as an EL expression results in an error
[ https://issues.apache.org/jira/browse/TRINIDAD-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kentaro Kinebuchi updated TRINIDAD-1993:
----------------------------------------
Status: Patch Available (was: Open)
> Setting tr:validateByteLength maximum property as an EL expression results in an error
> --------------------------------------------------------------------------------------
>
> Key: TRINIDAD-1993
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1993
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0.3-core
> Environment: Linux x86
> Reporter: Kentaro Kinebuchi
> Attachments: bug10432287.patch
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.