After adding a XML schema to the catalog, I wanted to display it to ensure that no errors ocurred. But the following error appears:
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
could you sent us the schema you used?
Also how did you open it for viewing? Did you click on the schema name in the summary profile of the asset or did you use a different way? If you could give us the exact version (about dialog) you are using that might help us as well.
I use the same version and can display the imported schema correctly.
Please see the attached screenshot.
What browser version are you using and which locale is your operating system?
Daniel:
I send you a word document with 2 screenshots: one showing the view where I start and the other, where the error appears.
While I’m writing this message, I’m thinking that the cause of this problem probably has to do with certain encoding or character set configured in CentraSite, because there’s no reason (apparently) by wich I can’t see the schema and you can since both we use the same version.
Hi Diego,
Daniel basically wanted you to set the following entries:
Language: English
Locale: English (United States)
and see if the error still occurs.
Hi Diego,
I think I’ve found the reason for the error, but do not yet know why this is happening.
The problem is that this file is encoded in UTF16, but when you read it back (error.xml actually contains the contents), the BOM (Byte Order Marker) is not present. This causes problems for Internet Explorer (Firefox handles this). In my environment the BOM is within the file in CentraSite, but seems to be lost on retrieval for you.
I’ve enclosed XML Schema file encoded as UTF8 - could you import this and see if this solve your problem?
If this does solve it, then you have a workaround.
R&D need to do some investigation how/why this is happening - its going to be interesting to find…
As you told, the problem has to do with encoding used in a XML file. I encoded it to UTF-8 as you asked me, and…voila! it works!
It would be interesting to know why this happens and, of course, if it possible to solve it because all (or at least, many) of our XML schemas are codified in UTF-16 wich is the natural way that Microsoft Biztalk does.
