You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2009/05/19 02:52:45 UTC

[jira] Created: (MYFACES-2236) Allow define defferedValueType for component/converter/validator for tag @JSFProperty when generate tld using myfaces-builder-plugin

Allow define defferedValueType for component/converter/validator for tag @JSFProperty when generate tld using myfaces-builder-plugin
------------------------------------------------------------------------------------------------------------------------------------

                 Key: MYFACES-2236
                 URL: https://issues.apache.org/jira/browse/MYFACES-2236
             Project: MyFaces Core
          Issue Type: Bug
          Components: build process
            Reporter: Leonardo Uribe
            Assignee: Leonardo Uribe



The example that requires is f:convertDateTime.

timeZone could be assigned to TimeZone instances, but do not to String instances. The tag class has the code to convert the value and assign it as a TimeZone instance on the converter, but the tld is generated in this way (without change the template):

      <attribute>
         <description><![CDATA[The time zone to use instead of GMT (the default timezone). When
this value is a value-binding to a TimeZone instance, that
timezone is used. Otherwise this value is treated as a String
containing a timezone id, ie as the ID parameter of method
java.util.TimeZone.getTimeZone(String).]]></description>
         <name>timeZone</name>
         <deferred-value>
             <type>java.util.TimeZone</type>
         </deferred-value>
      </attribute>

The same problem is with locale:

      <attribute>
         <description><![CDATA[The name of the locale to be used, instead of the default.]]></description>
         <name>locale</name>
         <deferred-value>
             <type>java.util.Locale</type>
         </deferred-value>
      </attribute>

Right now, the solution is fix the template to include a "hack" for these two properties, but we need a more general solution to this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.