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 70462 - Faster search for BeanInfos and property editors
Summary: Faster search for BeanInfos and property editors
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@platform
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-12-15 12:42 UTC by _ rkubacki
Modified: 2009-01-06 14:30 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
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 2005-12-15 12:42:52 UTC 
We need BIs mostly for loading of settings and for form editor to analyze
designed components. Possibly also for editing of BeanNodes.

This is slow if the BeanInfo class is in a package enumerated in BI search path
or not defined at all as we can ask all modules to load it for each it on search
path.
Comment 1 _ rkubacki 2005-12-15 12:49:39 UTC 
Possible tricks to make it faster:

BI in the same package. Not possible for JDK classes or something what should
not be exposed in API/SPI

Reduce number of entries in search paths. Currently there are -
org.openide.src.beaninfo
org.netbeans.beaninfo
org.netbeans.core.execution.beaninfo
org.netbeans.modules.xml.tax.beans.beaninfo
org.netbeans.modules.form.beaninfo.awt
org.netbeans.modules.form.beaninfo.swing

Do not query app CL too often. The dirty trick would be to load some known
resource from packages on search path to warmup the CL cache.

Avoid the need for BI ;-)