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 112099 - I18N - invalid mbyte in newly created WSDL document
Summary: I18N - invalid mbyte in newly created WSDL document
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2007-08-06 17:32 UTC by kaa
Modified: 2007-10-01 18:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
win xp (156.40 KB, image/jpeg)
2007-08-06 17:33 UTC, kaa 		Details
win xp design view (145.71 KB, image/jpeg)
2007-08-06 17:33 UTC, kaa 		Details
solaris (113.30 KB, image/jpeg)
2007-08-06 17:34 UTC, kaa 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kaa 2007-08-06 17:32:46 UTC 
Product Version: NetBeans IDE Dev (Build 200707270000) Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
System: Windows XP version 5.1 running on x86; MS932; ja_JP (nb)

Steps:
1. Create BPEL Module
2. Create new WSDL document using only ja chars in its name. Press Next.
3. Press Finish button

There are several chars shown incorrectly in navigator, design and properties windows.
The problem exists in the following cases:
1. on WinXP if there are ja chars at the end of WSDL doc name
2. on Solaris with ja (non utf-8) locale
Comment 1 kaa 2007-08-06 17:33:26 UTC 
Created attachment 46222 [details]
win xp
Comment 2 kaa 2007-08-06 17:33:56 UTC 
Created attachment 46223 [details]
win xp design view
Comment 3 kaa 2007-08-06 17:34:31 UTC 
Created attachment 46224 [details]
solaris
Comment 4 Nikita Krjukov 2007-08-20 11:04:48 UTC 
I have fixed problems with encoding for BPEL and did the same for WSDL. 
See comments for the issue #111955
I'm not sure for 100% but it seems I havn't seen the described effects after my fix.
Comment 5 Shivanand Kini 2007-08-21 23:00:44 UTC 
Looks like this got fixed after fix of 111955 please verify.
Comment 6 kaa 2007-10-01 18:53:58 UTC 
verified: build 0927