XSD from PI in Syndicator - no root element selectable

Hello
I have created a message type in PI and exported the XSD. However when I want to use that XSD in the syndicator no root element is available. Why is that?
I have searched the forums and found that MDM won't show a root element if the XSD is not sane. What part of the XSD is not sane? I have validated it in Liquid XML and it works in the import manager.
Has anyone had the same problem?
BR
/Alexander

Hi,
I also faced same problem. We removed namespace from XSD manually. When u create file from PI it contains namespace.
It worked then !!!!
if still not solved tell me in detail i will give eg ..
Regards
Himanshu
reward if helpful

Similar Messages

XSD from PI in Syndicator

Bonjour
I have created a message type in PI and exported the XSD. However when I want to use that XSD in the syndicator no root element is available.
Any with similar issues.
FV

Heard this in the past try removing namespace from XSD manually or do post more details if this does not work !
Regards,
Raj

XSD from PI does not works in Syndicator.

Hey Guys
I created a data type in PI then made a XSD out of It ,when i try to import that in Syndicator i don't get any root element for it. but if i tweak the XSD just a little bit. it works perfectly in syndicator.
I understand MDM has some limitations in terms of XSD attributes it uses.
The XSD which is imported from PI and does not gives root element is below
<?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns="http://mc.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:complexType name="DT_Sender">
- <xsd:sequence>
- <xsd:element name="Name" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="Description" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
XSD which works is as below
<?xml version="1.0" encoding="UTF-8" ?>
- <xsd:schema xmlns="http://millercoors.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <xsd:element name="DT_Sender">
- <xsd:complexType>
- <xsd:sequence>
- <xsd:element name="Name" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
- <xsd:element name="Description" type="xsd:string" minOccurs="0">
- <xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
The only difference between the 2 XSD's is that in the first one i have element defined as
<xsd:complexType name="DT_Sender">
whereas in the second one i have defined it as
<xsd:element name="DT_Sender">
<xsd:complexType>
Is there some kind of restriction for element definition in XSD for MDM?
Thanks
Saif

Hello Saif,
have a detailed look at your XSDs.
The first one does not define any root element. It contains the definition of a complex type only. But there is no element that is using the complex type "DT_Sender". That is the reason why Syndicator does not show any root element for selection.
The second one is different. This one defines an element "DT_Sender" that consists of a complex type. Now Syndicator is able to show the element.
If you want to use the first definition you have to add an element using the complex type. It could look like:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns="http://mc.com/MDM/CustomerMaster" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="DT_Sender" type="DT_Sender" />
<xsd:complexType name="DT_Sender">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:annotation>
            <xsd:appinfo source="http://sap.com/xi/TextID">56635e00e5a911deaefc0012f0e979b0</xsd:appinfo>
         </xsd:annotation>
      </xsd:element>
      <xsd:element name="Description" type="xsd:string" minOccurs="0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
         <xsd:annotation>
            <xsd:appinfo source="http://sap.com/xi/TextID">56635e01e5a911de8eac0012f0e979b0</xsd:appinfo>
         </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
</xsd:complexType>
</xsd:schema>
Some further tipps and tricks:
1) If you need the xmlns="http://mc.com/MDM/CustomerMaster" in your XML, it makes more sense to add this in the Syndication map properties. There is a field for the namespace where you should paste the http://mc.com/MDM/CustomerMaster part.
2) xmlns:xsd definitions don't have to be mentioned for each element. If you do this in the schema, it's ok.
3) MDM does not handle annotations in the XSD. You can remove them.
So a perfect XSD could look like
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="DT_Sender" type="DT_Sender" />
<xsd:complexType name="DT_Sender">
    <xsd:sequence>
      <xsd:element name="Name" type="xsd:string" minOccurs="0" />
      <xsd:element name="Description" type="xsd:string" minOccurs="0" />
    </xsd:sequence>
</xsd:complexType>
</xsd:schema>
Best regards
Michael

Root Element in Syndicator?

hi All,
I am currently working with MDM Syndicator.
My problem is about Root element
when i am opening in the syndicator file-->destination properties
it will open dialog box with the following options, (i.e. type,Remote system,port,xml schema,xml file name,Root.
when i am selecting type as xml schema , romote system(i.e which i have declared in console for that repository). but when i click on OK button.
it is asking for the Root element required.
can any one help me about:
1)what is root element?
2)where we can declare root element and where we can use it in syndicator?
3)what actually Root element holds in it?
can any please provide answers to this questions
thanks in Advance
Bharat.chinthapatla

Hi Michael,
Thanks for your reply for the pervious question Michael.
But.................?
My Problem is..........
Under Admin in console i have selected XML Schema table and i have created one record with Name as "xml schema file one" and in the filename field i have clicked on the browse button and selected one .xsd file in the repository.
(i have tried with .xml schema file also but not....)
I have opened the syndicator on that particular repository and in the source item i am able to see the table and fields of that particular repository and i have clicked on the file option and i have choosen "Destination properties" it has opened dialog box with different input fields, there i have selected type as "xml schema" and Remote system " MDM "(default). when i selected type as xml schema automatically xml schema input field is enabled and it as shown all the xml schema files or record which i have created in the XML schema table under Admin of the console.
But Root element is not enabled, what i have to do?
In the previous question you have said like this " <b>you have to add an XML Schema to your repository using the <u>corresponding branch</u> in the Console Admin menu</b>.
what is the corresponding branch in the console Admin menu, can you please explain me in details...
if there is any other procedure to come out of this problem, can you please explain me in details ?
Thanks in advance
bharat.chinthapatla

How to remove namespace from root-element

Hi Gurus,
I want one xml output from xslt transformation with no namespace. I managed to remove namespace from child elements by leveraging elementFormDefault ='unqualified' property of xsd. But not able remove namespace from root-element.
Output that I want is :
<?xml version = '1.0' encoding = 'UTF-8'?>
<inp1:Email_Mod_Root>
   <Email_Mod_Root_Element>
      <Email_Record1>
         <PERSON_NUMBER>123456</PERSON_NUMBER>
         <COUNTRY/>
          <EMAIL_TYPE>WORK</EMAIL_TYPE>
         <EMAIL>EMAIL3</EMAIL>
         <PRIMARY_FLAG>Y</PRIMARY_FLAG>
      </Email_Record1>
</Email_Mod_Root_Element>
</Email_Mod_Root>
Output that I am getting:
<?xml version = '1.0' encoding = 'UTF-8'?>
<inp1:Email_Mod_Root xmlns:inp1="http://www.example.org">
   <Email_Mod_Root_Element>
      <Email_Record1>
         <PERSON_NUMBER>123456</PERSON_NUMBER>
         <COUNTRY/>
         <EMAIL_TYPE>WORK</EMAIL_TYPE>
         <EMAIL>EMAIL3</EMAIL>
         <PRIMARY_FLAG>Y</PRIMARY_FLAG>
      </Email_Record1>
</Email_Mod_Root_Element>
</Email_Mod_Root>
Anyone, pls suggest.
Thanks in advance,
SG_SOA

First of all :
<inp1:Email_Mod_Root>
   <Email_Mod_Root_Element>
      <Email_Record1>
         <PERSON_NUMBER>123456</PERSON_NUMBER>
         <COUNTRY/>
          <EMAIL_TYPE>WORK</EMAIL_TYPE>
         <EMAIL>EMAIL3</EMAIL>
         <PRIMARY_FLAG>Y</PRIMARY_FLAG>
      </Email_Record1>
</Email_Mod_Root_Element>
</Email_Mod_Root>
isn't valid xml (you start with inp1: prefix and you end the tag with no prefix, but let's assume you don't want any prefix/namespace at all)
if i use :
[code]
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:inp1="http://www.example.org" exclude-result-prefixes="inp1">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="*">
    <xsl:element name="{local-name(.)}">
      <xsl:apply-templates select="@* | node()"/>
    </xsl:element>
</xsl:template>
<xsl:template match="@*">
    <xsl:attribute name="{local-name(.)}">
      <xsl:value-of select="."/>
    </xsl:attribute>
</xsl:template>
</xsl:stylesheet>
[/code]
i get this
[code]
<Email_Root_Element>
<Email_Record>
<EMPLID>EMPLID46</EMPLID>
<EMAIL>EMAIL48</EMAIL>
<E_ADDR_TYPE>E_ADDR_TYPE49</E_ADDR_TYPE>
<COUNTRY>US</COUNTRY>
</Email_Record>
<Email_Record>
<EMPLID>EMPLID47</EMPLID>
<EMAIL>EMAIL49</EMAIL>
<E_ADDR_TYPE>E_ADDR_TYPE50</E_ADDR_TYPE>
<COUNTRY>US</COUNTRY>
</Email_Record>
<Email_Record>
<EMPLID>EMPLID48</EMPLID>
<EMAIL>EMAIL49</EMAIL>
<E_ADDR_TYPE>E_ADDR_TYPE51</E_ADDR_TYPE>
<COUNTRY>US</COUNTRY>
</Email_Record>
</Email_Root_Element>
[/code]

Multiple Root elements in the XSD Schema

Hi Dear MDM gurus,
I have manually created an XSD Schema and I can import it in the Syndicator without any problem.
I have 3 different Root elements in the schema that I want to use and map to the corresponding table of this type.
In my Syndicator screen in the Rood dropdown box I can see all three of the Root elements that I have in the schema.
If I select the first Root element - everything goes fine and I can do my mapping, save the map, etc.
The problem is that if I select the second or third root element to do the mapping for them, the syndicator does not show the structure in the Item Mapping after that.
I tried moving the Second root element of the schema and make it first and it works with it, but then the other two are not appearing and I have the same issue.
Does MDM support only one Root element in the Schema? If that's the case, why does it show all three of them in the dropdown?
Here is an example:
1. If I have them in this order in my XSD
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
I can only see the structure when I select the "ManufacturerGroupNumber".
2. If I have them in the Schema in this order
          <xs:element name="SupplierLocationNumber" type="Suppliers"/>
          <xs:element name="SupplierGroupNumber" type="SupplierGroupNumbers"/>
          <xs:element name="ManufacturerGroupNumber" type="ManufacturerGroupNumbers"/>
I can only see the structure when I select the first one again "SupplierLocationNumber" and I can only do the mapping for it.
Any help would be appreciated.
Thanks in advance,
Boris

Hello Satish,
Thank you for your quick response.
I read some of the architectural approaches and XML specifications and depending on your design, you may have only one Root element or in rare cases Several Root elements. In my case, I was advised by our PI experts to use Multiple Root elements and this gives me the following:
Advantages:
u2022 The reusability of the schema definition is available for all types and all elements defined in the global namespace.
Disadvantages:
u2022 Since there are many global elements, there are many valid XML documents.
I initially had the schema as you suggested, but they didn't like it in PI and advised me to change it with having multiple roots.
What I'm trying to figure out is if there is a bug in MDM that does not allow to use the rest of the root elements, so I can open an OSS message.
Thanks,
Boris

Unable to find root element in XML Schema when Syndicating (SAP MDM)

Hi experts,
We are having a problem with our Syndication.
We have created an XML Schema using XML Spy. We need a namespace, and this is 70 characters long (in other words, far shorter than maximum at 255 characters).
<xs:schema xmlns:ns="http://schemas.xxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" xmlns:xs="http://www.xxxxx.org/2001/XMLSchema" targetNamespace="http://schemas.xxxxxx.com/ServiceManagement/ServiceMasterDataFromMDM/0.3" elementFormDefault="unqualified" attributeFormDefault="unqualified">
When opening the xml schema file in Syndicator, the root field is disabled.
If we remove namespace in heading of xml schema, the root field is enabled, and the root element is correct.
How can we make use of the XML schema when we need namespace?
We have tried to add namespace annotation ns: to all type definitions:
<xs:element name="ServiceCategory" type="ns:ServiceCategoryType">
This did not help.
Please advice.
KR,
Thomas
Edited by: Thomas on Mar 2, 2011 2:12 PM

>>We need a namespace, and this is 70 characters long
If you want namespace to appear in XML and your XSD has it too. please add the namespace under "URI" attribute in XML schema in Console.
You need to import the XSD in Console first, specify namespace under URI and then use this to build syndication map.
Thanks
Aamir

Root element is missing - Response from a WCF service - WCF-Custom adapter

hi BizTalk experts,
In the production environment, as soon as the response is getting subscribed by the orchestration, the orchestration instance is getting suspended and the error that shows up in console is
"Root element is missing".
I have checked the actual response message in the console it is a well formed xml. This is happening only for a few responses from the WCF services. A majority of them are getting processed successfully. I have tried getting the parsing the response in a
pipeline (using custom pipeline component, the production one uses xml receive) and pass it to the orchestration, but it fails giving the same error.
Thanks in advance.

Do you have any mapping done on the response message from the WCF service . ?
If so Better to copy the suspended message coming from the WCF service and validate against the custom response Schema you have created.
Note : You can try running fiddler tool to check the response from from the web service incase of failure.
Also try logging the message in the event viewer or any debug tool.
Thanks
Abhishek

WSDL incorrect - in XSD elements always must be the root element?

Hi!
First of all, sorry about my english, but I'm not accustomed to write in this language ;-)
We're trying to publish a Webservice with JAXWS and with a classes generated via JAXB parsing a group of XSD files, always in a maven project with java 5.
More explained the steps we are trying to follow:
1) parse the XSD files with JAXB and generate a JAR file to be included like a dependency in the webapp
2) use the classes packaged in the JAR in other maven project and define and deploy a webapp with the webservice using JAXWS defining a SEI that uses and returns a Type included in the JAR generated in the previous step. Here it is the interface that implements the SEI:
@WebMethod
     public TESTELEMENT test(
               @WebParam(name = "test")
               TESTELEMENT element);The problem seems to be that if the elements in the original XSD files aren't root elements the WSDL generated is incorrect.
Here there are the XSD files we are using and the WSDL error result (XMLSpy dixit, "ns1:Example" must refer to an existing element).
Anyone knows what happens?
Thank you in advance and sorry about this large message!
+--- start of TEST.XSD --+
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:include schemaLocation="TEST_TYPE.xsd"/>

<xs:element name="TEST_ELEMENT">
<xs:annotation>
<xs:documentation>Blablabla</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="Example" type="TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>+-- end --+
+--- start of TEST_TYPE.xsd --+
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://example.work/test" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:complexType name="TestType">
<xs:annotation>
<xs:documentation>Example type</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>+-- end --+
+-- start WSDL error --+
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="TestBO" targetNamespace="http://our.package.test/" xmlns:ns1="http://our.package.test/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Example" type="tns:TestType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TestType">
<xs:sequence>
<xs:element name="Element_A" type="xs:string"/>
<xs:element name="Elment_B" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://our.package.test" xmlns:ns1="http://example.work/test" xmlns:tns="http://our.package.test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
<xs:sequence>
<xs:element minOccurs="0" name="test">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
<xs:sequence>
<xs:element minOccurs="0" name="return">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" ref="ns1:Example"/> **
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
<wsdl:message name="test">
<wsdl:part element="ns1:test" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:message name="testResponse">
<wsdl:part element="ns1:testResponse" name="parameters">
</wsdl:part>
</wsdl:message>
<wsdl:portType name="TestBO">
<wsdl:operation name="test">
<wsdl:input message="ns1:test" name="test">
</wsdl:input>
<wsdl:output message="ns1:testResponse" name="testResponse">
</wsdl:output>
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>+-- end --+

Hi again.
About my last post, say that the WSDL generated, in fact, was generated with CXF, sorry.
Using JAXWS (wsgen to be more explicit) the WSDL results still are not ok, as you can see, the error is in the last ns1:Example reference in ServeiTestBO_schema1.xsd, that XMLSpy says that doesn't exists :-( :
+--- ServeiTestBOImplService.wsdl [ServeiTestBOImpl - SEI] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://impl.our.package.test/" name="ServeiTestBOImplService" xmlns:tns="http://impl.our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl/">
<import namespace="http://our.package.test/" location="ServeiTestBO.wsdl"/>
<binding name="ServeiTestBOImplPortBinding" type="ns1:ServeiTestBO" xmlns:ns1="http://our.package.test/">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
    <operation name="test">
      <soap:operation soapAction=""/>
      <input>
        <soap:body use="literal"/>
      </input>
      <output>
        <soap:body use="literal"/>
      </output>
    </operation>
</binding>
<service name="ServeiTestBOImplService">
    <port name="ServeiTestBOImplPort" binding="tns:ServeiTestBOImplPortBinding">
      <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
    </port>
</service>
</definitions>+--- ServeiTestBO.wsdl [SEI interface] ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<definitions targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
    <xsd:schema>
      <xsd:import namespace="http://our.package.test/" schemaLocation="ServeiTestBO_schema1.xsd"/>
    </xsd:schema>
    <xsd:schema>
      <xsd:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
    </xsd:schema>
</types>
<message name="test">
    <part name="parameters" element="tns:test"/>
</message>
<message name="testResponse">
    <part name="parameters" element="tns:testResponse"/>
</message>
<portType name="ServeiTestBO">
    <operation name="test">
      <input message="tns:test"/>
      <output message="tns:testResponse"/>
    </operation>
</portType>
</definitions>+--- ServeiTestBO_schema1.xsd *[with error in the last "ns1:Example"]* ---+
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema version="1.0" targetNamespace="http://our.package.test/" xmlns:tns="http://our.package.test/" xmlns:ns1="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://example.work/test" schemaLocation="ServeiTestBO_schema2.xsd"/>
<xs:element name="test" type="tns:test"/>
<xs:element name="testResponse" type="tns:testResponse"/>
<xs:complexType name="test">
    <xs:sequence>
      <xs:element name="test" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
<xs:complexType name="testResponse">
    <xs:sequence>
      <xs:element name="return" minOccurs="0">
        <xs:complexType>
          <xs:sequence>
            <xs:element ref="ns1:Example" minOccurs="0" maxOccurs="unbounded"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
</xs:complexType>
</xs:schema>
--- ServeiTestBO_schema2.xsd ---
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema elementFormDefault="qualified" version="1.0" targetNamespace="http://example.work/test" xmlns:tns="http://example.work/test" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="TEST_ELEMENT">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="Example" type="tns:TestType" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:complexType>
</xs:element>
<xs:complexType name="TestType">
    <xs:sequence>
      <xs:element name="Element_A" type="xs:string"/>
      <xs:element name="Elment_B" type="xs:boolean"/>
      <xs:element name="Sex" type="tns:SexType"/>
    </xs:sequence>
</xs:complexType>
<xs:simpleType name="SexType">
    <xs:restriction base="xs:string">
      <xs:enumeration value="M"/>
      <xs:enumeration value="W"/>
    </xs:restriction>
</xs:simpleType>
</xs:schema>Thanks in advance again.

Creating root element w/reference to XSD file

I'm using JDOM and would like to know how to create the root element so it
looks like this:
<Import xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://www.mydomain.com/XSDfilename.xsd">

I am trying to create a xml file with then serves as an input to a vendor tool
I tried creating the root element with default namespace but the second elemnt is also created with the default namespace. I am using Jdom to create this xml file .
My program output:
<?xml version="1.0" encoding="UTF-8"?>
<PacketGroup xmlns="http://www.abc.com/schemas/idwebarchive/data">
<DefaultPacket xmlns="" logonid="scott" password="humptydumpty">
<IndexLevel level="1" containerDesc="" containerName="Recorder Docs" />
<IndexLevel level="2" containerName="Recorded Year" containerDesc="">
<Keyword name="Recorded Year" value="2005" />
</IndexLevel>
<DocumentLevel documentName="Documents" docDesc="" >
<Keyword name="Document Number" value="2005-034378" />
</DocumentLevel>
</DefaultPacket>
</PacketGroup>
Vendor REquirement:
<?xml version="1.0" encoding="UTF-8"?>
<PacketGroup xmlns="http://www.abc.com/schemas/idwebarchive/data">
<DefaultPacket logonid="scott" password="humptydumpty">
<IndexLevel level="1" containerDesc="" containerName="Recorder Docs" />
<IndexLevel level="2" containerName="Recorded Year" containerDesc="">
<Keyword name="Recorded Year" value="2005" />
</IndexLevel>
<DocumentLevel documentName="Documents" docDesc="" >
<Keyword name="Document Number" value="2005-034378" />
</DocumentLevel>
</DefaultPacket>
</PacketGroup>
How do I go about creating this structure without the default namespace in my subsequent elements.
Any help is appreciated , I am new to this aspect of programming
Thanks
VK

Document root element is missing: migrating spring app from tomcat

Hi!
can anybody help me with this issue?
I have ported my tomcat spring application to netweaver(6.40, SP 17, Windows 2k SP4) and i get the following error:
Error occured in invoking event "contextInitialized()" on listener clas
s com.webapp.listener.StartupListener. The error is: org.springfram
ework.beans.factory.BeanCreationException: Error creating bean with nam
e 'sessionFactory' defined in ServletContext resource [/WEB-INF/applica
tionContext-hibernate.xml]: Initialization of bean failed; nested excep
tion is org.hibernate.MappingException: Could not parse mapping documen
t in input stream
org.hibernate.MappingException: Could not parse mapp
ing document in input stream
     at org.hibernate.cfg.Configuration.addIn
putStream(Configuration.java:430)
     at org.springframework.orm.hibernat
e3.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.j
ava:654)
     at org.springframework.beans.factory.support.AbstractAutowir
eCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactor
y.java:1059)
     at org.springframework.beans.factory.support.AbstractAut
owireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.j
ava:363)
     at org.springframework.beans.factory.support.AbstractBeanFac
tory.getBean(AbstractBeanFactory.java:226)
     at org.springframework.bea
ns.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java
:147)
     at org.springframework.beans.factory.support.DefaultListableBea
nFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:269)
     at org.springframework.context.support.AbstractApplicationContext.ref
resh(AbstractApplicationContext.java:320)
     at org.springframework.web.
context.support.AbstractRefreshableWebApplicationContext.refresh(Abstra
ctRefreshableWebApplicationContext.java:134)
     at org.springframework.w
eb.context.ContextLoader.createWebApplicationContext(ContextLoader.java
:246)
     at org.springframework.web.context.ContextLoader.initWebApplica
tionContext(ContextLoader.java:184)
     at org.springframework.web.contex
t.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:4
9)
     at com.ifx.webapp.listener.StartupListener.contextInitialized(Star
tupListener.java:42)
     at com.sap.engine.services.servlets_jsp.server.r
untime.context.WebEvents.contextInitialized(WebEvents.java:45)
     at com
.sap.engine.services.servlets_jsp.server.container.ApplicationThreadIni
tializer.run(ApplicationThreadInitializer.java:112)
     at com.sap.engine
.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.sec
urity.AccessController.doPrivileged(Native Method)
     at com.sap.engine.
core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.
sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
C
aused by: org.dom4j.DocumentException: Error on line 1 of document : D
ocument root element is missing. Nested exception: Document root elemen
t is missing.
     at org.dom4j.io.SAXReader.read(SAXReader.java:482)
     at
org.hibernate.cfg.Configuration.addInputStream(Configuration.java:421)
     ... 18 more
And yes, the xml files are valid xml files at least in anything i've used to look at them (eclipse, ultraedit, notepad, ie) :).....
Thank you!
ps. the file:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
    "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
    
    <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
        <property name="dataSource" ref="dataSource"/>
        <property name="mappingResources">
            <list>
                <value>package/ModelObj1.hbm.xml</value>
                <value>package/ModelObj2.hbm.xml</value>
            </list>
        </property>
        <property name="hibernateProperties">
            <props>
                <prop key="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</prop>
            </props>
        </property>
    </bean>
    
    <bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
    
    <bean id="dao" class="com.dao.hibernate.BaseDAOHibernate">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
</beans>

hi istvan,
we are also migrating from websphere to netweaver.
But in spring framework we r facing problems.
We hav spring-beans.jar file in lib dir of Web Application. But When we are creating BeanFactory from xml as,
BeanFactory beanFactory = new ClassPathXmlApplicationContext ("client-config.xml");
clent-config.xml file contains :
[code<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
     <bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" >
          <property name="location">
               <value>conf/service-client/client.properties</value>
          </property>
     </bean></beans>
[/code]
But code is giving exception: ClassNotFoundException -org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.
Wat is the problem ?
Kindly help.
We are also using JAAS for authentication.We are refering above code from our LoginModules login() method.
Regards,
sagar.

Getting Error in java mapping: Parsing empty source. Root element expected!

Hi Experts,
   I am using java mapping for schema validation of input message. I have followed all the standard procedures and implemented the java class in the interface mapping.
My interface mapping is like this:
OrderData --->Java Class ---SchemaValidate
                     Mesg Map ---OrderData_to_BAP --->BAPI Msg
So first I want to validate the schema of the input message. If the input message is invalid then XI should throw an exception. Then I use the actual message mapping to map the input order data to the BAPI input parameters.
In the java code I am using xerces parser.
The java code works fine when I run it as a standalone application.
The interface mapping also works fine if I don't include the java mapping. Ofcourse schema validation does not happen.
But when I test the interface mapping by including the java mapping then I am getting the error:
Call method execute of the application Java mapping SchemaValidate
Java mapping SchemaValidate completed. (execute() of SchemaValidate
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected!
What am I doing wrong? Why it is not getting the root element?
My Java code is as follows:
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import com.sap.aii.mapping.api.StreamTransformationException;
import java.io.*;
import java.util.Map;
import javax.xml.parsers.*;
import org.xml.sax.helpers.*;
import org.xml.sax.*;
import org.apache.xerces.jaxp.*;
Sample mapper for SAP-XI
@author Gopal
public class SchemaValidate implements StreamTransformation {
    //Constants when using XML Schema for SAX parsing.
     static final String JAXP_SCHEMA_LANGUAGE =
     "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
     static final String W3C_XML_SCHEMA =
     "http://www.w3.org/2001/XMLSchema";
     static final String JAXP_SCHEMA_SOURCE =
     "http://java.sun.com/xml/jaxp/properties/schemaSource";
Injection of mapping parameters
from integration engine
@param map Map with configuration data
    public void setParameter(Map map) {
Mapping implementation
@param inputStream Input data from integration engine
@param outputStream Output data to integration engine
    public void execute(InputStream inputStream,
                        OutputStream outputStream)
      throws StreamTransformationException {
        try {
              // obtain an object of class javax.xml.parsers.SAXParser,
              SAXParserFactory spf = SAXParserFactoryImpl.newInstance();
              spf.setNamespaceAware(true);
              spf.setValidating(true);
              SAXParser sp = spf.newSAXParser();
              // setup the schema file
              sp.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
              sp.setProperty(JAXP_SCHEMA_SOURCE, new File("IOReqMsgSchema.xsd"));
              //parse the input xml using the given schema
              sp.parse(inputStream, new ParseErrorHandler());
        catch(SAXException se) {
          se.printStackTrace();
        catch ( Exception e ) {
          throw new StreamTransformationException( e.getMessage() );
My input message is :
<?xml version="1.0" encoding="UTF-8"?>
<ns0:OrderCreate_request xmlns:ns0="mynamespace">
   <ORDER>HTEST1234567</ORDER>
   <ORDER_TYPE>z001</ORDER_TYPE>
   <ORDER_NAME>Test Order</ORDER_NAME>
   <CO_AREA>INTC</CO_AREA>
   <CCTR_POSTED>1234567890888888888</CCTR_POSTED>
   <CURRENCY>USD</CURRENCY>
   <PERSON_RESP>12345679</PERSON_RESP>
</ns0:OrderCreate_request>
Kindly help! please this is urgent!!!!!!
Thanks
Gopal
Edited by: gopalkrishna baliga on Feb 28, 2008 9:34 AM

Hi Stefan,
   I did the code changes to return output stream and the java code works perfectly in standalone mode in my PC.
   But when I use the same in the Java mapping with XI then It throws an error "Getting Error in java mapping: Parsing empty source. Root element expected!".
My XI J2EE server has JDK1.4.3.11.
Is there any limitation of using SAX parser in XI? If Yes, then which parser should be used for schema validation in XI?
I have included the XSD file for schema validation along with class files in the .jar file. This jar file is then imported in XI repository. Is the XI engine not able to read the XSD file?
Do I have to handle reading XSD file differently? Any suggession how?
Is this parser error due to some security access?
Kindly help me! I have been struggling with this problem since 2 weeks. I will be greatfull to you if you can help me.
Thanks
Gopal

Root element required

SDNers,
I have created a message type in XI and have exported the XSD. When I try to import the XSD in the syndicator, I get an error message: Root element required.
Thanks in advance.
+ JT

Hi Jolin,
If u can share the solution as we have faced same problem.
Rgds
Ankit

Root element charts not defined in schema error??

My xsd file is
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://www.datastay.com/schema" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:target="http://www.datastay.com/schema">
     <xs:element name="time" type="xs:positiveInteger" default="1"/>
     <xs:element name="timeType" default="weeks">
          <xs:simpleType>
               <xs:restriction base="xs:string">
                    <xs:enumeration value="days"/>
                    <xs:enumeration value="weeks"/>
               </xs:restriction>
          </xs:simpleType>
     </xs:element>
     <xs:element name="refresh">
          <xs:complexType>
               <xs:all>
                    <xs:element ref="target:time"/>
                    <xs:element ref="target:timeType"/>
               </xs:all>
          </xs:complexType>
     </xs:element>
     <xs:element name="query">
          <xs:complexType>
               <xs:simpleContent>
                    <xs:extension base="xs:string">
                         <xs:attribute name="series" type="xs:string" use="required"/>
                    </xs:extension>
               </xs:simpleContent>
          </xs:complexType>
     </xs:element>
     <xs:element name="chartDefinition">
          <xs:complexType>
               <xs:all>
                    <xs:element ref="target:refresh"/>
                    <xs:element ref="target:query"/>
               </xs:all>
               <xs:attribute name="id" type="xs:ID" use="required"/>
               <xs:attribute name="title" type="xs:string" use="required"/>
               <xs:attribute name="type" type="xs:string" use="required"/>
               <xs:attribute name="xaxislabel" type="xs:string" use="required"/>
               <xs:attribute name="yaxislabel" type="xs:string" use="required"/>
               <xs:attribute name="classType" default="com.dms.chart.DefaultChartBusinessHandler">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:enumeration value="com.dms.chart.DefaultChartBusinessHandler"/>
                              <xs:enumeration value="com.dms.chart.PieChartBusinessHandler"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:attribute>
               <xs:attribute name="width" type="xs:int" default="500"/>
               <xs:attribute name="height" type="xs:int" default="500"/>
               <xs:attribute name="chartColor" type="xs:string" default="#FFFFFF"/>
          </xs:complexType>
     </xs:element>
     <xs:element name="charts">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="target:chartDefinition"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>
My xml file is
<?xml version="1.0"?>
<charts xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\Tomcat4\webapps\chart\WEB-INF\files\chartdefs.xsd">
<chartDefinition id="1" title="Monthly Logins" type="verticalbar3d" xaxislabel="Month" yaxislabel="Logins" classType="com.dms.chart.DefaultChartBusinessHandler" width="500" height="750" chartColor="#FFFFFF">
<refresh>
<timeType>
minutes
</timeType>
<time>
1
</time>
</refresh>
<query series="john">
          select * from defaultchart where name = 'john'
</query>
<query series="max">
          select * from defaultchart where name = 'max'
</query>
</chartDefinition>
<chartDefinition id="2" title="Average Workflow life span" type="pie3d" xaxislabel="Workspace" yaxislabel="Days" classType="com.dms.chart.PieChartBusinessHandler" width="500" height="500" chartColor="#FFFFFF">
<refresh>
     <timeType>
minutes
</timeType>
     <time>
5
</time>
</refresh>
<query series="john">
     select * from defaultchart where name = 'mike'
</query>
</chartDefinition>
</charts>

Copy the schema and the XML document to the same directory.
The root element of the XML document specifies the location of the schema.
<?xml version="1.0"?>
<charts xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="chartdefs.xsd">The xs:schema element:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">

Root element required error in syndication

Hi,
We have added few new fields into the main table. Now accordingly we need to update the Oubound map to include these new fields. I have created a new XSD file having these new fields. But when I try to use this in syndicator to update, it throws me an error back saying "Root element required". I checked in SDN but couldnt find enough clues.
Any pointers will be highly appreciated.
Regards,
Ponraj M

Hello,
There are few possible root causes to this error appearing in MDM Syndicator:
1. This error indicates that the XSD is not valid as there is no declaration of the root element.
If you try to validate this XSD in XMLspy you will receive a similar error.
2. The XSD declares the root element but it does not appear in the XML.
If you validate the XML against the XSD in XMLspy you will receive a similar error.
3. An illegal character in the XSD root element declaration makes it impossible for Syndicator to detect it.
Please check these possible causes.
Best regards,
Hedda Cohen.

XSD from PI in Syndicator - no root element selectable

Similar Messages

Maybe you are looking for