Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357841 - Eclipselink still uses Vector / NonSynchronizedVector extensively
Summary: Eclipselink still uses Vector / NonSynchronizedVector extensively
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 13:05 EDT by Martin Marinschek CLA
Modified: 2022-06-09 10:22 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Marinschek CLA 2011-09-15 13:05:53 EDT
Build Identifier: 2.2.1

I guess most of the vector occurrences should be replaced, and the NonSynchronized stuff should be replaced with an ArrayList. The issue is also that my IDE (IntelliJ) can not properly handle NonSynchronizedVector's in the Debugger - it is not showing the contents, so this is a nuisance during Debugging. I would think also other developers have this issue.

Reproducible: Always
Comment 1 Martin Marinschek CLA 2011-09-15 16:48:49 EDT
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.
Comment 2 Doug Clarke CLA 2012-07-13 14:23:42 EDT
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.
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:22:02 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink