I've been trying to track down a problem with Unicode surrogate pairs in our web services, which use XMLBeans. I've tracked an issue down to where xmlText and parse are not idempotent. It looks like attribute values are serialized correctly but element values are not, the "invalid" surrogate pair bytes are replaced with 0x3F, which is the question mark character.
Is XMLBeans performing this substitution? I'm using 2.1.0 but I got the same result when I upgraded to 2.2.0. mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
