Issue Details (XML | Word | Printable)

Key: SPR-5231
Type: Refactoring Refactoring
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Juergen Hoeller
Reporter: Juergen Hoeller
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Spring Framework

Java 5+ upgrade of core container API and implementation

Created: 23/Oct/08 04:35 AM   Updated: 01/Dec/08 10:07 AM   Resolved: 20/Nov/08 03:36 PM
Component/s: SpringAOP, SpringCORE
Affects Version/s: None
Fix Version/s: 3.0 M1

Time Tracking:
Not Specified


 Description  « Hide

Spring 3.0 gives us the chance to upgrade the entire Spring API to Java 5+.

This issue is tracking the upgrade effort in Spring's core packages:

  • org.springframework.aop
  • org.springframework.beans
  • org.springframework.context
  • org.springframework.core
  • org.springframework.util


Paul Benedict added a comment - 21/Nov/08 08:12 AM

Will you be introducing generic signatures? Many of these classes still use raw types all over the place.


Juergen Hoeller added a comment - 24/Nov/08 09:41 AM

Have you been looking at the actual (new) 3.0 repo at https://src.springframework.org/svn/spring-framework/trunk?

We are certainly not done with generifying the API yet... but plenty of it has been generified already.

Juergen


Juergen Hoeller added a comment - 26/Nov/08 06:40 PM

Two further big commit bunches came in yesterday and tonight. The Java 5 code style update is 99% done now.

Juergen


Paul Benedict added a comment - 01/Dec/08 10:07 AM

My apologies. Because this issue was Resolved well in advance of further commits, I thought all the commits were finished. My interest is looking to see how much generic signatures, like SPR-4610, will make it into the core.

For example, this article says that instanceof operator should always use the unknown type <?> on a generic class. I think it's a good practice to follow:
http://mail.openjdk.java.net/pipermail/compiler-dev/2008-November/000714.html