[73cat] Re: [Bug 216526] cannot compile web service client when generated on an italian machine
- From: Denis Anisimov <
- To: Michael Müller <
- Subject: [73cat] Re: [Bug 216526] cannot compile web service client when generated on an italian machine
- Date: Wed, 31 Oct 2012 11:59:00 +0400
What Tools do you mean ?
source encoding setting is used only in the editor and (I suppose
) by javac nb ant task .
Any other ant tasks use system default encoding.
Recent XJC version generates java code based on the system default
if "encoding" attribute is not specified.
On 31.10.2012 11:54, Michael Müller wrote:
type="cite">Did I understand right, if setting Source encoding,
some Tools still ignore this settings?
--- Comment #18 from Denis Anisimov
> 2012-10-31 06:47:34 UTC ---
(In reply to comment #17)
Denis, if I got it right the problem is that project specific encoding is not
passed on some command line tool(s). And consequently the command line tool
uses OS default encoding and these files later are causing conflicts as IDE
expects project specific encoding.
Should not the fix be as easy as to instruct
the command line to user project specific
No. I don't see how to fix it in a good way on the WS side.
Only new version of xjc ( or wsimport, wsgen ) has "encoding" attribute.
Build file modification to add this attribute will work only for
recent GF version and won't work for any older.
So this is not a fix.
It could be fixed by forcing system default encoding for sources instead of
At the moment we have inconsistency between system default encoding, which is
by overall IDE (along with ant) and sources encoding which is UTF-8 by default.
It causes the issue and probably will cause issues in the future (any ant task
which uses system default encoding is a source of the issue). I would suggest
to use the same encoding across all IDE.
The other simple solution could be uses sources encoding property as a
system default encoding for ANT infrastructure. But I don't know if it
About this Project