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 85736 - wsdl model is not understanding chinese characters
Summary: wsdl model is not understanding chinese characters
Status: VERIFIED INVALID
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Model (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Girish Balachandran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-26 02:59 UTC by Ritesh Adval
Modified: 2007-03-29 20:19 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Ritesh Adval 2006-09-26 02:59:17 UTC 
partnerLinkType name attribute and role attribute have chinease characters.

bugster  CR 647388 is blocking on this.

when calling getName() on partnerLinkType and role it is returning garbage 
charcters.

A test has been added in 
xml\wsdlext\org.netbeans.modules.xml.wsdl.model.extensions.i18n.ReadChineaseTest


to run tests first change your regional and language options from control panel:

*click on regional and language options 
* in the regional options tab change the language to chinease PRC from drop 
down. apply and ok.

* restart netbeans.

*uncomment test

testChineasePartnerLinkType
and 

testChineasePartnerLinkTypeRole

* run test in ReadChineaseTest.
Comment 1 Sreenivasan Genipudi 2006-09-26 03:55:49 UTC 
cc sreeni
Comment 2 Nam Nguyen 2006-09-26 06:28:28 UTC 
Girish, I think maybe you could help out on this one.
Comment 3 artibee 2006-09-26 19:15:56 UTC 
bugster CR 6473881 is blocking on this.
Comment 4 Girish Balachandran 2006-09-26 23:24:07 UTC 
There is an user error in the unit test case written. WSDL (/Schema) model
indeed handels unicode chars. Please see the modified test case. What I have
done is, read the partner link type that has chinese chars in it, added a prefix
and then write it out in another file. Comparing the original file and the
output file, you will see that the chinese chars are intact as expected.

The string constant that was defined in the test case was wrong. The unicode
chars had to be escaped for a proper string comparison.


As a side note, the procedure that is mentioned in this bug for changing the
locale setting is wrong. Changing language in "regional options" will change
only the units of the language and not the language itself. Proper language
change should be done in the last tab (Advanced) and you might need windows
install CD for successful completion.

here are the proper steps
http://devtools.sfbay/teams/DeveloperTools_I18N/windows.usingasianlocales
http://devtools.sfbay/teams/DeveloperTools_I18N/setuplocale.solaris.part1
http://devtools.sfbay/teams/DeveloperTools_I18N/setuplocale.solaris.part2
Comment 5 tonybeckham 2007-03-29 20:19:14 UTC 
VERIFIED in build 200703271800