This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 48581 - Expensive FilterClassPathImplementation
Summary: Expensive FilterClassPathImplementation
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-09-07 13:22 UTC by _ rkubacki
Modified: 2008-02-25 16:14 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2004-09-07 13:22:51 UTC 
Every instance of FilterClassPathImplementation
creates a string key in constructor that is usualy
>1.5kB and for more complex project hierachy can
be several kB by iterating original classpaths and
concating their string representations.
Comment 1 Martin Matula 2004-09-19 10:43:10 UTC 
So, where's the defect? Do you see a way how to do it more efficiently?
Comment 2 _ rkubacki 2004-09-20 09:07:56 UTC 
What are the problems?

The key is too big. 2kB per FCPI just for storing some key is too big
IMO. 

It is weak. Is it guarantueed that ClassPath.toString on a classpath
has required semantic?
Comment 3 Quality Engineering 2007-09-20 12:01:17 UTC 
Reorganization of java component
Comment 4 Jan Becicka 2008-02-25 16:14:57 UTC 
This issue is not valid in current builds any more. Java support was completely
redesigned in 6.0 time frame. Please use NetBeans 6.0 and later.