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.
Description: Name: vgR10179 Date: 03/05/2003 NetBeans Version = Number: 030304 Date: March 4 2003 JDK Version = Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21) Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode) Operating Systems = Windows/Linux RH/Solaris 5.9 Steps to reproduce are: - create the 'Servlet' immediately after S1S4J start (JSPs and Servlets/Servlet template); - compile it and call context menu then; - push the Customize Bean menu item. Customize Bean (Servlet) dialog is opened too slow (more than for 2 sec) for all platforms: Windows NT - 2875 ms (Pentium III, GenuineIntel, 500 MHz). Linux RH - 3453 ms (Pentium III, Katmai, 500MHz). Solaris 5.9 - 4517 ms (Sun-Blade-1000). ====================================================================== A comment.
Verified in BugTraq #4827575.
Radim, please investigate. IMO this does not deserve P2, "Customize Bean" action is useless and should be removed from the IDE.
Downgrading the priority to P3 and setting target milestone to NB40. The funcionality (Customize Bean) is not used when developing Servlets and doesn't make very much sense here. Radime, do we need this funcionality for servlets at all? Is it possible to hide this menu item for servlets?
> Radime, do we need this funcionality for servlets at all? IMO, "Customize Bean" should be killed completely. This is the remnants of the old "everything shold be a JavaBean" philosophy in the old NB days
It is more complicated than that; see my post to nbui. There are a lot of interrelated changes we need to do; Customize Bean action is just one part of it.
Took a fraction of a second for me (on a 1200Mhz machine). Anyway why would you want to invoke Customize Bean on a servlet to begin with?? It's useless.
I know that it's useless but the action is here and it is enabled. So anyone can try.
The recommended hardware configuration for UI responsiveness testing is 1GHZ Pentium 3, 512 MB for Windows and Linux. Blade 1000, 750GHz UIII, 1Gb RAM, 2Gb swap area so I did another measurement using my PIII/800MHz/512MB. Instead of 3453 ms on Linux I get 1392 ms (or 1898 when running as a socend IDE together with Mozilla). To be honest I get 2898 ms on my Solaris 5.8 / Ultra60 / 512MB / 450MHz when there is S1AS and Mozilla running. I think this is significantly slower configuration that we recommend. Also note that if you try it on dev build there are exceptions printed to console that slows down the process (even 0.3 seconds?). These are not printed in release builds. According to this I will close this bug.
Verified with NetBeans 3.5 RC3. Time to open was approximately one second on an Ultra 10 with 640 MB RAM.