If a Procedure Step Action Diagram Description contains DBCS characters the generated WSL file fails to open after deployment to Axis and the user will receive an error of the form:
Sorry, something seems to have gone wrong... here are the details:
Fault - ; nested exception is:
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
DBCS characters are supported in the generated Proxy XML .xsd file (with PTF GEN80010/RO26563 applied). However the Web Service Wizard (WSW) Plug-in which creates the .wsdl from the .xsd file only supports single byte file I/O and this results in any DBCS characters being corrupted in the generated .wsdl file.
To enhance the WSW to support DBCS characters is not something that is feasible with a PTF and so this problem will be addressed in a future release.
- Remove DBCS/NLS characters from the Procedure Step Action Diagram Description in the model prior to generation of the Proxy with XML option.
- Remove DBCS/NLS characters in documentation tag in the generated .xsd file before generating the .wsdl with the WSW plug-in.