Actually I think this is a JBossWS (installer) bug ?
The WSDL and Soap headers default to UTF-8, but the characters sent are in the machines java default encoding!
I did a "hot fix" to add the system property
to the jvm running JBossWS, thus changing the default file !? encoding
of the complete jboss installation. Afterwards UTF-8 handling worked
as expected (before that jbossws 1.2 used the default file encoding of
the installation (was iso latin 1 on my machine)
Has anyone found the correct way to configure the file encoding of
I actually tried that too, but it didn't work for me, here's the jboss process running on my linux box..
340 pts/0 Sl 1:10 /usr/java/jdk1.5.0_11/bin/java -Dprogram.name=run.sh -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dfile.encoding=UTF-8 -Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n -Djava.endorsed.dirs=/var/www/jboss/lib/endorsed -classpath /var/www/jboss/bin/run.jar:/usr/java/jdk1.5.0_11/lib/tools.jar org.jboss.Main
Shouldn't there be some way to configure the output encoding for each webservice?
Well, it should work then (solved my problems, though).
Actually make sure that your console will handle UTF-8 correctly, alternatively you might want to direct the output into a file and check it with an editor/hex editor of your choice, or generate a html file to check it with a web-browser. (is much easier than configuring an arbitrary linux console to show utf-8 :-)
It looks like you have a space between the - and D character in -Dfile.encoding...
have you find the solution ? please