You can start JBoss with the file.encoding parameter
Be careful when doing this because you will treat all files as UTF-8-encoded if nothing else is given. OK, I haven't had any problems doing this on all our servers, but it is worth an extra note.
The file encoding didn't work out that well since everything else broke ;-)
Well, now the wsdl file is correctly UTF-8 encoded but the problem seems to be a JBossWS_remote._24540.xsd (schema validation?). The file has the original iso-8859-1 chars and no encoding info -> tilt.
Is there any way of hinting the encoding for the .xsd? Sure, I could strip the entities from all non-utf chars but since they are quite central that would lead to refactoring everywhere so if there is I a workaround, I'm more than happy to listen.
Any theories as to why the wsdl file is correctly encoded but the .xsd is not? Since they both are generated from the same information, one would assume the encodings would match(?)