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

Similar Messages

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

Creation of XSD from XML

Hi SDN,
Can anybody guide me to solve this problem.
I have created a custom repository as per the requirement(repository has text fields, taxonomy fields etc). I have created a XSD structure using xomLite from the XML(by exporting from Console).
Now if I open the XSD I am finding only a Category field but the attributes that were created in Datamanager are not present.
I want an XSD with attrbutes , please help me out.
Very urgent.
Regrads,
Pramod

Creating XSD with attributes:
since attributes are created in Data mgr they are not part of data structure which we define in console hence the xsd from console will not have attributes. you can create an xml file from MDM syndicator with all the attributes and from that xml file convert to XSD using the software.
I want to syndicate all the attributes
since we dont have the xsd while syndicating we need to add all attributes first then do the mapping.how to add fields in the xsd in syndicator Manager pls refer the ref guide for MDM Syndicator.
hope it helps.reward points if suitable
Regards-
Ravi

Is it possible to create a Webservice in BI which takes XML as an input and gives PDF as output with an additional requirement that Siebel expecting the XSD from BI to send data in the BI requested format

Is it possible to create a Webservice in BI which takes XML as an input and gives PDF as output with an additional requirement that Siebel expecting the XSD from BI to send data in the BI requested format. Siebel wants to send the data as xml to BI but not sure of the BI capabilities on giving WSDL embedded with XSD (input is a hierarchical)

Hi All,
I am able to fulfil above requirement. Now I am stuck at below point. Need your help!
Is there any way to UPDATE the XML file attached to a Data Definition (XML Publisher > Data Definition) using a standard package or procedure call or may be an API from backend? I am creating an XML dynamically and I want to attach it to its Data Definition programmatically using SQL.
Please let me know if there is any oracle functionality to do this.
If not, please let me know the standard directories on application/database server where the XML files attached to Data Definitions are stored.
For eg, /$APPL_TOP/ar/1.0/sql or something.
Regards,
Swapnil K.

Issue using XSD from MDS

Hi
I am having issue when using XSD from MDS. ( AIA 11G)
I have created MDS connection and tested it and it workds. Through SOA Browser -> Resource Pallet I am able to brouse XSD also. After selecting XSD when i import , I get below mentioned error
Exception: oracle.mds.exception.MDSException: MDS-02501: cannot load the ORAMDS URL "oramds:/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Industry/HealthSciences/EBO/SupplierParty/V1/SupplierPartyEBO.xsd" because MDS session could not be created or resolved
MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "mstore-usage_2" is invalid.
MDS-00918: Connection details for the MDS repository are incomplete. The values for "userName, password, jdbcURL" are invalid
Is there something i am missing?
Bikash

i run into the same issue a lot and it seems that everytime i modify the composite or the bpel, somehow all the userid, password, and jdbc-url properties are removed from the adf-config file. i always have to restore to a previous version from history. i have no idea what causes jdeveloper to remove these tags and haven't yet found a remedy for this problem.

How to make xsd from xml file?

Hi,
i have one xml file which has many node and element.
anyone know how to make xsd from the xml file in order to make DT by using xsd ?
Thanks and Best Regards;
BangBang

HI
there are multiple ways of doing this if you have XML based 3rd party tool with you.. you can search on Google also and will get many tools which can convert this to XSD..
few links with similar discussion..
How to convert XML file into DTD or XSD
XML to XSD
How to creste a XSD ?
Thanks,
Bhupesh

XSD from WSDL SOAP response

From WSDL, I have SOAP respose as
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
     <soapenv:Body>
          <ns1:getDistanceResponse xmlns:ns1="http://DefaultNamespace" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
               <ns1:getDistanceReturn xsi:type="xsd:double">0.0</ns1:getDistanceReturn>
          </ns1:getDistanceResponse>
     </soapenv:Body>
</soapenv:Envelope>
How do I create XSD so that I can import external defintion in designer message_type without typing the fields from scratch?
Here is the XSD:-
<?xml version="1.0" encoding="ISO-8859-1"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"><xs:element name="getDistanceResponse"><xs:annotation><xs:documentation>Comment describing your root element</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name="getDistanceReturn" type="xs:double" /></xs:sequence></xs:complexType></xs:element></xs:schema>

Satish,
When I look at /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1, from WSDL an XSD is created for getDistanceResponse.
Also there is a note from Shabarish "At my first try i used the messages getDistanceRequest and getDistanceResponse in my mapping but later found out that it wasnt the message structure that the webservice expected."
Hence wondering how to create XSD from WSDL so that I can use the structures in message mapping.
In this case it is simple, so i can create the data type but for complex it is better to create XSD from WSDL. May be I'm not putting the right words and question. Please help

Generate XSD from java class

Hi all,
Is there any tool that can generate an XSD from either a java code file or a byte code file?
Thanks in advance,
Asaf

I've never used it, but the Castor project also provides such a tool...at least that what it says in its FAQ:
http://www.castor.org/xml-faq.html#Is-there-a-way-to-automatically-create-an-XML-Schema-from-an-XML-instance?

Extracting XSD from WSDL

Hi Everyone,
I am looking at a very simple scenario: Flat file to Web Service Through SAP XI.
I have created a web service in SAP ECC system. With the help of WSDL document of the web service i created a Message Interface(External Definitions).
On the other hand, i created the data type, message type and message interface for the flat file. Now, When i want to do the message mapping, I only have one message type.
I want to Extract XSD from the WSDL document of the webservice in order to do the message mapping. Can you help me out with this.
Thanks
chan

you dont need XSD,you can just import WSDL itself as you import XSD in the IR.but make sure you select WSDL as the structure.I mean you will have options like DTD,XSD,WSDL.here select WSDL.
and you would get the structure for the other message structure.you can use it as either Ooutbound or inbound.

Referencing an exiting XSD from a new XSD

Hi,
Sorry for the newbie question. Could somebody illustrate how I can reference an existing xsd from a new xsd?
I have registered a schema in the database but I am unsure how to reference it so that I can incorporate a set of enumeration values into a new schema.
Any insights are much appreciated.
Thanks
Joel.

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


<xs:schema targetNamespace="http://xmlns.oracle.com/xdb/OrdImage" xmlns="http://xmlns.oracle.com/xdb/OrdImage" xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:element name="Attributes" type="AttributesType" xdb:defaultTable="ORDIMAGE_METADATA_TABLE"/>
     <xs:complexType name="AttributesType" xdb:SQLType="ord:ORDIMAGE_ANNONTATION_T">
          <xs:sequence>
               <xs:element name="MEDIA_SOURCE_MIME_TYPE" type="MEDIA_SOURCE_MIME_TYPE_Type"/>
               <xs:element name="MEDIA_SIZE" type="MEDIA_SIZE_Type"/>
               <xs:element name="MEDIA_SOURCE_FILE_FORMAT" type="MEDIA_SOURCE_FILE_FORMAT_Type"/>
               <xs:element name="IMAGE_CONTENT_FORMAT" type="IMAGE_CONTENT_FORMAT_Type"/>
               <xs:element name="IMAGE_COMPRESSION_FORMAT" type="IMAGE_COMPRESSION_FORMAT_Type"/>
               <xs:element name="IMAGE_HEIGHT" type="IMAGE_HEIGHT_Type"/>
               <xs:element name="IMAGE_WIDTH" type="IMAGE_WIDTH_Type"/>
          </xs:sequence>
     </xs:complexType>
     <xs:complexType name="IMAGE_COMPRESSION_FORMAT_Type" xdb:SQLType="IMAGE_COMPRESSION_FORMAT_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="IMAGE_CONTENT_FORMAT_Type" xdb:SQLType="IMAGE_CONTENT_FORMAT_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="IMAGE_HEIGHT_Type" xdb:SQLType="IMAGE_HEIGHT_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:short">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="IMAGE_WIDTH_Type" xdb:SQLType="IMAGE_WIDTH_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:short">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="MEDIA_SIZE_Type" xdb:SQLType="MEDIA_SIZE_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:int">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="MEDIA_SOURCE_FILE_FORMAT_Type" xdb:SQLType="MEDIA_SOURCE_FILE_FORMAT_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
     <xs:complexType name="MEDIA_SOURCE_MIME_TYPE_Type" xdb:SQLType="MEDIA_SOURCE_MIME_TYPE_T" xdb:maintainDOM="false">
          <xs:simpleContent>
               <xs:extension base="xs:string">
                    <xs:attribute name="desc" type="xs:string" use="required"/>
                    <xs:attribute name="dt" type="xs:string" use="required"/>
               </xs:extension>
          </xs:simpleContent>
     </xs:complexType>
</xs:schema>
Then it is referenced by
<?xml version="1.0" encoding="UTF-8"?>


<xs:schema targetNamespace="http://xmlns.oracle.com/xdb/ImageMetadata"
xmlns:xdb="http://xmlns.oracle.com/xdb"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:ord="http://xmlns.oracle.com/xdb/OrdImage"
xmlns="http://xmlns.oracle.com/xdb/ImageMetadata" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:import namespace="http://xmlns.oracle.com/xdb/OrdImage" schemaLocation="http://xmlns.oracle.com/xdb/OrdImage.xsd"/>
     <xs:element name="ImageMetadata" type="ImageMetadataType" xdb:defaultTable="IMAGE_METADATA_TABLE"/>
     <xs:complexType name="ImageMetadataType" xdb:SQLType="IMAGE_METADATA_T">
          <xs:sequence>
               <xs:element name="RESID" type="xs:string"/>
               <xs:element name="virtualPath">
                    <xs:simpleType>
                         <xs:restriction base="xs:anyURI">
                              <xs:maxLength value="512"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element minOccurs="0" name="Title" xdb:SQLName="TITLE">
                    <xs:simpleType>
                         <xs:restriction base="xs:string">
                              <xs:maxLength value="80"/>
                         </xs:restriction>
                    </xs:simpleType>
               </xs:element>
               <xs:element minOccurs="0" name="Description" type="xs:string" xdb:SQLType="CLOB" xdb:SQLName="DESCRIPTION"/>
               <xs:element ref="ord:Attributes"/>
               <xs:element minOccurs="0" name="Thumbnail" type="xs:base64Binary" xdb:SQLType="CLOB"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>
Note in this example 2 seperate namespaces are used so the import directive is required. If both schemas share the namespace then the include directive is required. Include simply takes the URL of the schema to be included.

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

Unable to load XSD from the MDS

Hi,
We are undergoing this problem for the last 2 weeks. We are working with BPEL processes which refer the schema from MDS. Everything is working fine in dev which is a single server, but as soon as we moved the code to a clustered test environment, the interfaces are failing to load the XSDs often and they are working only intermittently. When they fail, we receive the following error:
+<fault>+
+<bpelFault>+
+<faultType>0</faultType>+
+<bindingFault>+
+<part name="summary">+
+<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Put' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.ftp.outbound.FTPInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for -Namespace- due to: Unable to lookup schema for '-Namespace- ' Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>+
+</part>+
+<part name="detail">+
+<detail>Connection reset</detail>+
+</part>+
+<part name="code">+
+<code>null</code>+
+</part>+
+</bindingFault>+
+</bpelFault>+
+</fault>+
The server logs are shown:
+<May 2, 2013 9:18:32 AM GMT+00:00> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> InterfaceName:AdapterName [ Write_ptt::Write(body) ] Could not invoke operation 'Write' against the 'File Adapter' due to:+
BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.file.outbound.FileInteractionSpec due to: XSD Resolution problem.
XSD Resolution problem.
Unable to load Translation schemas from for -Namespace- due to: Unable to lookup schema for '-Namespace-'
Please make sure all used XML schemas are imported/included correctly.
+".+
+The invoked JCA adapter raised a resource exception.+
+Please examine the above error message carefully to determine a resolution.+
+>+
+<May 2, 2013 9:18:32 AM GMT+00:00> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> [default/InterfaceName!3.0*soa_7aa1ce63-47ca-49af-a447-b231b8cde31c.AdapterName]:Write One-way operation Write() failed>+
+<May 2, 2013 9:18:32 AM GMT+00:00> <Error> <oracle.soa.bpel.engine.ws> <BEA-000000> <got FabricInvocationException+
+java.net.SocketException: Connection reset+
+at java.net.SocketInputStream.read(SocketInputStream.java:168)+
+at weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)+
+at java.io.InputStream.read(InputStream.java:82)+
+at com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)+
+at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)+
+...+
We have never had this problem till moving to the clustered environment and all the XSDs in the MDS are configured properly to our knowledge. Any helpful pointers to the problem are very much appreciated.
Regards,
vu2jerry
Edited by: 989720 on May 2, 2013 4:57 AM

We have a sev-1 SR raised with Oracle and the issue hasn't been found yet. I had no idea it was a known issue as I couldn't find anything related to these on the web.
By the way it isn't a problem with the File and FTP adapters alone. Even the validate activity is failing to load the XSDs more often than not with the same error. Has anyone else faced the same issue?
Regards,
vu2jerry

Can I create an XSD from XML data in a CLOB?

Environment:
Oracle 11.2.0.3 EE on Solaris.
Very much an XML newbie so please be kind!
I have spent the past few days pouring through the documentation and various blogs, especially this one, but ... I need some help.
I am trying to extract XML data stored in a CLOB and produce a flat file for the user's consumption.
They have sent me what they think is the XSD for the XML data but when I look at the data in the CLOB I don't see the tags documented in the XSD.
I'd like to produce an XSD based on the actual data to compare with what they've sent.
Is this possible?
I am able to query the XML data using the tags I see in the data using XMLTable and it's working fine.
Any help is greatly appreciated.
-gary

Welcome to the XML side of the world, where you will love it and curse it, just like any other piece of technology.
So as I understand it, the scope of your operation is to extract information from an XML file and then write that information to disk, correct?
Some questions
- Why is the XML stored in a CLOB instead of an XMLType column? Without knowing the system history, it is a valid question.
- How big are the XML? The reason I ask this is because when the XML is stored in XMLType columns (of Object Relational structure or SECUREFILE BINARY XML format), then Oracle can parse the XML substantially easier than when it is stored as a CLOB. If the XML is fairly small, you may see no performance difference between the two.
The Oracle DB itself has no built in ability to generate a schema from an XML file. In order to do that, you would need to use some third party tool that has that functionality built in. For example, XML Spy can do this. Other tools can as well, but that is what came to mind first as it is what I use. The one thing to remember is that the schema it builds represents that one instance of XML. Other instances of XML may be different and not validate against the schema you generated, but still have been valid against the unknown original schema.
You can register the schema in the database and then use the XML to create an XMLType instance associated to the schema and then validate the XML that way. One example can be found at XML DB FAQ and here is another example Re: XML Schema validation
Hope that helps you continue on.

XSD from Database table/view/procedure

Hi all,
Does anyone know of a tool or framework which enables generation of XSD's out of a Database table/view/procedure?

Hi Naval,
It depends on whether you created a BOL model for your Z-table or not. If you don't have a BOL model, then all you can do is use a value node. In that case, you need to add attribute that you want to show in the value node, read the values from the z-table and add them to the node. You can create method(s) in view implementation class to read values from database table and fill the context node. From where these methods should then be called will depend on your requirement.
Regards,
Shiromani

Generating XSD from Database

I need to auto-generate an XSD file from a database. I'm told there are free tools out there to do this but haven't had any luck finding any. Any ideas? I don't want to have to write this by hand.

Thanks, I'll take a look at that. Are there any free tools available to do this? I heard a rumor that Hibernate will do this. Let me know if anyone has any other ideas.

XSD from PI in Syndicator

Similar Messages

Maybe you are looking for