XSD encoding

[anthony_scholtz2]

I am uploading an XSD into an external definition. In the XSD the encoding is specified as UTF-8. In the external definition it has changed to ISO-8859-1. This seems to be messing up my output XML. Any ideas on why and how the encoding changed from XSD to external definition? Is this a setting somewhere?

Regards

Anthony

[Former Member]

If re-export the imported external definition, the output file will have UTF-8 only. So, its only the display its showing like that. But i never faced any problem with this before. May be I havent tested any international characters but even i'm not sure why the display is like that.

[Former Member]

Hi Anthony,

the change of the encoding is only for display purposes. Internally the original XSD is still used. Therefore, I cannot imagine that your problems result from this. Can you more precisely describe the problems you face.

Greetings

Stephan

[anthony_scholtz2]

Hi Stephan

I checked and see that it is only used for display. The problem I'm having is this:

The sample XML from my partner looks like this:

<cmt:Store>

<cmt:AddressLine1>1 main street</cmt:AddressLine1>

My generated XML looks like this:

<ns0:Store>

<ns0:AddressLine1>1 main street</ns0:AddressLine1>

In the tags cmt has changed to ns0.

The XSD starts like this:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:cmt="http://www.trimble.com/tms/XMLSchema/1.0" xmlns:exds="http://www.trimble.com/tms/XMLSchema/ExtendedDataSchema/2.0" targetNamespace="http://www.trimble.com/tms/XMLSchema/1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">

Hope this helps.

Anthony

[Former Member]

the ns0 / nsX style of coding is what's generated by default, it still references the correct namespace from the URI you specified. i.e. it's just standard XML markup. Your XML processor at the remote end should still suck it in just fine as the tags are in effect just variables that point to the URI's specified elsewhere. If it is not being processed correctly at the remote end then check your data (run it through a validator like xmlspy), or the remote system could be failing to recognise the URI's you specified (you havnt referenced their schemas correctly on the remote system).

If you need to change the ns0 to cmt etc, you may be able to use XSLT or the anonymiser bean to change this but I've never had any need to so I cant say for sure.

[anthony_scholtz2]

Thanks James. I'll get my partner to run it through there parser and see what happens.

[Former Member]

Hi Anthony,

If our exporting XSD which UTF-8 then it will be UTF-8 in external def. please check our XSD while uploading.

Thanks

Sreeram