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 127397 - I18N - deployed web service has MB chars changed to ???
Summary: I18N - deployed web service has MB chars changed to ???
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Axis2 (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords: I18N
Depends on:
Blocks:
 
Reported: 2008-02-14 14:28 UTC by Jaroslav Pospisil
Modified: 2008-07-11 17:55 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
screenshot (91.16 KB, image/png)
2008-02-14 14:30 UTC, Jaroslav Pospisil
Details
image (54.53 KB, image/jpeg)
2008-07-11 17:52 UTC, kaa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2008-02-14 14:28:31 UTC
pseudo localized Build 200802120006,JDK1.6.0_04,Win Vista

When I deploy web service to Axis server, it has multibyte characters substituted by "?". It causes errors,when I try to
display WSDL or call service's operations.
Comment 1 Jaroslav Pospisil 2008-02-14 14:30:30 UTC
Created attachment 56683 [details]
screenshot
Comment 2 kaa 2008-02-14 16:32:37 UTC
Seems it is server side problem. See:
http://weblogs.java.net/blog/joconner/archive/2005/07/charset_traps.html
Comment 3 Milan Kuchtiak 2008-03-14 13:02:00 UTC
Reported an issue to Axis2 project:
https://issues.apache.org/jira/browse/AXIS2-3607

We cannot do much with this.
Comment 4 Lukas Jungmann 2008-04-11 14:21:53 UTC
v.
Comment 5 Ken Frank 2008-04-11 17:23:03 UTC
jungi,

please bear with my question -

in cases like this when its problem in other s/w, but yet it manifests
when using netbeans, should issue really be verified if its a wontfix ?

and should it stay in some other state that wontfix so we can still track it
easier to test again when the fix happens in other s/w ?

ken.frank@sun.com
Comment 6 Lukas Jungmann 2008-04-21 17:34:52 UTC
I'd say so - verification in this sense, IMO, means that we're sure there's appropriate issue filed against 3rd party
product.

Fixed? - no, we don't have a proper fix for this, issue must be fixed somewhere else
Invalid? - no, issue is valid
Worksforme? - would be strange, issue is there
Later or Remind? - possible options (to be honest - who uses those states appropriately (ie really revisits such issue
later)?)
Wontfix? - yes, because we will not be the ones who will fix the issue. We will be maybe able to deliver the fix by
updating bundled 3rd party product, but the question is when an updated lib with the fix will become available
Comment 7 Ken Frank 2008-04-22 15:50:50 UTC
Jungi,
I think that a fix can be that for axis ws, the wizard could
not accept and warn about use of non ascii  if its a different
wizard than the usual ws one, due to the issue in axis server.

thus in that case this would be a valid issue; at least in past
that is how some similar issues have been handled that were limited
by other s/w as to use of multibyte or non ascii.

if its same wizard as regular nb wizard, then is there any other place
in our own axis module where such a warning can happen ?

Also, for some other areas, the non ascii has been substituted with underscores
due to reasons about browsers and context root - create a web app with multibyte
and can see the subsitution - perhaps that could be done by us as well ?

ken.frank@sun.com

what do you think ?
Comment 8 Ken Frank 2008-05-27 17:27:50 UTC
am reopening this - I realize that the problem itself is from axis server
and issue has been filed - but this does not help our users who might
run into it - can't we provide a warning or not allow use of multibyte
in these cases in a wizard, or do like web apps projects do and change
mbyte to underscores ?

that way, the issue would be solved since user would not run into the server
problem.

changing to p2 just to be consistent with other issues where use of multibyte
causes such problems that user cannot proceed well and/or can't see multibyte correctly.

BTW, what usages of multibyte are a problem - is it in project name or path,
is it in use of mbyte in java code or in some other data or file names/paths ?

Andrey, if this stays open, please track it.

ken.frank@sun.com

ken.frank@sun.com
Comment 9 kaa 2008-06-07 17:03:55 UTC
Сan the issue be fixed for 6.5 timeframe?
Comment 10 Milan Kuchtiak 2008-06-17 13:28:51 UTC
I think, I fixed this issue already.
If a multibyte character is typed for service name, the service name in services.xml is changed using the

URLEncoder.encode(serviceName, "UTF-8"); method.

Though the service node name uses the orginal multibyte character name, the configuration file uses the encoded string :

Example:

This is the services.xml file for "ČSService" service:

    <service name="%C4%8CSService" scope="application">
        <description>ČSService service</description>
        ...
    </service>

Since then, in logical view, there is :]

Axis2 Services
 - ČSService
  - hello
 ...

and the url in browser works fine as well :
http://localhost:8084/axis2/services/ČSService/hello?name=XYZ

That's because browsers change it to :
http://localhost:8084/axis2/services/%C4%8CSService/hello?name=XYZ
Comment 11 kaa 2008-07-11 17:51:48 UTC
checked with Glassfish V2 UR2,
Product Version: NetBeans IDE Dev (Build 200807060002)
Java: 1.6.0_06; Java HotSpot(TM) Client VM 10.0-b22
System: Windows XP version 5.1 running on x86; MS932; ja_JP (nb)

Deployed WebServer with mbyte in name looks without question marks but still encoded.
If this is not expected behavior please reopen.
Comment 12 kaa 2008-07-11 17:52:15 UTC
Created attachment 64349 [details]
image
Comment 13 kaa 2008-07-11 17:55:02 UTC
I meant Web Service above.