Writing XML Document to a file or the console

How do i write an XML document to a file & to the console.
Document doc = new Document
doc = (Document)Class.forName("org.apache.xerces.dom.DocumentImpl").newInstance();
Element root = doc.createElement("PERSON");
Element item = doc.createElement("NAME");
item.appendChild(doc.createTextNode("Vaskar"));
root.appendChild(item);
How do i write this doc object to the console

if you use XMLDocument object which implements Document then you would be able to use the method print that is part of the xmlDocument class
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Vaskar Dasgupta ([email protected]):
How do i write an XML document to a file & to the console.
Document doc = new Document
doc = (Document)Class.forName("org.apache.xerces.dom.DocumentImpl").newInstance();
Element root = doc.createElement("PERSON");
Element item = doc.createElement("NAME");
item.appendChild(doc.createTextNode("Vaskar"));
root.appendChild(item);
How do i write this doc object to the console<HR></BLOCKQUOTE>
null

Similar Messages

When I change the time zone of the clock, the "Date created" time information for my documents and image files in the Finder window (and in Get Info) is changed. Can I make the time info in "Date created" remain fixed regardless of the clock's timezone?

When I change the time zone of the clock, the "Date created" time information for my documents and image files in the Finder window (and in Get Info) is changed. Can I make the time info in "Date created" remain fixed regardless of the clock's timezone?

When I change the time zone of the clock, the "Date created" time information for my documents and image files in the Finder window (and in Get Info) is changed. Can I make the time info in "Date created" remain fixed regardless of the clock's timezone?

I have opened Pages and am writing a document. Where, though, is the spell checker?

I have opened Pages and am writing a document. Where, though, is the spell checker?

If you mean checking spelling as you type, go to Edit > Spelling > Check Spelling While Typing.

Problems while writing xml doc to a file

Hi all , in my project (of distributed xml databases) i need to write the xml files from the main server to the clients.
These xml files i had formed by fragmenting one xml doc and i did the fragmentation using ....
TransformerFactory tf = TransformerFactory.newInstance();
          Transformer transformer = tf.newTransformer();
          transformer.transform(new DOMSource(root),
          new StreamResult(new FileOutputStream(outputFile)));
Now the problem is that on the client where these fragments reside..i m not able to do the indexing of the document properly ie...
some extra text nodes with no values are coming in the index...
i dont know how to deal wid the extra nodes that i m getting after parsing the file and craeting an index for the same..
may be its coz of the transformer func i m using....don know(???)
Note : i m fragmenting the xml files into text files using the above function and then sending thm to the client via sockets.
Also,after fragmenting i am getting sumthng like
<?xml version="1.0" encoding="UTF-8"?>
in all the files..is this a source of any problem....
plz reply soon....

You have not described how you "index" the files and what you mean by that.
Are you processing them with SAX or DOM, or one of the variations of those means?
Is there a chance that the "extra" nodes are simply text nodes with newlines ("\n")? There are usually a lot of extra text nodes in a file each containing only one newline.
If you are using SAX, there is no requirement for the parser to collect all of the text inside an element into a single block before calling the characters method. You may get several calls to characters between the start of an element and the end. If you change parsers, you may even get a different number of calls, but the character data will always be the same.
Dave Patterson
As to the <?xml version="1.0" encoding="UTF-8"?> line, that is perfectly fine. It means that your file thinks it is valid XML. Whether or not it REALLY is valid depends on a validation of the file.

Writing XML document using form values

Being new to java/xml I'm strugling with this task:
I have a web form and I need to pass the values from the form to a class that will then create an xml file using the form values.
I've looked through the JAXP tutorial and Sun's XML tutorial but can't find anything that would suit my needs.
Could anyone help me on how I should go about doing this?
Does anyone have any sample code?

with JAXP, you can either :
- build a new XML document from scratch, using DOM, and append each node, each value,
- create a style sheet that generates an XML document, receiving the web form values as parameters, processed with XSLT.

Writing xml from an .exe file

Hi,
So, is it possible to post to php in an .exe file instead of a .swf displayed inside a browser?
If so, how? I figured if you just created the .exe on the server with the .php file in the same folder
it would read it and work fine.
This doesn't seem to be the case... any ideas? Does it always have to go through a browser page?
thanks

It is possible to call a PHP file from an EXE. Make sure that you have th PHP file in the webroot of your webserver (IIS or Apache). Also, make sure that you use the server path..for example: http://localhost/myapp/myphpfile.php. It should work!

Writing XML Object to a File

Hi, I am using InDesign JavaScript to make an XML object in memory. When my script is done, I want to write the XML to a file. When I run the code below, the file is created, but the XML is not written to the file. Any help would be appreciated. Thanks. Rick
#target indesign
var partsMap = <partsMap />;
savePartsMap (partsMap);
function savePartsMap (partsMap) {
    var partsFile;
    // Make a File object for the parts map XML file.
    partsFile = new File("E:\\Test.xml");
    // Open the map file.
    partsFile.open("w");
    partsFile.write(partsMap);
    partsFile.close();

Add partsFile.encoding = 'UTF-8'; right after your File instantiation.
I'm not sure but you also might want to write partsMap.toXMLString() instead of the partsMap.toString() you're implicitly writing.
Jeff

HT1451 the itunes xml document just shows up on the internet not in itunes i feel like I'm missing a step that you are not giving to me after the opening of document

very frustrating

Let's try the following user tip with that one:
"There is a problem with this Windows Installer package ..." error messages when installing iTunes for Windows

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 + "]"

How to write an xml Document to a flat file using JAVA....

Can any one help me out.....
How to write a XML Document to the current filesystem using JAVA....
without using com.sun.xml.tree.*....
Document xmlDoc;
Node rows = (Node) xmlDoc.createElement("ROWS");
xmlDoc.appendChild(rows);
and i have to write this xmlDoc to a file called(abc.xml) for further use...

Have you considered using JDOM? ( www.jdom.org )
The XMLOutputter class can write the Document to a file. ( The Document however will be an org.jdom.Document object ).
If you are weary of a new API, you could just create a new File object called abc.xml and stream the data from the XML Document you have to this new File object.

Writing XML to file problem

I have the following code, worked just fine in JRE 1.4.2 but when I try to run it on a JRE 1.5 runtime it does not.
Code:
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder documentBuilder = factory.newDocumentBuilder();
Document document = documentBuilder.newDocument();
Element configNode = document.createElement("config");
configNode.setAttribute("name", "something");
document.appendChild(configNode);
code to write the document to a file.
In JRE 1.5 the XML file that is written to the file looks like this:
<?xml version="1.0" encoding="ISO-8859-1" ?>
[config: null]
In JRE 1.4.2 the XML file that is written to the file looks like this:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<config name="something">
</config>
In JRE 1.5, after document.appendChild(configNode); I can do document.getDocumentElement(); and it returns the [config: null].
What has changed in 1.5 that breaks creating XML documents? And what is the new correct way to do it?
Any help would be greatly appreciated.

Hmm, ok. We were doing the following to write out the file:
BufferedWriter out = new BufferedWriter(new OutputStreamWriter(
                                            new FileOutputStream(configFile)));
         out.write(headerString); // headerString being <?xml version="1.0" encoding="ISO-8859-1" ?>
         out.newLine();
         out.newLine();
         out.write(document.getDocumentElement().toString());
         out.flush();
         out.close();And before document.getDocumentElement returned the XML so we were able to just write it out, but in 1.5 it was returning the [config: null] thing.

Writing to an xml document, not working.

Hey all,
I'm trying to do something pretty simple, just setting up a phone forwarding script (I believe it is the one that came with CCX) that reads XML documents to forward and unforward the phones. But I cant for the life of me get the script to actually write to a status file on ccx. Please take a look at my script and help me out.

Figured it out. You have to write to a different directory.

To retrieve the PRT document (a PDF file) and insert the doc in PM order

Hello guys,
I have a challenging task in from printing as follows,
By using TC: IW3D we get print preview of PM Order Set (PM Print Program: YIPRJT01), currently the PRT document number prints in the PM Order. Now we have to insert the PRT documents (a PDF file) into the PM Order set rather than printing the PRT document number ( By using TC: IW33 by going OPERTIONAL TAB we will get the PRT document(a PDF file))
The requirement is to retrieve the PRT document (a PDF file) and insert the document in PM order set with out navigating separately by using the TC: IW33.
If you run the script in the print preview we can able to see PM the order set along with the PRT document (a PDF file).
Thanks & Regards
Vishnu

I'm also trying to print PRT document with shop papers and still not able to do so. I selected "P" for print on the control key and it should print but still didn't print.
If I understand it right, I think you are trying to do the same.
Have you resolved this issue ?
Thank you,
Sam

How to set the encoding of an XML-document

I need to change the encoding of an xml-document.
When I convert the document into a string, UTF-8
is used, I want to use ISO-8859-1.

use this in your identity transform:
transformer.setOutputProperty(OutputKeys.ENCODING, "ISO-8859-1");

Resubmitting the archived XML Documents?

Hi,
I just wanted to confirm whether archived XML documents can be resubmitted?
The XI message has been archived in a storage system and now its required to retrieve it in XI system.
Does XI allow this resubmitting?
Edited by: sriparna1 on Nov 16, 2009 8:11 AM

Hi Sriparna,
Synchronous messages occupy lot of space in the memory/database and hence they are not persisted by default.
If you want the synchronous messages to be persisted, then follow this blog:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1629352550DB00149050467001567547End?blog=/pub/wlg/1629
Refer this discussion to understand the concept of persistence with respec to sync msgs.
Synchronous Messages persistence in XI
And regarding your question about "How are the successfull and erroneous synchronous messages handled while archiving",
it is very staright forward.
By default, all the succesful messages are archived by the archiving job.
The error messages are not archived.
If you want the error messages to be archived, you have to Cancel them.
After canceling, the status changes from error to cancelled. Then the archiving job will archive the cancelled messages also.
Regards,
Ravi Kanth Talagana

Writing XML Document to a file or the console

Similar Messages

Maybe you are looking for