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 5.5 Dev (Build 200606090200) Operating System = Windows XP version 5.1 running on x86 Java; VM; Vendor; Home = 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-b02; Sun Microsystems Inc.; F:\Java\jdk1.5.0_07\jre System Locale; Encoding = en_US (nb); Cp1252 -- i've created web app with glassfish as j2ee server (source level 1.5) created new web service with mbyte char (とserive) in its name built/deployed project and invoked "test service" on とservice it couldn't be acessed - in http monitor there were ? instead of mbytes in glassfish admin console everything looked ok - but when i tried test service from there - same problem occured.
See the GlassFish bug : https://glassfish.dev.java.net/issues/show_bug.cgi?id=751
I fixed the service uri calculation to use the URLEncoder : Diff: http://websvc.netbeans.org/source/browse/websvc/core/src/org/netbeans/modules/websvc/core/jaxws/nodes/JaxWsNode.java?r1=1.1.2.36&r2=1.1.2.37 The rest depends on GlassFish
Are these other observations related to this issue (or the gf one) or should separate issue be filed. 1. assuming the ws name is english, if the WebMethod name has mbyte, like とSayHi, then browser reports it can't be found - web page says "cant find method とSayHi (when using tester) also, on the main tester page, the mbyte part of SayHi word shows a ?, not the real mbyte - the web page encoding in browser is set to iso8859, not utf8 or that of the locale (ja) but even if set to these, that mbyte does not show ok, although other mbyte does. 2. even if the SayHi does not have mbyte as part of its name, if mb is used in tester as the value, and then click the SayHi button, the next web page does not show the value correctly as to the mbyte and still causes browser to be in iso8859 encoding and gives exception. even when browser encoding changed to that of locale, the exception still shows even though the mbyte of the value shows ok. see 2 attached gifs. ken.frank@sun.com
Created attachment 31709 [details] image
Created attachment 31710 [details] image
Works fine with build 20060904000 and glassfish ur1.
So I consider this as fixed.
Verified NB part.