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

Similar Messages

  • Read XML response with multiple root elements

    Hi ,
    I am trying to achieve the below scenario but unable to do so.Please help urgently.
    I am getting a response from a service which has multiple root elements.these root elements can change at runtime..I need to read the different root elements and extract data from its sub elements.
    Regards...
    Hoping for an anwser..

    i assume on runtime the service just returns 1 rootnode, but this rootnode can change
    you could use a switch after the invoke
    if $response/myroot1
    assign $response/myroot to myroot1_var
    if $response/myroot2
    assign $response/myroot to myroot2_var
    etc
    so you check what's in the root node before you assign to you temp variable
    or if you have logic which is specific based on this root nod you can just implement all these branches in the switch and execute logic in there based on the selected rootnode
    several implementations are possible

  • PCO 2.1 Error : there are multiple root elements Line 6, position 2

    HI all,
    I am getting an error while adding Destination for Notification.
    On the Destination Tab, I am able to create MII System as Destination. And expanding the newly created Destination, i can see a child node 'Destination'. While clicking on this child node, i am getting an error as "there are multiple root elements Line 6, position 2"
    Can anybody please help.
    Regards
    Muzammil

    Hi,
    While configuring MII Server details, instead of IP address of MII server, we gave domain name and it started working.
    Regards
    Muzammil

  • Error in WebServices Consumption - There are multiple root elements

    hi,
    I am working on consuming webservice which has a WSDL to get the RouteDetails with a structure like:
    <Source>
    <HouseNumber>1</HouseNumber>
    <Street>XYZ</Street>
    <City>Hyderabad</City>
    <Country>India</Country>
    <PostalCode>500018</PostalCode>
    </Source>
    <Destination>
    <HouseNumber>2</HouseNumber>
    <Street>X1Y1Z1</Street>
    <City>Bangalore</City>
    <Country>India</Country>
    <PostalCode>500067</PostalCode>
    </Destination>
    When I am calling the method RouteDetails of the proxy I created, I am getting the error 'There are multiple root elements in line 1 column 178 and the column is indicating <HouseNumber> in <Destination> node.
    Please let me know how to overcome this.
    Thanks for the help
    Githa

    Its now resolved. Thanks,
    Githa

  • Hello Anybody, I have a question. Can any of you please suggest me how to make an xml file from the database table with all the rows? Note:- I am having the XSD Schema file and the resulted XML file should be in that XSD format only.

    Hello Anybody, I have a question. Can any of you please suggest me how to make an xml file from the database table with all the records?
    Note:- I am having the XSD Schema file and the resulted XML file should be in that XSD format only.

    The Oracle documentation has a good overview of the options available
    Generating XML Data from the Database
    Without knowing your version, I just picked 11.2, so you made need to look for that chapter in the documentation for your version to find applicable information.
    You can also find some information in XML DB FAQ

  • How to permit multiple workspaces to access the same schema?

    Hello,
    When creating a new workspace (version 3.2), I am getting the following warnings:
    "Warning: The requested schema already exists. Warning: The requested schema is already assigned to one or more workspaces. Please ensure that giving multiple workspaces access to the same schema is permitted by the security policies at your site before approving this request."
    How do I "ensure that giving multiple workspaces access to the same schema is permitted"?
    What are the advantages/disadvantages of doing so?
    Thanks,
    Gabor

    The correct answer to it would have been: I use manual provisioning.I didn't ask a detailed enough question. What I am wondering is how you are set up to to workspace provisioning at your site. In apex_admin, if you navigate to Home>Manage Service>Instance Settings there is a radio group like:
    Provisioning Status:      
    0 Manual - An administrator manually creates each workspace
    0 Request - Link displayed on login page enabling users to request workspaces
    0 Email Verification - Workspace created after email address is verified by the user
    The help text for this is:
    Provisioning Status:      
    Determines how the process of provisioning (or creating) a workspace works for your development instance. Options include:
        * Manual - An Application Express administrator manually creates new workspaces and notifies the Workspace administrator of the login information.
        * Request - Users request workspaces directly in a self-service fashion. Selecting this option displays a link on the Login page enabling users to request a workspace. When a user requests a workspace, each request is submitted to a queue for approval.
        * Email Verification - Works similar to Request except each user receives an initial email containing a link. Clicking this link validates the user's email address before the request is processed.
    Note: To enable users to request a workspace using a link on the Login page, you must choose Request or Email Verification. If you select Manual, no link appears on the login page.How is yours set up?
    As to the first original question (How do I "ensure that giving multiple workspaces access to the same schema is permitted"?), I still do not know.Whether it is permitted or not is a decision made by the apex site administrator who approves/declines workspace requests. Whether it ought to be permitted is a different question and is really same as your second question which involves issues you said you are now starting to understand better. So I think we've covered your original questions. If not, please elaborate.
    As to the last subject (How did the hidden workspace get created and how do I get rid of id? What happens if I don't?), this happened at work, so I can only tell you more on Monday (luckily...). Until then, here is what I remember. The work space was created, which is proven by the fact that when I want to create a new workspace with the same name, I am getting an error, which says that a workspace with that name already exists. However, I cannot delete the workspace, since it show up nowhere.No hidden workspace got created. I'm pretty sure the request is just in the queue waiting to be approved/declined. In the meantime a workspace with the same name cannot be requested.
    By the way, how do you quote some text here? I just put a '>' in the first character position before the text to quote. You can also use the " rich text icon above the text pane.
    Scott

  • How to map multiple output values to the output schema in biztalk mapper?

    Hi,
    In my biztalk mapper, I am using a "database lookup" functoid which is linked to a "Value Extractor" functoid. A source schema field is linked to the database lookup functoid which is linked to a "Value Extractor" functoid
    which is linked to the destination schema field. After passing the required parameter values in the database lookup functoid (lookup value, conn string, table, column name), I know that the result set may get multiple rows which are transferred to the "value
    extractor" functoid.
    Now what I want is to create a record in destination schema for each row in the result set. My current mapping is as below:
    1) Source record > looping functoid > destination record
    2) Source record field > Database functoid > Value Extractor functoid > dest record field
    but this mapping is giving me only the first value in result set.
    Please help me in this so that my map creates a destination record for each value in the result set.
    e.g. if query [select * from employees where surname='Brown'] returns five records, then I would like five records in the destination schema.
    Thanks
    manibest

    Hi Muhammad Ehsan,
    Thank you for the useful suggestion. however, I have only one difficulty in building your suggested solution. in my query  (select
    * from employees where surname='Brown'), the value of surname is coming from the source schema field which could be different in each source schema record field.
    lets say that source schema instance has 3 records in it as below:
    <Records>
    <Record><Surname>Brown<Surname></Record>
    <Record><Surname>Atkinson<Surname></Record>
    <Record><Surname>White<Surname></Record>
    </Records>
    For each of above records the database query should run with the relevant surname value. if database has 5 records for "Brown", 3 records for "Atkinson" and 1 record for "White" then the destination schema should create (5+3+1) = 9 records in
    total.
    To create a destination canonical schema that works fine, I have to somehow pass this surname value from source schema as parameter so that it uses this value to poll the database and get records. Is there a way I can pass this surname value as parameter
    to the destination canonical schema? Thank you so much for the help.
    manibest

  • Namespace Prefix in the Root Element of the variable

    Hi Gurus,
    We need to call a webservice which requires a namespace prefix at the root elemnt of the xml payload. But as we know that the default behaviour of BPEL removes the prefix so the invoke activity is failing and so we are stuck.
    I found this thread Namespace prefix in Root element missing during variable assignment but i feel the solution specified in this link works only in SOA 10g environment Please let us know what needs to be done?
    Appreciate a prompt response.
    NOTE: SOA Suite Version- 11.1.1.4
    Regards
    Ayush

    Hi All,
    we are also facing the same issue, Please provide the solution if anyone knows. We are also using the SOA Suite 11g Version.

  • Drag and Drop Multiple Pictogram elements from the Palette

    I have created custom Objects in the palette that can drag and drop individual pictogram elements using a class that extends AbstractAddFeature. What I would like to know if it is possible to drag and drop an item from the palette that contains multiple pictogram elements, such as task1, task2 and a connection between them? I cannot do this with my class from above since
    @Override
    public PictogramElement add(IAddContext context) {}
    only returns one PictogramElement.

    Hi,
    In my editor I am adding rectangle with associated label that are separate pictogram elements. However they are both linked to the same business object and more linked to each other.
    Please look at example from my code:
    @Override
    public PictogramElement add(IAddContext context) {
    final Task addedTask = (Task) context.getNewObject();
    final ContainerShape target = context.getTargetContainer();
    final IPeCreateService peCreateService = Graphiti.getPeCreateService();
    final IGaService gaService = Graphiti.getGaService();
    final ContainerShape containerShape = peCreateService.createContainerShape(target, true);
    int width = 0;
    int height = 0;
    width = context.getWidth() <= 0 ? getWidth() : context.getWidth();
    height = context.getHeight() <= 0 ? getHeight() : context.getHeight();
    final Rectangle invisibleRectangle = gaService.createInvisibleRectangle(containerShape);
    gaService.setLocationAndSize(invisibleRectangle, context.getX(), context.getY(), width, height);
    // create and set visible rectangle inside invisible rectangle
    RoundedRectangle roundedRectangle = gaService.createRoundedRectangle(invisibleRectangle, 20, 20);
    roundedRectangle.setParentGraphicsAlgorithm(invisibleRectangle);
    roundedRectangle.setStyle(addedTask.isOnlyLocal() ? onlyLocalStyle : getStyle());
    if(!addedTask.isAtomic()) roundedRectangle.setLineStyle(LineStyle.DOT);
    gaService.setLocationAndSize(roundedRectangle, 0, 0, width, height);
    insertInside(peCreateService, gaService, width, height, containerShape, invisibleRectangle, addedTask);
    ContainerShape labelShape = addLabel(target, addedTask.getId(), width, height, context.getX(), context.getY());
    link(containerShape, new Object[] {addedTask, labelShape});
    link(labelShape, new Object[] {addedTask, containerShape});
    updatePictogramElement(labelShape);
    layoutPictogramElement(labelShape);
    addInternalPorts(addedTask, containerShape);
    updatePictogramElement(containerShape);
    return containerShape;
    I think that linking or making somehow relation between pictogram elements should be enough.

  • Question on multiple form elements with the same name !

    Hi All,
    I have a requirement in which more than one text field with the same name exists on a HTML page. We are using JSF framework (Oracle JDeveloper IDE and OC4J ) . I tried using a String array in my backing bean to handle these text boxes. When I hit the Submit, the action (method) is not invoked. But when I try with unique names everything works fine. Am I going wrong somewhere ?
    Thanks in Advance.

    You cannot have exactly the same name on objects.
    You will have to make an array of them to be able to
    o work with them properly--it will keep the names
    unique.I understand! But JSF creates its own names which are unique. The following JSF code
            <htm:tr>
                <htm:td>
                    <h:inputText value="#{Test.description}" id="description1"/>
                </htm:td>
            </htm:tr>
            <htm:tr>
                <htm:td>
                    <h:inputText value="#{Test.description}"  id="description2"/>
                </htm:td>
        </htm:tr>generates the following HTML code with unique names.
            <tr>
                <td>
                    <input id="Test:description1" type="text" name="Test:description1" />
                </td>
            </tr>
            <tr>
                <td>
                    <input id="Test:description2" type="text" name="Test:description2" />
                </td>
        </tr>
        <tr>Though I have a String Array in the backing bean, this doesn't work (The form does not submit to the method in the Backing Bean).
    Similar situation in Struts works absolutely fine.
    Any help would be appreciated !!!

  • 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

  • Based on an xsd schema create a table

    Hi all,
    i need a way that allow me to create a table having an xsd file, in others word i load the xsd schema and create a table accordingly to the element that the xsd schema has respecting also the datatype of every element.
    Is the some functionality that allow me to do a thing like that?
    thanks to every one
    Francesco
    Italy

    I should now give the following output
    Connected.
    SQL> set termout on
    SQL> set feed on
    SQL>
    SQL> drop user test cascade;
    User dropped.
    SQL>
    SQL> purge dba_recyclebin;
    DBA Recyclebin purged.
    SQL>
    SQL> create user test identified by test;
    User created.
    SQL>
    SQL> grant xdbadmin, dba to test;
    Grant succeeded.
    SQL>
    SQL>
    SQL> connect test/test
    Connected.
    SQL>
    SQL> set echo on
    SQL> set termout on
    SQL> set feed on
    SQL> set long 100000
    SQL> set pages 5000
    SQL>
    SQL> var schemaPath varchar2(256)
    SQL> var schemaURL  varchar2(256)
    SQL>
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Create an XML Schema root.xsd in directory /public/
    SQL>
    SQL> ----------------------------------------------------------
    SQL> declare
      2    res boolean;
      3    xmlSchema xmlType := xmlType(
      4  '<?xml version="1.0" encoding="UTF-8"?>
      5   <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
      6              xmlns:xdb="http://xmlns.oracle.com/xdb"
      7              elementFormDefault="qualified"
      8              attributeFormDefault="unqualified"
      9              xdb:storeVarrayAsTable="true">
    10   <xs:element name="ROOT" xdb:defaultTable="ROOT_TABLE" xdb:maintainDOM="false">
    11    <xs:annotation>
    12     <xs:documentation>Example XML Schema</xs:documentation>
    13    </xs:annotation>
    14    <xs:complexType xdb:maintainDOM="false">
    15     <xs:sequence>
    16      <xs:element name="ID" type="xs:integer" xdb:SQLName="ID"/>
    17      <xs:element ref="INFO" xdb:SQLInline="false" />
    18     </xs:sequence>
    19    </xs:complexType>
    20   </xs:element>
    21   <xs:element name="INFO" xdb:SQLName="INFO_TYPE">
    22    <xs:complexType xdb:maintainDOM="false">
    23     <xs:sequence>
    24      <xs:element name="INFO_ID" type="xs:integer" xdb:SQLName="TYPE_INFO_ID"/>
    25      <xs:element name="INFO_CONTENT"
    26                  xdb:SQLName="TYPE_INFO_CONTENT" type="xs:string"/>
    27     </xs:sequence>
    28    </xs:complexType>
    29   </xs:element>
    30  </xs:schema>');
    31  begin
    32  if (dbms_xdb.existsResource(:schemaPath)) then
    33      dbms_xdb.deleteResource(:schemaPath);
    34  end if;
    35   res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    36  end;
    37  /
    PL/SQL procedure successfully completed.
    SQL>
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Selecting repository files and folders via XDBUriType
    SQL>
    SQL> ----------------------------------------------------------
    SQL> select xdbURIType ('/public/root.xsd').getClob()
      2  from   dual;
    XDBURITYPE('/PUBLIC/ROOT.XSD').GETCLOB()
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.o
    racle.com/xdb" elementFormDefault="qualified" attributeFormDefault="unqualified"
    xdb:storeVarrayAsTable="true">
      <xs:element name="ROOT" xdb:defaultTable="ROOT_TABLE" xdb:maintainDOM="false">
        <xs:annotation>
          <xs:documentation>Example XML Schema</xs:documentation>
        </xs:annotation>
        <xs:complexType xdb:maintainDOM="false">
          <xs:sequence>
            <xs:element name="ID" type="xs:integer" xdb:SQLName="ID"/>
            <xs:element ref="INFO" xdb:SQLInline="false"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
      <xs:element name="INFO" xdb:SQLName="INFO_TYPE">
        <xs:complexType xdb:maintainDOM="false">
          <xs:sequence>
            <xs:element name="INFO_ID" type="xs:integer" xdb:SQLName="TYPE_INFO_ID"/
    >
            <xs:element name="INFO_CONTENT" xdb:SQLName="TYPE_INFO_CONTENT" type="xs
    :string"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:schema>
    1 row selected.
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Create an XML Document root.xml in directory /public/
    SQL>
    SQL> ----------------------------------------------------------
    SQL> begin
      2    :schemaURL := 'http://www.myserver.com/root.xml';
      3    :schemaPath := '/public/root.xml';
      4  end;
      5  /
    PL/SQL procedure successfully completed.
    SQL> declare
      2    res boolean;
      3    xmlSchema xmlType := xmlType(
      4  '<?xml version="1.0" encoding="UTF-8"?>
      5  <ROOT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  xsi:noNamespaceSchemaLocation="root.xsd">
      6   <ID>0</ID>
      7   <INFO>
      8     <INFO_ID>0</INFO_ID>
      9     <INFO_CONTENT>Text</INFO_CONTENT>
    10   </INFO>
    11  </ROOT>');
    12  begin
    13  if (dbms_xdb.existsResource(:schemaPath)) then
    14      dbms_xdb.deleteResource(:schemaPath);
    15  end if;
    16   res := dbms_xdb.createResource(:schemaPath,xmlSchema);
    17  end;
    18  /
    PL/SQL procedure successfully completed.
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Selecting repository files and folders via XDBUriType
    SQL>
    SQL> ----------------------------------------------------------
    SQL> select xdbURIType ('/public/root.xml').getClob()
      2  from   dual;
    XDBURITYPE('/PUBLIC/ROOT.XML').GETCLOB()
    <?xml version="1.0" encoding="UTF-8"?>
    <ROOT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchem
    aLocation="root.xsd">
      <ID>0</ID>
      <INFO>
        <INFO_ID>0</INFO_ID>
        <INFO_CONTENT>Text</INFO_CONTENT>
      </INFO>
    </ROOT>
    1 row selected.
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Register the XML Schema and create the OR objects
    SQL>
    SQL> ----------------------------------------------------------
    SQL> select * from tab;
    no rows selected
    SQL> --
    SQL> alter session set events='31098 trace name context forever';
    Session altered.
    SQL> --
    SQL> BEGIN
      2   DBMS_XMLSCHEMA.registerSchema
      3   (SCHEMAURL => 'root.xsd',
      4    SCHEMADOC => xdbURIType('/public/root.xsd').getClob(),
      5    LOCAL     => FALSE, -- local
      6    GENTYPES  => TRUE,  -- generate object types
      7    GENBEAN   => FALSE, -- no java beans
      8    GENTABLES => TRUE,  -- generate object tables
      9    OWNER     => USER
    10   );
    11  END;
    12  /
    PL/SQL procedure successfully completed.
    SQL> select * from tab;
    TNAME                          TABTYPE  CLUSTERID
    INFO1902_TAB                   TABLE
    INFO1904_TAB                   TABLE
    ROOT_TABLE                     TABLE
    3 rows selected.
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- Insert some data with XDBURIType
    SQL>
    SQL> ----------------------------------------------------------
    SQL> DECLARE
      2     XMLData xmlType := xmlType(xdbURIType ('/public/root.xml').getClob());
      3  BEGIN
      4    for i in 1..10
      5    loop
      6        insert into ROOT_TABLE
      7        VALUES
      8        (XMLData);
      9    end loop;
    10  END;
    11  /
    PL/SQL procedure successfully completed.
    SQL> -- randomize the data a little
    SQL> update ROOT_TABLE
      2  set object_value = updateXML(object_value,
      3                              '/ROOT/ID/text()',
      4                              substr(round(dbms_random.value*100),0,2)
      5                              );
    10 rows updated.
    SQL> update ROOT_TABLE
      2  set object_value = updateXML(object_value,
      3                              '/ROOT/INFO/INFO_ID/text()',
      4                              substr(round(dbms_random.value*100),0,2)
      5                              );
    10 rows updated.
    SQL> pause
    SQL> ----------------------------------------------------------
    SQL>
    SQL> -- End Result
    SQL>
    SQL> ----------------------------------------------------------
    SQL> select count(*) from root_table;
      COUNT(*)
            10
    1 row selected.
    SQL> select * from root_table where rownum <= 2;
    SYS_NC_ROWINFO$
    <?xml version="1.0" encoding="US-ASCII"?>
    <ROOT>
      <ID>54</ID>
      <INFO>
        <INFO_ID>28</INFO_ID>
        <INFO_CONTENT>Text</INFO_CONTENT>
      </INFO>
    </ROOT>
    <?xml version="1.0" encoding="US-ASCII"?>
    <ROOT>
      <ID>33</ID>
      <INFO>
        <INFO_ID>35</INFO_ID>
        <INFO_CONTENT>Text</INFO_CONTENT>
      </INFO>
    </ROOT>
    2 rows selected.
    SQL>

  • 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">

  • Binding a sequence XSD Schema to repeating subform elements

    Hi, I am creating a form with repeated table rows using an Add button to add rows dynamically. I am binding the row with the xsd schema with [*] at the end in the data binding option with checked repeat row for each data item. While submitting the form as XML data to the java controller I am getting only one table row and not other rows added dynamically by add button functionality.
    I want to know that how to generate the xml of dynamically added rows bonded with XSD schema.
    I have also explore the below link but doesn't resolve the issues:
    http://www.adobe.com/devnet/livecycle/articles/binding-xsd.html
    Thanks in advance

    I have resolved the issues by adding maxOccurs="unbounded" in xsd schema with the binded element name.

  • Assign ora:getCompositeInstanceId() in the xsd element

    I need to assign BPEL process id, ora:getCompositeInstanceId(), to one of element in the xsd. Is this function available in the Transformation mapping so that I can assign to the element? I found the function in the mediator functions but I didn't work in the BPEL. Any of your idea will be appreciated.
    SOA: 11.1.1.6

    It works in BPEL, it is available as part of Advanced Functions in Expression Builder. However, it does not in Transformations(XSLT). So to work around two alternatives can be used
    Alternate 1:
    - Create a temp variable like "varCompositeInstanceId".
    - Create a assign activity, before the transformation, set the value of the variable to "ora:getCompositeInstanceId()" inside this Assign activity.
    - Send the variable as a parameter to the transformation.
    - Use the parameter to map to the target inside the transformation(XSLT).
    Alternate 2:
    - Set the target in the XSLT to some random text.
    - After the transformation, add an assign activity and inside it, set the value of the taget to "ora:getCompositeInstanceId()".
    Mark the posting appropriately as "helpful" or "correct answer", if your issue is resolved.

Maybe you are looking for