Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 163215

Summary:	[model] classpath decoding should use a SAX parser
Product:	[Eclipse Project] JDT	Reporter:	Olivier Thomann <Olivier_Thomann>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Olivier Thomann

2006-11-02 09:55:13 EST

There is no need to create a DOM tree for the classpath file. A SAX parser with the appropriate callbacks should be good enough.

Comment 1 Olivier Thomann

2006-11-02 09:56:07 EST

org.eclipse.jdt.internal.core.JavaProject#decodeClasspath(String, Map)
org.eclipse.jdt.internal.core.JavaProject#decodeClasspathEntry(String)

are the places where a SAX parse could be used.

Comment 2 Eclipse Genie

2019-09-23 20:29:18 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.