You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Raymond DeCampo (JIRA)" <de...@myfaces.apache.org> on 2007/08/23 21:24:30 UTC
[jira] Created: (TOMAHAWK-1094) Validation message for inputDate
component when using non-MyFaces JSF implementation is
"org.apache.myfaces.Date.INVALID"
Validation message for inputDate component when using non-MyFaces JSF implementation is "org.apache.myfaces.Date.INVALID"
-------------------------------------------------------------------------------------------------------------------------
Key: TOMAHAWK-1094
URL: https://issues.apache.org/jira/browse/TOMAHAWK-1094
Project: MyFaces Tomahawk
Issue Type: Bug
Components: Date
Affects Versions: 1.1.6
Environment: Sun RI 1.2_04
JBoss 4.2.0
Reporter: Raymond DeCampo
When using the Sun RI implementation with Tomahawk, the validation message for the inputDate component is "org.apache.myfaces.Date.INVALID". I imagine this occurs because the message is defined in the JSF message bundle supplied with MyFaces; when using the Sun RI, there is no entry for org.apache.myfaces.Date.INVALID in the bundle.
A workaround would appear to be to use a custom JSF message bundle and add the message for org.apache.myfaces.Date.INVALID.
As for the fix, I would suggest bundling the messages with Tomahawk under a different resource bundle. First check the configurable JSF message bundle for the message; if it appears, use that one. Otherwise fall back to the hardcoded Tomahawk message bundle. This will allow developers to easily override the supplied messages without additional configuration while providing for the messages in the case where the developer has not overridden the default set. It also covers the case when the main message bundle is overridden but Tomahawk specific messages were omitted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TOMAHAWK-1094) Validation message for inputDate
component when using non-MyFaces JSF implementation is
"org.apache.myfaces.Date.INVALID"
Posted by "Raymond DeCampo (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TOMAHAWK-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522253 ]
Raymond DeCampo commented on TOMAHAWK-1094:
-------------------------------------------
I've since discovered a simpler work-around when using JSF 1.2. Use the converterMessage attribute with the inputDate component.
> Validation message for inputDate component when using non-MyFaces JSF implementation is "org.apache.myfaces.Date.INVALID"
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-1094
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1094
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Date
> Affects Versions: 1.1.6
> Environment: Sun RI 1.2_04
> JBoss 4.2.0
> Reporter: Raymond DeCampo
>
> When using the Sun RI implementation with Tomahawk, the validation message for the inputDate component is "org.apache.myfaces.Date.INVALID". I imagine this occurs because the message is defined in the JSF message bundle supplied with MyFaces; when using the Sun RI, there is no entry for org.apache.myfaces.Date.INVALID in the bundle.
> A workaround would appear to be to use a custom JSF message bundle and add the message for org.apache.myfaces.Date.INVALID.
> As for the fix, I would suggest bundling the messages with Tomahawk under a different resource bundle. First check the configurable JSF message bundle for the message; if it appears, use that one. Otherwise fall back to the hardcoded Tomahawk message bundle. This will allow developers to easily override the supplied messages without additional configuration while providing for the messages in the case where the developer has not overridden the default set. It also covers the case when the main message bundle is overridden but Tomahawk specific messages were omitted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.