[ http://issues.apache.org/jira/browse/BEEHIVE-206?page=comments#action_12374111 ]
matt c commented on BEEHIVE-206: -------------------------------- The above issue failed b/c the maxValue was set to an improper format. Set it to "Sun, Jul 4, '04", for example, and the code will work. !!The error message is erroneous though!! - even though the maxValue is wrong, it prints out the value set in the client, for the above code the error is: Cause: The value, Wed, Jul 4, '01, assigned to maxValue date constraint property is not in the specified format of: EEE, MMM d, ''yy Where the value - Wed, Jul 4, '01 - is not the maxValue (and not the problem), but it is instead the value being sent by the client. Verified fixed using local beehive build synced to SVN 393036 by running the test case: beehive/trunk/controls/test/src/junit-controls/org/apache/beehive/controls/test/src/units/org/apache/beehive/controls/test/java/property/MemberTypeTest.java This bug can be closed, though I think the error message should be changed. > control property constraint:AnnotationMemberTypes.Date accept one format > ------------------------------------------------------------------------ > > Key: BEEHIVE-206 > URL: http://issues.apache.org/jira/browse/BEEHIVE-206 > Project: Beehive > Type: Bug > Components: Controls > Versions: V1Beta > Reporter: James Song > Assignee: James Song > Priority: Minor > Attachments: MemberTypeTest.java, MemberTypeTest.java, PersonControl.java, > PersonControl.java > > Currently, AnnotationMemberTypes.Date only accept YYYY/MM/DD. > There will be cases when user would like to specify the HH:MM, or other input > format, such as long date format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
