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.
WSDL File text field (and also WS Port text field) should be placed above the "WS Name" text field in the wizard panel. In general when we have a template that says "... from <something>", this <something> should be the first thing we ask for in the wizard panel. I understand that the panel for file name and location is shared, but this atually doesn't work from UI perspective, because if there are more components (text fields) in the wizard, the beginning of all text fields should be vertically aligned. Like this: Name: |___________| Location: |___________| Some Other Field: |___________| I'm not sure we can achieve that when the panel is shared. Now the funny part. If I designed the API :-), I would just share the class that does the event handling of the name, location text field and Browse button, etc. and the person who uses the API would have to do the layout manually. AFAIK there's no other way how to achieve proper layout than doing it manually.
Well, the implementation is according to the UI spec: http://jupiter.czech.sun.com/wiki/view/Cdpj2ee/WebServicesPromoGUISpec#Step_2_New_Web_Service_from_WSDL Also, according to the bug priority guidelines, this should be a P4: http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html
My comments from previous email discussion: "We use the target chooser panel which is common to whole IDE in the wizard. This panel consists of two subpanels - the top panel is a standard name and package panel, the bottom panel can be customized. That's why the WSDL file selection is in the bottom part. There is no option how to swap these two panels in the wizard. Of course, it is possible to fix it by copying the panel implementation to our module, change the layout, etc. but I would avoid it. It is not worth doing this, it is a big prise for a small benefit."
Or change it to enhancement. My intention was to have a record for it in Issuezilla.
IMO this issue is more complex. If I remember, Jano wrote the UI spec for the target chooser wizard panel when new projects implementation came. There was written that name and package fields belongs to the top part of the panel and bottom part can be used for a specific template UI. Unfortunately I cannot find this UI spec now. There is no way how to swap these two parts of the wizard and I also don't remember I would have ever seen the rule "... from <something>". I would propose following: 1. Jano will update the UI spec for target chooser wizard panel saying that the customizable part can be placed above the location part. 2. new issue or enhancement will be filed against target chooser wizard panel and this issue will depend on that issue. 3. when target chooser wizard panel is fixed I will fix this issue.
I'm fine with P4. There has never been a UI spec for general target chooser. But in the beginning we probably didn't have "... from <something>" templates. Project related UI specs are at: Buildsys infrastructure: http://projects.netbeans.org/nonav/buildsys/build-sys-ui-spec-promoe.html Java SE project: http://projects.netbeans.org/nonav/buildsys/j2se-project-ui-spec-promoe.html Java EE project: http://j2ee.netbeans.org/docs/promoe/ejb-and-web-service-ui-spec-promoe.html BTW, take a look at the "WS from WSDL" wizard in the last UI spec.
OK, but I would still follow my previous proposal. I we have "... from <something>" templates now, the target chooser wizard panel should count with that and it should allow to choose if the customizable part will be shown at the top or at the bottom. This is a project UI API change which can be useful for all similar wizards in the future. It applies to: o.n.spi.project.ui.templates.support.Templates.createSimpleTargetChooser(...) o.n.spi.java.project.support.ui.templates.JavaTemplates.createPackageChooser(...)
moving opened issues where TM != dev to TM=TBD
Still not implemented.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team