[
https://issues.apache.org/jira/browse/CXF-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768235#action_12768235
]
nicolas de loof commented on CXF-2450:
--------------------------------------
This also affect CXF generated classes as they can derive method / parameter
names from the WSDL (operation and message), potentialy including some non
ASCII characters
The maven convention is to set encoding to ${project.build.sourceEncoding},
most plugins (including compiler) allready follow this best practice
> WSDL2java uses system encoding when generating java classes
> -----------------------------------------------------------
>
> Key: CXF-2450
> URL: https://issues.apache.org/jira/browse/CXF-2450
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.1.3
> Reporter: Mads Jensen
>
> When using wsdl2java java classes are created in default encoding(for
> instance MacRoman). But when we afterwards try to compile these classes in
> UTF-8 special chars in java comments resolves in compliations error
> [INFO] Compilation failure
> /url/to/file/SomeFile.java:[31,18] unmappable character for encoding UTF-8
> We would like somehow to specify which encoding wsdl2java should use when
> generating java classes. We can't seem to find this property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
