SRE Decode Method: Issues With Special Characters
Last updated on DECEMBER 01, 2017
Applies to:Sun Schema Runtime Environment (SRE) - Version 5.0.5u1 and later
Information in this document applies to any platform.
***Checked for relevance on 21-August-2013***
When unmarshaling the string with special characters, it truncates at the point where special character begins. The base64 encode-decode method in SRE 5.0.5 U1 doesn't unmarshal the data with special characters.
Using base64 encode and decode in collaboration rules. For strings with special characters (accent marked characters) such as "PreStringPEÑAPostString" the base64 encode works but the base64 decode does not - it truncates at the point where the special character is in the string such as "PreStringPE"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms