incubator-adffaces-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Lessard (JIRA)" <>
Subject [jira] Commented: (ADFFACES-72) Convert Trinidad to Java 5 standards and clean-up code
Date Fri, 11 Aug 2006 19:11:15 GMT
    [ ] 
Simon Lessard commented on ADFFACES-72:

Note: If the final patch is applied, I think this issue can be closed as long as people submit
Java 5 compliant patches for other issues. There's still some cleaning to do, but considering
the amount of patches I already submitted for it, I think a new task issue to remove deprecated
API calls and such would be better.

> Convert Trinidad to Java 5 standards and clean-up code
> ------------------------------------------------------
>                 Key: ADFFACES-72
>                 URL:
>             Project: MyFaces ADF-Faces
>          Issue Type: Improvement
>            Reporter: Simon Lessard
>            Priority: Minor
>         Attachments:, API_template.patch, DEMO_DateField_Java_5.patch,
DEMO_java_5.patch, DEMO_SourceCodeServlet_Java_5.patch, Faces_plugin.patch,,
I18N_Java_5.patch,, SubKeyMap_Java_5.patch, TAG_Java_5.patch,,,, 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:
For more information on JIRA, see:


View raw message