We are upgrading our xmii 11.5 to 12.0. All interfaces are working properly except for one which returns an xml document to a custom j2ee system. This particular interface is having difficulty parsing the xMII xml. When we point it back at the exact same interface in 11.5 it works, in 12.0 it doesn't. The only obvious difference I can see is the new system is unicode. Calling the exacute program from an IE browser with the exact same string as is in the app yields beautifully formatted xml.
We have suspicions that this is due to a UTF-9 BOM (Byte Order Mark) not being interpreted properly by the recieving program. We can't see the BOM with notepad or even using od -a in UNIX but we assume it is there, the parallels to this known java limitation are extensive. As IE does not have this limitation, the xml renders fine in the browser.
Has anyone experienced this issue with xml returns from unicode XMII 12.0 or older?
In this instance it would be wonderful if I could send the file ast UTF-16 instead to avoid the whole issue but we can't figure out how to force that to happen.
Regards,
Phillip
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.