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.
Product Version: NetBeans IDE Dev (Build 20080424124045) Java: 1.6.0_05; Java HotSpot(TM) Client VM 10.0-b19 System: Windows XP version 5.1 running on x86; MS932; ja_JP (nb) Default fontsize, project encoding UTF-8 Steps: 1. Open wsdl from db wizard 2. Goto the step 4 3. Double click Advanced cell The dialog appears. It doesn't resize to show all of its buttons. Assumption is that user does not need to manually resize most windows or dialogs to see all of the UI objects and information in them. I'm running in pseudo localized locale in which each message/label is sometimes longer than in English. To account for that in some locales, translations from English (and some other euro languages) could be shown with longer strings. Also I'm running at font size 16, which is viewed as a valid font size that might be used. Resizing issues are not just related to i18n; they might show to user in English locale if they run at larger font size. Often, these issues happen because the length of some label or message or size of entire window is hardcoded vs using layout managers or other techniques or api to have the windows or the objects in them, dynamically resize.
Created attachment 60662 [details] dlg with resize issue
Created attachment 60663 [details] dlg after manual resize
Pls look into this.
also in panel 3, not show all of label for Database name (next to the dropdown) Selected table at least on solaris, even at fontsize default resize makes no difference Andrey can you add image of that ?
Separate issue was filed for this: 129414 - not fixed ( the same was for 6.0 109419 - fixed, verified). It has an image.
this seems to be a serious one in that even using default font size, and using pseudo translated, some buttons were not showing at all and user does not know how to cancel or ok the window (and they would not know to resize it since thats not usual needed user action) perhaps this was side effect of fixing msgs or that once the msgs did come from bundle, then the problem showed but I think its something else since on other wizard panel is also resize problem not there before and it was not missing msg; kaa will add gif of that soon. ken.frank@sun.com
changed target milestone.
This must be due to long strings in the bundle for buttons "Clear All", "Select All", etc. I'll look into it.
http://hg.netbeans.org/main/rev/fc2348474b14 Changeset for 133862 and 133874
verified, trunk 0507, solaris, ja locale using pseudo localized. this could go into patch 2 - adding whiteboard entry and sustaining to cc ken.frank@sun.com
Hi nav064, (1) please provide changeset for this issue only (not for two issues: 133862 and 133874) (2) the change set you provided has label "Automated merge with http://hg.netbeans.org/main/" which is strange, it should have label with issue number that was fixed. (3) Excetion handling in changeset http://hg.netbeans.org/main/rev/fc2348474b14 may be done much better (file sql.wizard/src/org/netbeans/modules/jdbcwizard/builder/wsdl/WSDLGenerator.java): Instead of WSDLGenerator.logger.log(Level.INFO, "Successfully generated wsdl file :" + outputFileName); } catch (final Exception e) { if(e instanceof UnsupportedEncodingException){ ... } if(e instanceof FileNotFoundException){ System.out.println(e.getMessage()+"FileNotFoundException"); } if(e instanceof IOException){ System.out.println(e.getMessage()+"IOException"); } if(e instanceof UnsupportedCharsetException){ System.out.println(((UnsupportedCharsetException)e).getCharsetName()); } you can catch the proper exception type in one level above, like: WSDLGenerator.logger.log(Level.INFO, "Successfully generated wsdl file :" + outputFileName); } catch (UnsupportedEncodingException e) { ... } catch (FileNotFoundException e){ System.out.println(e.getMessage()+"FileNotFoundException"); } catch (IOException e){ System.out.println(e.getMessage()+"IOException"); } catch (UnsupportedCharsetException e){ System.out.println(((UnsupportedCharsetException)e).getCharsetName()); } Also, please do not use System.out.println(), redirect all these messages into log file. And make them more descriptive, please. Can you fix this and may you provide new changeset for this issue? Thanks!
Hi Petr, 1) Please ignore the changes in file WSDLGenerator.java and ChosenColumnPanel.java. This has to be re-worked. Sorry for including that. 2) The changeset for the fix is http://hg.netbeans.org/main/rev/89437828ac01 3) The changes in bundle are for 133874 and those in JDBCWizardTablePanel.java are for 133862. Let me know if you need more info.
Are you going to provide new fix for this issue? Or should I use the old one, which is not very nice?
May be I wasn't clear in my previous post. Please don't make any changes in WSDLGenerator.java and ChosenColumnPanel.java Porting the changes in the remaining files i.e., JDBCWizardTablePanel.java and Bundle.properties as provided in the changeset would fix this issue. The required changes for exception logging are done already to WSDLGenerator.java under a different issue id.
The fix has been ported into the release61_fixes repository. http://hg.netbeans.org/release61_fixes/rev/aa2ce24e193f