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 94215

Summary: Component XML files should be generated via introspection
Product: obsolete Reporter: bugbridge <bugbridge>
Component: visualwebAssignee: _ edwingo <edwingo>
Status: NEW ---    
Severity: blocker CC: edwingo, gjmurphy, joellelam
Priority: P2    
Version: 5.x   
Hardware: PC   
OS: Windows XP   
Issue Type: ENHANCEMENT Exception Reporter:

Description bugbridge 2007-02-03 01:27:48 UTC
Original status: 1-Dispatched; Suggested Status: NEW

Original Target Release: shortfin_dev; Suggested Target Milestone : 5.5


Original submitter: joellelam

Description:
Component XML files should be generated via introspection.  

Our current method is to manually create an xml file for each component item.
There is then redundancy between the xml file and BeanInfo in the following
areas: images, names, resources, and maybe tooltip. 

I know that there is an effort to do this functionality by [edwingo].
[edwingo]'s focus is primarily on imported complibs, but the functionality is
similar.  It takes a class and generates and xml file for the palette.  I know
there is a movement towards loading all components through [edwingo]'s code. 
This would then make the RFE obsolete.  

There are some benefits to the current method.  By having these static defined
xml files, we have increased our performance.  Moving towards having all
component loaded by complib may bring back earlier performance issues.  There
should be effort made towards only creating these xml files once and never
again.  This would mean decreased performance on first startup, but after that
we will continue to have the performance gains that we currently do.

Evaluation:
(by edwingo)
As I understand it, the current plan is to add this to the shortfin update release.
Comment 1 Jiri Prox 2007-09-17 21:39:22 UTC
Obsolete milestone, please reevaluate
Comment 2 _ edwingo 2007-09-17 21:59:11 UTC
I'm not sure what the plans are regarding this issue. I would guess that nothing will change in this area unless someone
thinks this is a priority. So I will mark this as future.