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.
This is the email from David (developer automation for wsdl editor) "I see many components having names now that weren't there before. However, that being said, still not all components have names. And none of the components in the binding concrete configuration dialogs (e.g., File, FTP, etc) have names. Most dialogs of the these binding configurations have anywhere from 10 to 15 or more components that need to be addressed; it makes it very difficult and a guessing game to reference them without proper names. Are different developers responsible for each binding type dialog? I wonder." For wsdl editor automation, Mohammed and David requested all components in a panel to have their component names set. The new binding configuration panels do not have this, which is a showstopper for automation. Since they have to write magic code (which breaks very often when something changes), if there are no component names. Creating this high priority issue for all responsible developers to add component names in panels. This is a very very low risk task (and completely done by single click on each panel by netbeans GUI builder) and does not affect the user experience at all. But it makes the automation more robust.
Checked in fixes for File and JMS BC to soa-dev: changeset: 87105:1b0c3902333c user: jonelle@netbeans.org date: Fri Nov 07 17:37:50 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components changeset: 87111:9f8cde3ba384 tag: tip parent: 87110:f72b63017568 parent: 87105:1b0c3902333c user: jonelle@netbeans.org date: Fri Nov 07 17:38:17 2008 -0800 summary: Automated merge with http://hg.netbeans.org/soa-dev Still need to post changes to soarelease.
Ported over fixes to soarelease for File BC and JMS BC: searching for changes changeset: 249:4ff0955e4bfa tag: tip user: jonelle@netbeans.org date: Fri Nov 07 17:43:23 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components
Added fixes for LDAP BC in soarelease: changeset: 265:ff043dafcd08 tag: tip user: jonelle@netbeans.org date: Tue Nov 11 11:21:08 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components for LDAPBC
Fixed LDAP fixes to soa-dev: changeset: 87149:5a25b59434d8 tag: tip user: jonelle@netbeans.org date: Tue Nov 11 13:43:29 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components
Checked in fixes for DB BC in soarelease changeset: 266:93fd10815933 tag: tip user: jonelle@netbeans.org date: Tue Nov 11 16:24:34 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components for DBBC
confirmed reassignment to Jim Fu for FTP.
checked in fixes for FTPBC to both: soa-dev: changeset: 87206:49641706eeb0 tag: tip user: jfu <jfu@netbeans.org> date: Thu Nov 13 15:10:25 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components for FTPBC design time and soarelease: changeset: 299:99295390623e tag: tip user: jfu <jfu@netbeans.org> date: Thu Nov 13 15:01:53 2008 -0800 summary: IZ#152748 enabled 'Set Component Names' form property to automatically generate names for visual components for FTPBC desing time
fixed
Verified using Verified on Glassfish ESB 2.1 on windows Vista: PRODUCT_BUILD=20090426-0723 NETBEANS_BUILD=200904151427 NETBEANS_VERSION=6.5.1 SOA_BUILD=090426 NETBEANS_VERSION=Sierra/soarelease Build Ran ally tool against all the panes of the following concrete WSDL editor plugins, to ensure that all fields had defined names: File BC JMS BC LDAP BC Database BC FTP BC Scheduler BC