You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Simon Lessard (JIRA)" <ad...@incubator.apache.org> on 2006/10/01 17:57:21 UTC
[jira] Commented: (ADFFACES-72) Convert Trinidad to Java 5
standards and clean-up code
[ http://issues.apache.org/jira/browse/ADFFACES-72?page=comments#action_12439003 ]
Simon Lessard commented on ADFFACES-72:
---------------------------------------
Hello garpnic,
This kind of discussion is held on the developer mailing, not on JIRA. To subscribe to the list you can send an empty mail to adffaces-dev-subscribe@incubator.apache.org. The main reason why it was converted is in prevision of JSF 1.2 which is based on Java 5. Furthermore, JSF 1.1 is not part of any JEE standard as it was created after JEE 1.4 and JEE 5 specification request JSF 1.2, not 1.1.
> Convert Trinidad to Java 5 standards and clean-up code
> ------------------------------------------------------
>
> Key: ADFFACES-72
> URL: http://issues.apache.org/jira/browse/ADFFACES-72
> Project: MyFaces ADF-Faces
> Issue Type: Improvement
> Reporter: Simon Lessard
> Priority: Minor
> Attachments: API_1_5_standard.zip, API_template.patch, DEMO_DateField_Java_5.patch, DEMO_java_5.patch, DEMO_SourceCodeServlet_Java_5.patch, Faces_plugin.patch, FINAL_Java_5.zip, FINAL_Java_5_v2.zip, I18N_Java_5.patch, IMPL_5_standard.zip, SubKeyMap_Java_5.patch, TAG_Java_5.patch, UI_Java_5.zip, UNIT_TESTS_Java_5.zip, UNIT_UI_Java_5_v2.zip, XRTS_java_5.patch
>
>
> This is a non critical long term improvement that should convert existing Trinidad code to Java 5.0 standard:
> - Remove references to deprecated API
> - Remove unused imports
> - Remove unread variables
> - Change StringBuffer to StringBuilder where synchronization is not required
> - Reduce to minimum the use of raw type collections (they should be used only when calling an external 1.4 API)
> - Make all collection generic compliant
> - Use the enhanced 'for' construct in favor to classical 'for' whenever possible to reduce potential OutOfBoundsException risks
> - Use enums
> - Use concurrent API
> - Add @Override annotation on overridden methods
> - Add @SuppressWarning("unchecked") on method calling external method that returns non-generic enabled collections
--
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