| Summary: | Eclipselink still uses Vector / NonSynchronizedVector extensively | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Martin Marinschek <martin.marinschek> |
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | douglas.clarke |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Martin Marinschek
You can forget about the Debugging part of my statement - this seems to be a JDK issue, according to the IntelliJ issue tracker. In any case the collection handling should definitely be streamlined. We have changed all internal usages of Vector but struggle to change return types from operations given many customers using older versions and the pain that causes when they upgrade. There is a work-around listed in bug: 255634 Closing this request as well for now. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |