XML document question?

Is an XML document only "information" on a song and not the song itself? I burned my "iTunes Music Library" to a CD thinking I saved all my songs. Can it be transformed into a usable file or did I just save "info"? Can anyone help a PC 1st grader?
inspiron 8600 Windows XP

The XML file is only data about the songs on the Playlist or Library. You can open the file with one of several programs and view it for yourself.
See: What are the iTunes Library files?
There are no song files contained in the XML file. Only music metadata.

Similar Messages

Storing XML Document as Data question...

Hi,
I read the document from http://technet.oracle.com/tech/xml/info/htdocs/otnwp/about_oracle_xml_products.htm and
this document mention that can store XML Document as Data.
How does it work? and is there any example code tha I can try?
Thanks for you kindly help!
Good day.

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Kelly:
I read the document about XSU and where I can download the XSU for testing?<HR></BLOCKQUOTE>
Go to http://technet.oracle.com/tech/xml/oracle_xsu/
That's the same URL where you found the XSU document.
Then click the Software tab at the top of the main frame.
If you don't see the Software tab, you may need to enable JavaScript. If you can't (or don't want to) enable JavaScript, try this URL: http://technet.oracle.com/software/tech/xml/oracle_xsu/htdocs/listing.htm
Thanks,
-rh
null

Question about generate xml document

Hi, I'm new to xml can anyone introduce me some tools to generate xml documents? or some faster way to generate xml documents.

a good site for the info www.xml.com or www.oasis.org
xml-spy is a good tool

Question about special characters in XML documents

Hi,
I need to create some XML documents based on documents containing elements containing strings containing accentuated and special characters such as �� or Asian characters.
I have found the following code claiming that XML documents created by the xformer will have a utf-8 format:
// Write the DOM document to the file
Transformer xformer = TheTF.newTransformer();
xformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");and I have found the InputSource object to be used to read UTF-8 XML documents:
InputSource in = new InputSource(new FileReader(filename));
in.setEncoding("UTF-8");Is this enough to make sure that accentuated and Asian characters (or any other characters) will be converted properly when creating and re-reading the XML document? If one of my elements contain the following text '��33445tata', will the string remain the same when re-read from the XML? Do I need more code to make sure that all conversion will be performed properly and transparently? If yes, can one provide an example?
Thanks!

Hi Dr.Clap,
Thanks for your answer, but I am not really sure I understand you. I have performed a test to generate a simple document containing one element. An attribute containing some special characters is added to the element. The element text also contains specials characters.
When I generate the XML into a byte array input and print the content, I get:
<?xml version="1.0" encoding="utf-8" standalone="no"?><UTF8TEST BIBI="��ii��">tre33��</UTF8TEST>When I parse the document, and print the result, I get:
-- Begin of Parsing
Element Name = UTF8TEST
Attribute Name = BIBI
Attribute Value = �ii��
Found text : tre33��
-- End of Parsingwhich is correct. I am worried by the ��ii� ��-like characters generated in the XML. Should I be worried or shouldn't I? Should I convert these into something looking a more like ASCII, or is this fine?
I am including the code of my example (excluding imports):
public class XMLUTF8_Test extends DefaultHandler {
    // Logger
    private final static Logger LOG = Logger.getLogger(XMLUTF8_Test.class.getName());
    // Static
    public static DocumentBuilderFactory DOCUMENT_BUILDER_FACTORY;
    public static DocumentBuilder DOCUMENT_BUILDER;
    public static TransformerFactory TRANSFORMER_FACTORY;
    private static SAXParserFactory FACTORY;
    private static SAXParser SAXPARSER;
    private static XMLReader XMLREADER;
    static {
        // Preparing the writting
        DOCUMENT_BUILDER_FACTORY = DocumentBuilderFactory.newInstance();
        try {
            DOCUMENT_BUILDER = DOCUMENT_BUILDER_FACTORY.newDocumentBuilder();
        } catch (ParserConfigurationException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
        TRANSFORMER_FACTORY = TransformerFactory.newInstance();
        // Preparing the reading
        try {
            FACTORY = SAXParserFactory.newInstance();
            SAXPARSER = FACTORY.newSAXParser();
            XMLREADER = SAXPARSER.getXMLReader();
        } catch (ParserConfigurationException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
        } catch (SAXException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
    public static void main(String[] args) {
        // Perform test
        new XMLUTF8_Test();
    public XMLUTF8_Test() {
        // Saving to File
        Document NewDoc = DOCUMENT_BUILDER.newDocument();
        Element Root = NewDoc.createElement("UTF8TEST");
        Root.setAttribute("BIBI", "�ii��");
        Root.setTextContent("tre33��");
        NewDoc.appendChild(Root);
        ByteArrayOutputStream TheBAOS = new ByteArrayOutputStream();
        try {
            Source source = new DOMSource(NewDoc);
            Result result = new StreamResult(TheBAOS);
            Transformer xformer = TRANSFORMER_FACTORY.newTransformer();
            xformer.setOutputProperty(OutputKeys.ENCODING, "utf-8");
            xformer.transform(source, result);
        } catch (TransformerConfigurationException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
        } catch (TransformerException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
        // Printing result
        System.out.println(TheBAOS.toString());
        // Parsing the result
        ByteArrayInputStream TheBAIS = new ByteArrayInputStream(TheBAOS.toByteArray());
        XMLREADER.setContentHandler(this);
        try {
            XMLREADER.parse(new InputSource(TheBAIS));
        } catch (IOException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
        } catch (SAXException Ex) {
            Debugger.LogUnreachableCodeReachedSituation(LOG, Ex);
    @Override
    public void startDocument() throws SAXException {
        System.out.println("-- Begin of Parsing");
    @Override
    public void endDocument() throws SAXException {
        System.out.println("-- End of Parsing");
    @Override
    public void startElement(String namespaceURI, String LocalName, String QualifiedName,
            Attributes TheAttributes) throws SAXException {
        String ElementName = LocalName;
        if ("".equals(ElementName)) {
            ElementName = QualifiedName; // namespaceAware = false
        System.out.println("Element Name = " + ElementName);
        if (TheAttributes != null) {
            for (int i = 0; i < TheAttributes.getLength(); i++) {
                String AttributeName = TheAttributes.getLocalName(i); // Attr name
                if ("".equals(AttributeName)) AttributeName = TheAttributes.getQName(i);
                System.out.println("Attribute Name = " + AttributeName);
                System.out.println("Attribute Value = " + TheAttributes.getValue(AttributeName));
    @Override
    public void endElement(String namespaceURI, String SimpleName, String QualifiedName) throws SAXException {
    @Override
    public void characters(char[] buf, int offset, int len) throws SAXException {
        String s = new String(buf, offset, len);
        System.out.println("Found text : " + s);
}Thanks!

Problem replacing Null nodes with real values in XML documents...

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
Our friends in Java land are insisting on passing data between Java and PL/SQL using fairly small XML documents (don't ask). I then need to extract the input parameter values and pass them, on to the stored procedures that actually do the work. These return a result which needs to be returned to the java layer in the output XML document.
Here is a cut down version of the input XML...
<ParameterList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Parameter>
<Id>1</Id>
<Result xsi:nil="true"/>
</Parameter>
<Parameter>
<Id>2</Id>
<Result xsi:nil="true"/>
</Parameter>
</ParameterList>
and this is an example of what I am expected to return...
<ParameterList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Parameter>
<Id>1</Id>
*<Result>SUCCESS</Result>*
</Parameter>
<Parameter>
<Id>2</Id>
*<Result>WARNING</Result>*
</Parameter>
</ParameterList>
i.e. I am expected to replace the value of the Result node with a string indicating the succes or otherwise of the underlying PL/SQL process.
I am extracting the input values using the DBMS_XMLDOM functions and naively assumed that DBMS_XMLDOM.SETNODEVALUE could be used to update the value in the Result node - It didn't work so I resorted to reading the documentation which revealed that it will not work for a null node.
Am I going to have to use XSLT to generate the output XML from the Input and incorprate the result? Or is there a simpler way?
I have used XSLT in Oracle before and still have the nervous tick...

Thanks A Non,
With your suggestion and a bit of help from the w3schools.com xml dom tutorial I eventually managed to work out how to do this.
Here is the code (with all my debug stuff in so it looks worse than it is...)
create or replace
PROCEDURE ExtractXMLValues (p_inXml IN CLOB ) IS
l_string VARCHAR2(4000);
l_value VARCHAR2(4000);
l_DOM_doc dbms_xmldom.DOMDocument;
l_DOM_node dbms_xmldom.DOMNode;
l_new_DOM_node dbms_xmldom.DOMNode;
l_new_element dbms_xmldom.DOMElement;
l_new_DOM_nodevalue dbms_xmldom.DOMNode;
l_value_Node dbms_xmldom.DOMNode;
l_parameter_Node dbms_xmldom.DOMNode;
--l_DOM_nodelist dbms_xmldom.DOMNodeList;
l_Result_DOM_node dbms_xmldom.DOMNode;
BEGIN
l_DOM_doc := dbms_xmldom.newDomDocument(p_inXml);
l_DOM_node := dbms_xmldom.makeNode(l_DOM_doc);
dbms_xmldom.writeToBuffer(l_DOM_node, l_string);
dbms_output.put_line('1 ' || l_string);
l_parameter_node := dbms_xslprocessor.selectSingleNode(l_DOM_node,'//Parameter');
-- get the current values in the XML document for Id and Result
l_Result_DOM_node := dbms_xslprocessor.selectSingleNode(l_DOM_node,'//Id');
l_value_Node := dbms_xmldom.getFirstChild(l_Result_DOM_node);
l_value := dbms_xmldom.getnodevalue(l_value_Node);
dbms_xmldom.writeToBuffer(l_Result_DOM_node, l_string);
dbms_output.put_line('2 ' || l_string || ' : ' || l_value);
l_Result_DOM_node := dbms_xslprocessor.selectSingleNode(l_DOM_node,'//Result');
l_value_Node := dbms_xmldom.getFirstChild(l_Result_DOM_node);
l_value := dbms_xmldom.getnodevalue(l_value_Node);
dbms_xmldom.writeToBuffer(l_Result_DOM_node, l_string);
dbms_output.put_line('3 ' || l_string || ' : ' || l_value);
-- create new Result node
l_new_DOM_node := dbms_xmldom.makenode(dbms_xmldom.createElement(l_DOM_doc, 'Result'));
dbms_xmldom.writeToBuffer(l_new_DOM_node, l_string);
dbms_output.put_line('4 New node : ' || l_string);
-- create a value for it
l_new_DOM_nodevalue := dbms_xmldom.makenode(dbms_xmldom.createtextnode(l_DOM_doc, 'SUCCESS'));
dbms_xmldom.writeToBuffer(l_new_DOM_nodevalue, l_string);
dbms_output.put_line('5 New node value : ' || l_string);
-- add the value to the new Result node
l_new_DOM_nodevalue := dbms_xmldom.appendchild(l_new_DOM_node, l_new_DOM_nodevalue);
dbms_xmldom.writeToBuffer(l_new_DOM_node, l_string);
dbms_output.put_line('6 New node : ' || l_string);
-- replace the old node with the new one
l_Result_DOM_node := dbms_xmldom.replaceChild(l_parameter_node, l_new_DOM_node, l_Result_DOM_node);
dbms_xmldom.writeToBuffer(l_parameter_node, l_string);
dbms_output.put_line('6 parameter node : ' || l_string);
dbms_xmldom.writeToBuffer(l_DOM_node, l_string);
dbms_output.put_line('7 Updated document ' || l_string);
dbms_xmldom.freeDocument(l_DOM_doc);
END ExtractXMLValues;
and the output...
1 <ParameterList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Parameter>
<Id>1</Id>
<Result xsi:nil="true"/>
</Parameter>
</ParameterList>
2 <Id>1</Id> : 1
3 <Result xsi:nil="true"/> :
4 New node : <Result/>
5 New node value : SUCCESS
6 New node : <Result>SUCCESS</Result>
6 parameter node : <Parameter>
<Id>1</Id>
<Result>SUCCESS</Result>
</Parameter>
7 Updated document <ParameterList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Parameter>
<Id>1</Id>
*<Result>SUCCESS</Result>*
</Parameter>
</ParameterList>
One question, why do the dbms_xmldom functions return the Old value? I was expecting the returned value to be the updated node.
Edited by: Lone voice on May 14, 2009 11:24 AM

Parse and output XML document while preserving attribute order

QUESTION: How can I take in an element with attributes from an XML and output the same element and attributes while preserving the order of those attributes?
The following code will parse and XML document and generate (practically) unchanged output. However, all attributes are ordered a-z
Example: The following element
<work_item_type work_item_db_site="0000000000000000" work_item_db_id="0" work_item_type_code="3" user_tag_ident="Step" name="Work Step" gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_site="0000000000000000" last_upd_db_id="0" rstat_type_code="1">
</work_item_type>is output as:
<work_item_type gmt_last_updated="2008-12-31T18:00:00.000000000" last_upd_db_id="0" last_upd_db_site="0000000000000000" name="Work Step" rstat_type_code="1" user_tag_ident="Step" work_item_db_id="0" work_item_db_site="0000000000000000" work_item_type_code="3">
</work_item_type>As you may notice, there is no difference in these besides order of the attributes!
I am convened that the problem is not in the stylesheet.xslt but if you are not then it is posted bellow.
Please, someone help me out with this! I have a feeling the solution is simple
The following take the XML from source.xml and outputs it to DEST_filename with attributes in a-z order
Code:
private void OutputFile(String DEST_filename, String style_filename){
     //StreamSource stylesheet = new StreamSource(style_filename);
     try{
          File dest_file = new File(DEST_filename);
          if(!dest_file.exists())
              dest_file.createNewFile();
          TransformerFactory tranFactory = TransformerFactory.newInstance();
          Transformer aTransformer = tranFactory.newTransformer();
          aTransformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
          Source src = new DOMSource("source.xml");
          Result dest = new StreamResult(dest_file);
          aTransformer.transform(src, dest);
          System.out.println("Finished");
     catch(Exception e){
          System.err.print(e);
          System.exit(-1);
    }

You can't. The reason is, the XML Recommendation explicitly says the order of attributes is not significant. Therefore conforming XML serializers won't treat it as if it were significant.
If you have an environment where you think that the order of attributes is significant, your first step should be to reconsider. Possibly it isn't really significant and you are over-reaching in some way. Or possibly someone writing requirements is ignorant of this fact and the requirement can be discarded.
Or possibly your output is being given to somebody else who has a defective parser which expects the attributes to be in a particular order. You could quote the XML Recommendation to those people but often XML bozos are resistant to change. If you're stuck writing for that parser then you'll have to apply some non-XML processing to your output to fix it up on their behalf.

How to insert data into a table from an xml document

using the XmlSql Utility, how do I insert data into a table from an xml document, using the sqlplus prompt.
if i use the xmlgen.insertXML(....)
requires a CLOB file, which i dont have, only the xml doc.
Cant i insert directly from the doc to the table?
the xmlgen examples I have seen first convert a table to a CLOB xmlString and then insert it into another table.
Isnt there any other way?

Your question is little perplexing.
If you're using XML SQL Utility from
the commandline, just use putXML.
java OracleXML putXML
null

How to save sections of a single XML Document to multiple tables ?

Firstly, I apologise for the long e-mail but I feel it's necessary in order to clarify my problem/question.
The XML document representation below stores information about a particular database. From the information in the XML document you can tell that there is a single database called "tst" which contains a single table called "tst_table". This table in turn has two columns called "CompanyName" & "Country".
I want to use Oracle's XML SQL Utility to store this information into three seperate database tables. Specifically, I want to store the information pertaining to the database (i.e. name etc.) in one table, the information pertaining to the table (name, no. of columns etc.) in another and the information pertaining to the columns (name, type etc.) in yet another table.
I have seen samples where an entire XML Document is saved to a database table but I cannot find any examples where different sections of a single XML Document are saved into different database tables using the XML SQL Utility.
Can you please tell me the best approach to take in order to accomplish this . Does it involve creating an XMLDocument and then extracting the relevant sections as XMLDocumentFragment's, retrieving the String representations of these XMLDocumentFragment's and passing these strings to the OracleXMLSave.insertXml() method.
Is this the best approach to take or are there any other, perhaps more efficient or elegant, ways of doing this ?
Thanks in advance for your help
- Garry
<DATABASE id="1" name="tst">
<TABLES>
<TABLE name="tst_table">
<NAME>Customers</NAME>
<COLUMNS>
<COLUMN num="1"> <COLID>2</COLID>
<COLNAME>CompanyName</COLNAME>
<COLTYPE>Text</COLTYPE>
</COLUMN>
<COLUMN num="2">
<COLID>3</COLID>
<COLNAME>Country</COLNAME>
<COLTYPE>Text</COLTYPE>
</COLUMN>
</COLUMNS>
</TABLE>
</TABLES>
</DATABASE>
null

See this thread;
{thread:id=2180799}
Jeff

How to search for a text node with a particular value in an xml document with labview

supposing i have the following xml document:
<head>
<book>
<bookname>zio</bookname>
<author>dan</author>
</book>
<book>
<bookname>the spear warrior</bookname>
<author>britney</author>
</book>
<book>
<bookname>the beard</bookname>
<author>derrick</author>
</book>
</head>
i want to search for the author of the book "the beard" using for example the V.I Get first match of labview to access the the node with value "the beard" and then use Get next sibling V.I and Get node text content to get get the author of this book..so my question is how do i write the xpath expression for Get first match so as to access the node with bookname "the beard" instantyly? am trying to minimise the use of loops because they increase the time duration,..thank you (NB:i dont want to use Get all Matched V.I because it obliges me to use a loop in order to access the name derrick and this increases the time duration for my v.i)
Solved!
Go to Solution.

Since it's all text, why not use a real quick Match Pattern (or Regular Expression, but you don't need that much power here), see attached.
Cameron
To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.
To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):
LabVIEW Unit 1 - Getting Started
Learn to Use LabVIEW with MyDAQ
Attachments:
Two-stage match demo.vi ‏8 KB

Cannot unmarshal an XML document to a JavaBean without its XML Schema?

Hi,
2 questions:
1. I have an XML document and have the corresponding JavaBean (the 2 already exist). I tried to unmarshall the XML document using JAXB but I get a strange error of duplicate attributes/elements no matter if I use the annotations @XmlElement, @XmlAttribute etc. The code I use is simply:
JAXBContext jc = JAXBContext.newInstance("MyClass.class");
Unmarshaller u = jc.createUnmarshaller();
MyClass myClass = (MyClass) u.unmarshal(new File("myxml.xml"));Do I always have to create the .xsd file of my xml, create the JavaBean using xjc and then run the above?
2. Can I use JAXB to parse an XML file to a JavaBean but, because the xml file is a complicated one, to use xpaths to get the attributes?
E.g. to use something like this?
@XmlAttribute ("xpath/to/attribute")Thank you in advance for your replies.
Best regards,
John.

Hi,
2 questions:
1. I have an XML document and have the corresponding JavaBean (the 2 already exist). I tried to unmarshall the XML document using JAXB but I get a strange error of duplicate attributes/elements no matter if I use the annotations @XmlElement, @XmlAttribute etc. The code I use is simply:
JAXBContext jc = JAXBContext.newInstance("MyClass.class");
Unmarshaller u = jc.createUnmarshaller();
MyClass myClass = (MyClass) u.unmarshal(new File("myxml.xml"));Do I always have to create the .xsd file of my xml, create the JavaBean using xjc and then run the above?
2. Can I use JAXB to parse an XML file to a JavaBean but, because the xml file is a complicated one, to use xpaths to get the attributes?
E.g. to use something like this?
@XmlAttribute ("xpath/to/attribute")Thank you in advance for your replies.
Best regards,
John.

Parsing an xml document inside a Thread

Hi Friends
I have to do some processing in my application for which i need to use multithreading.
Inside every new thread created i have to parse an xml document using s parsing tool like castor or jibx.
My question is that is it possible to parse a xml document inside a new thread everytime it gets created.
is it a good coding practice as it involves java code to do it.
Thanks
Vikeng

vikeng wrote:
Hi
Thanks for the reply.
Well i need to do some kind of a batch processing in my application.
I need to parse an xml document and upload the data i get after parsing into columns in the database.
Since its a batch what i was asking was is it possible to do it for every request as batch needs to handle hundreds of records during the daily or nightly sync.
Is it a good practice to do parsing for every record in a batch
Thanks
VikengI don't get it. One batch is one document, and that document contains e.g. 100 records? What's one request? A request for one batch? I would execute one batch in one thread.
Kaj

Serializing an XML document

Hello, I recently downloaded the Java XML Pack, which uses the Xerces2 XML Parser. A couple of questions with regards to serializing an XML document to a file:
1) Xerces1 used the org.apache.xml.serialize.* classes to do serialization (such as shown below), but I don't see them in the Xerces2 API. Which packages take over for these in Xerces2?
import org.apache.xml.serialize.Serializer;
import org.apache.xml.serialize.SerializerFactory;
import org.apache.xml.serialize.XMLSerializer;
2) If we use the JAXP wrapper functionality to serialize instead, is the javax.xml.transform package the standard way to do this in 1.2?--from the examples I've seen searching this forum, this appears to be the case.
Thanks,
Glen

If you want to output your XML to a file, say, then yes the Transformer is the way to do it now. Don't know why they did that, it's far from intuitively obvious.

UCCX 8 - Dramatic change in the Create File Document step that is used by the Create XML Document step in order to read an XML file

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
For the last 5 years (and in IPCC3.x/4.x,UCCX/5.x/7.x) I've used the same basic subflow to read a XML document that contains holiday dates where the queue should be closed. I've re-used this script on 20+ client installs and it's always worked. The structure of the script allows you to pass the path and filename of the XML document as parameters to the subflow. (The document is in the repository)
I loaded this script in UCCX 8.0.2 recently and it crashed with a Java.IO error. It looked like it was trying to read the file system directly and not the repository. (In the Linux appliance model this kind of makes sense but why is the step trying to read the file system directly?)
So I open a TAC case (SR# 615243125) and TAC tells me that the method of using the Create File Document step is not supported anymore and that I should specify the filename directly in the Create XML Document step
The problem that I see (aside from having to edit all my scripts that use XML files) is that the Create XML Document step is looking for the input to be a type DOCUMENT and not a type STRING. This seems to imply that I have to hardcode the document in each script that I deploy for a customer. When it was a string it was easy to construct the full file path from parameters and pass to the subflow.
Questions to the group
#1 Am I missing something here?
#2 Do you assume that you'll be able to load a script that worked fine in UCCX 7 into UCCX 8 and that it should completely function when you're doing everything according to the step reference documentation.
#3 Cisco didn’t document this in any way that I can find.
#4 How can you use the Create XML Document step in a fashion that would let you construct the path of the file and the filename previously in the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
(Background)
Create File Document Step
The input filename is a STRING, could be an explicit path and filename in the repository or a variable that represents that path and string
The output of this step is a DOCUMENT to be used in the Create XML Document step
The string FILE_FullPathHolidayFiles references en_us\folderName\documentName.xml
The document was properly uploaded into the repository only, NOT trying to directly read c:\foo\blah…
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
The create XML document input can only be a type DOCUMENT

#1 Am I missing something here?
You are mixing two different issues together here.
The Create File Document step is indeed not needed or supported for creating an XML document. That is why there is a unique step; to trigger XML parsing within the MIVR subsystem.
Accessing the file system is restricted to a single folder within the VOS model (i.e. 8.0+). This folder is not backed up, replicated, or cleaned up automatically. It was intended to give developers some FS access as a temporary swap location only.
#2 Do you assume that you'll be able to load a script that
worked fine in UCCX 7 into UCCX 8 and that it should completely
function when you're doing everything according to the step reference
documentation.
Assume nothing; read the documentation and attend one of the dozens of partner training sessions that CCBU put on advising of the upcoming changes.
#3 Cisco didn’t document this in any way that I can find.
You're right, I guess, on the Create File vs. XML Document step. AFAIK Cisco never wrote a notice into the Step Reference Guide explicitly stating that you cannot use the Create File Document although the documentation seemed pretty clear to me without it. File system restrictions are documented in the 8.0 release notes.
Scripting and Development Series: Volume 2, Editor Step ReferenceUse the Create XML Document step to create a logical document that maps a document to another document variable (where the document has already been pre-parsed as an XML document and is ready to be accessed by the Get XML Document Data step).Use this step before the Get XML Document Data step to obtain data from a document formatted using the Extensible Markup Language (XML).
#4 How can you use the Create XML Document step in a fashion that would
let you construct the path of the file and the filename previously in
the script so you could pass it to a subflow ? It would seem this functionality has been killed in UCCX 8
No it hasn't; just concatinate a string to build the Source Document parameter the step needs. Example: "DOC[" + myFilePath + "]"

Creating an Element for an XML Document

Assuming I have an XML file
file.xml
<root>
<child1>
<child2>
<child100>
<root>
i do
SAXBuilder parser = new SAXBuilder();
doc = parser.build(file);
root = doc.getRootElement();This returns a root elemnet for the entire tree.Now my question is how do i create a root element for say jus the top 10 children? That is, is there a way i can create a document just reading the first 10 elements from the file tree above so that when i do a getChildren on root I should have only 10 elements in the list.

| 1. How are the attributes of an XML element can be stored to the database
XML SQL Utility (which XSQL uses under the covers) only stores
documents in the canonical format. You'll need to use an XSLT
transformation to transform data into the canonical format
(including transforming attribute values into elements whose
names correspond to the column in which you'd like to store it)
| 2. How can I store a single XML document to multiple database tables?
I outline several techniques for this in my upcoming
O'Reilly book, "Building Oracle XML Applications".
The basic idea is to either:
(1) Use an Object View with an INSTEAD OF INSERT trigger, or
(2) Use a technique that transform the inbound document
into a multi-table insert-format and passes each
relevant part for insert to the XML SQL Utility separately.
null

Append XML elements with same name in an XML document

Hi,
I am using Oracle9i XMLDB utilities to modify an XML document stored in the database. I have a sample XML document like this in the database:
<Person>
<Address ID="1"> </Address>
</Person>
My task is to include a second <Address> element with a different attribute so that my XML document will become
<Person>
<Address ID="1"> </Address>
<Address ID="2"> </Address>
</Person>
After creating the second element, I am using the function xmldom.appendChild() or xmldom.insertBefore() but they remove the first <Address> element and replace it with the second one. This is not what I want since I want both <Address> elements to be present.
Could anyone please advise.
Thanks.
A. Dennis

Please post your question [url http://forums.oracle.com/forums/forum.jsp?forum=154]here for quick response.
thank you.
Regards,
Anupama
[url http://otn.oracle.com/sample_code/]OTN Sample Code

XML document question?

Similar Messages

Maybe you are looking for