xml xsd namespace troubles with MDM Import Manager

[Former Member]

Hello everybody,

I have some troubles during the import of an xml file using import manager of mdm5.5sp5p1.

I defiened a client system and an inbound port and stored the following xml schema (xsd file):

<?xml version="1.0" encoding="UTF-8"?>

<!W3C Schema generated by XMLSpy v2007 (http://www.altova.com)>

I get the following error:

Logon Error: Cannot load XML file.

Error:

COM error 80004005 Unspecific error

Source = msxml4.dll Descreption = file:///C:/DOCUME~1/.......xsd#/schema[1]

The " namespace provided differs from the schema's 'http://..._mdm_for_chemicals' targetNamespace.

I created the xsd file by using XMLSpy.

Can you please tell me what is wrong with my xml schema?

thanks in advance

René

[Former Member · Accepted solution]

Hi Michael,

Sorry for the missing underscore. This was my mistake when I shortened the namespace-string in order to get the post clearer. In the original files the namespaces are the same.

Kind Regards,

René

[michael_theis · Accepted solution]

Hi Rene,

OK that explains it. Question: when adding the XSD in Console, did you enter your Namespace in the "URL" field? This field should be used if you have a NS within your XSD and XMl messages.

BR Michael

[Former Member]

Hi Michael,

thanks a lot. I added the URI in the XML Schema Definition and now it works.

Kind Regards,

René

[michael_theis]

Hi Rene,

th ereason is most probably that your defined xmlns differs from the targetNamespace in your XSD. Using Altova MXL Spy I'm unable to validate your XML against your XSD. I'd suggest to check the schema definition of your XSD:

<xs:schema xmlns="http://..._mdm_for_chemicals" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://...mdm_for_chemicals">

The definition has a leading underscore in the NS, the target NS has no leading underscore. Setting both to the same value, I'm able to validate your XML (but I did not check in IM / MDIS).

Edit:

choosing XML instead of XML Schema for a port does not validate your XML against the XSD during import!

BR Michael

[Former Member]

Hello,

I solved the problem. The mistake was in the definition of the port. In the port details, I chose XML Schema instead of XML.