Insertion in the xml document

a-o-a
i am trying to insert a block of elements in an xml file.infact in xml file there
is an elemnt data. when last element of data is ended then i want
to insert data element block in xml file in the end Document method of sax api.
i am unable to do so.
element is
 <data>
<fname>any name </fname>
</data> 
can any one give me the guidance that how can i insert it at the end of file
using sax api.
Thanx very much to him/her.

I used DOM objects to be able to modify the document. I used some methods like:
document.createTextNode(textValue)
document.createElement(tagName)
You can look them up.

Similar Messages

Date insertion from large XML document (clob) into relation table very slow

Hi Everybody!
I'm working with Oracle 9.2.0.5 on Microsoft Windows Server 2003 Enterprise Edition.
The server (a test server) is a Pentium 4 2.8 GHz, 1GB of RAM.
I use a procedure called PARITOP_TRAITERXMLRESULTMASSE to insert the data contained in the pXMLDOC clob parameter in the table pTABLENAME. (You can see the format of the XML document below). The first step on this procedure is to verify that the XML document is not empty. If not, the procedure needs to add a node in the document, in every <ROW> tag. This added node is named âRST_IDâ. Itâs the foreign key of each record. I can retrieve the value of each <RST_ID> node in an other table in which the data has been previously added (by the calling procedure). When each of the <ROW> elements has been treated, the PARITOP_INSERTXML procedure is called. This procedure uses DBMS_XMLSAVE.INSERTXML to insert the data contained in the XML document in the specified table.
(Below, you can see the code of my procedures.)
With this information, can you tell me why this treatment is very very very slow with a large XML document and how I can improve it?
Thank you for your help!
Anne-Marie
CREATE OR REPLACE PROCEDURE "PARITOP_TRAITERXMLRESULTMASSE" (
pPRC_ID IN PARITOP_PARC.PRC_ID%TYPE,
pRST_MONDE IN PARITOP_RESULTAT.RST_MONDE%TYPE,
pXMLDOC IN CLOB,
pTABLENAME IN VARCHAR2)
AS
Objectif :InsÃ©rer le contenu du XML passÃ© en paramÃ¨tre (pXMLDOC) Ã la table passÃ©e en paramÃ¨tre (pTABLENAME)
La table passÃ©e en paramÃ¨tre doit Ãªtre une table ayant comme clÃ© Ã©trangÃ¨re le champs "RST_ID" .
(Le noeud RST_ID est donc ajoutÃ© Ã tous les document XML. Ce rst_id est
dÃ©terminÃ© Ã partir de la table PARITOP_RESULTAT grÃ¢ce Ã pPRC_ID et
pRstMonde fournis en paramÃ¨tre)
result_doc CLOB;
XMLDOMDOC XDB.DBMS_XMLDOM.DOMDOCUMENT;
NODE_ROWSET DBMS_XMLDOM.DOMNODE;
NODE_ROW DBMS_XMLDOM.DOMNODE;
vUE_ID PARITOP_RESULTAT.UE_ID%TYPE;
vRST_ID PARITOP_RESULTAT.RST_ID%TYPE;
nodeList DBMS_XMLDOM.DOMNODELIST;
BEGIN
BEGIN
vUE_ID := 0;
vRST_ID := 0;
XMLDOMDOC := DBMS_XMLDOM.NEWDOMDOCUMENT(pXMLDOC);
IF NOT GESTXML_PKG.FN_PARITOP_DOCUMENT_IS_NULL(XMLDOMDOC) THEN
NODE_ROWSET := DBMS_XMLDOM.item(DBMS_XMLDOM.GETCHILDNODES (DBMS_XMLDOM.MAKENODE(XMLDOMDOC)),0);
for i in 0..dbms_xmldom.getLength(DBMS_XMLDOM.getchildnodes(NODE_ROWSET))-1 loop
NODE_ROW := DBMS_XMLDOM.ITEM(DBMS_XMLDOM.GETCHILDNODES(NODE_ROWSET), i) ;
nodeList := DBMS_XMLDOM.GETELEMENTSBYTAGNAME(DBMS_XMLDOM.makeelement(NODE_ROW) , 'UE_ID');
IF vUE_ID <> DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0))) THEN
vUE_ID := DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0)));
--on ramasse le rst_id
SELECT RST_ID INTO vRST_ID
FROM PARITOP_RESULTAT RST
WHERE RST.PRC_ID = pPRC_ID
AND RST.UE_ID = vUE_ID
AND RST.RST_MONDE = pRST_MONDE
AND RST_A_SUPPRIMER = 0;
END IF;
GESTXML_PKG.PARITOP_ADDNODETOROW(XMLDOMDOC, NODE_ROW, 'RST_ID', vRST_ID);
end loop;
RESULT_DOC := ' '; --Ã garder, pour ne pas que ca fasse d'erreur lors du WriteToClob.
dbms_xmldom.writeToClob(DBMS_XMLDOM.MAKENODE(XMLDOMDOC), RESULT_DOC);
--Insertion du document XML dans la table "tableName"
GESTXML_PKG.PARITOP_INSERTXML(RESULT_DOC, pTABLENAME);
DBMS_XMLDOM.FREEDOCUMENT( XMLDOMDOC);
end if;
EXCEPTION
[â¦exception treatementâ¦]
END;
END;
The format of a XML clob is :
<ROWSET>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6223</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>92.307692307692307</CMP_INDICESELECTION>
<CMP_PVRES>94900</CMP_PVRES>
<CMP_PVAJUSTE>72678.017699115066</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>72678.017699115095</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>72678.017699115037</CMP_PVAJUSTEMAX>
<CMP_PV>148000</CMP_PV>
<CMP_VALROLE>129400</CMP_VALROLE>
<CMP_PVRESECART>4790</CMP_PVRESECART>
<CMP_PVRHAB>101778.01769911509</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>148000</CMP_PVA>
</ROW>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6235</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>76.92307692307692</CMP_INDICESELECTION>
<CMP_PVRES>117800</CMP_PVRES>
<CMP_PVAJUSTE>118080</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>118080</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>118080</CMP_PVAJUSTEMAX>
<CMP_PV>172000</CMP_PV>
<CMP_VALROLE>134800</CMP_VALROLE>
<CMP_PVRESECART>0</CMP_PVRESECART>
<CMP_PVRHAB>147180</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>172000</CMP_PVA>
</ROW>
</ROWSET>
PARITOP_COMPARABLE TABLE :
RST_ID NUMBER(10) NOT NULL,
VEN_ID NUMBER(10) NOT NULL,
CMP_SELMAN NUMBER(1) NOT NULL,
CMP_UTILISE NUMBER(1) NOT NULL,
CMP_INDICESELECTION FLOAT(53) NOT NULL,
CMP_PVRES FLOAT(53) NULL,
CMP_PVAJUSTE FLOAT(53) NULL,
CMP_PVRHAB FLOAT(53) NULL,
CMP_TVM FLOAT(53) NULL
ROCEDURE PARITOP_INSERTXML (xmlDoc IN clob, tableName IN VARCHAR2)
AS
insCtx DBMS_XMLSave.ctxType;
rowss number;
BEGIN
--permet d'insÃ©rer les champs du XML dans la table passÃ©e en paramÃ¨tre.
--il suffit que les champs XML aient le mÃªme nom que les champs de la table
BEGIN
insCtx := DBMS_XMLSave.newContext(tableName); -- get context handle
DBMS_XMLSAVE.SETDATEFORMAT( insCtx, 'yyyy-MM-dd HH:mm:ss');--attention, case sensitive
DBMS_XMLSAVE.setIgnoreCase(insCtx, 1);
rowss := DBMS_XMLSAVE.INSERTXML(insCtx , xmlDoc);
DBMS_XMLSave.closeContext(insCtx);
EXCEPTION
[â¦]
END;
END;
PROCEDURE PARITOP_ADDNODETOROW (
XMLDOMDOC DBMS_XMLDOM.DOMDOCUMENT,
NODE_ROW dbms_xmldom.DOMNode,
NOM_NOEUD VARCHAR2,
VALEUR_NOEUD VARCHAR2)
AS
--PERMET D'AJOUTER UN NOEUD AVEC 1 SEULE VALEUR DANS une ROW D'UN XML.
--UTILE SURTOUT POUR LES CLÃS ÃTRANGÃRES
domElemAInserer DBMS_XMLDOM.DOMELEMENT;
NODE dbms_xmldom.DOMNode;
NODE_TMP dbms_xmldom.DOMNode;
BEGIN
domElemAInserer := DBMS_XMLDOM.createElement(XMLDOMDOC, NOM_NOEUD) ;
NODE := DBMS_XMLDOM.MAKENODE(domElemAInserer); --cast
NODE := DBMS_XMLDOM.APPENDCHILD(NODE_ROW,NODE);
NODE_TMP := DBMS_XMLDOM.MAKENODE(DBMS_XMLDOM.CREATETEXTNODE(XMLDOMDOC, VALEUR_NOEUD ) );
NODE := DBMS_XMLDOM.APPENDCHILD(NODE,NODE_TMP );
END;

Hi Everybody!
I'm working with Oracle 9.2.0.5 on Microsoft Windows Server 2003 Enterprise Edition.
The server (a test server) is a Pentium 4 2.8 GHz, 1GB of RAM.
I use a procedure called PARITOP_TRAITERXMLRESULTMASSE to insert the data contained in the pXMLDOC clob parameter in the table pTABLENAME. (You can see the format of the XML document below). The first step on this procedure is to verify that the XML document is not empty. If not, the procedure needs to add a node in the document, in every <ROW> tag. This added node is named âRST_IDâ. Itâs the foreign key of each record. I can retrieve the value of each <RST_ID> node in an other table in which the data has been previously added (by the calling procedure). When each of the <ROW> elements has been treated, the PARITOP_INSERTXML procedure is called. This procedure uses DBMS_XMLSAVE.INSERTXML to insert the data contained in the XML document in the specified table.
(Below, you can see the code of my procedures.)
With this information, can you tell me why this treatment is very very very slow with a large XML document and how I can improve it?
Thank you for your help!
Anne-Marie
CREATE OR REPLACE PROCEDURE "PARITOP_TRAITERXMLRESULTMASSE" (
pPRC_ID IN PARITOP_PARC.PRC_ID%TYPE,
pRST_MONDE IN PARITOP_RESULTAT.RST_MONDE%TYPE,
pXMLDOC IN CLOB,
pTABLENAME IN VARCHAR2)
AS
Objectif :InsÃ©rer le contenu du XML passÃ© en paramÃ¨tre (pXMLDOC) Ã la table passÃ©e en paramÃ¨tre (pTABLENAME)
La table passÃ©e en paramÃ¨tre doit Ãªtre une table ayant comme clÃ© Ã©trangÃ¨re le champs "RST_ID" .
(Le noeud RST_ID est donc ajoutÃ© Ã tous les document XML. Ce rst_id est
dÃ©terminÃ© Ã partir de la table PARITOP_RESULTAT grÃ¢ce Ã pPRC_ID et
pRstMonde fournis en paramÃ¨tre)
result_doc CLOB;
XMLDOMDOC XDB.DBMS_XMLDOM.DOMDOCUMENT;
NODE_ROWSET DBMS_XMLDOM.DOMNODE;
NODE_ROW DBMS_XMLDOM.DOMNODE;
vUE_ID PARITOP_RESULTAT.UE_ID%TYPE;
vRST_ID PARITOP_RESULTAT.RST_ID%TYPE;
nodeList DBMS_XMLDOM.DOMNODELIST;
BEGIN
BEGIN
vUE_ID := 0;
vRST_ID := 0;
XMLDOMDOC := DBMS_XMLDOM.NEWDOMDOCUMENT(pXMLDOC);
IF NOT GESTXML_PKG.FN_PARITOP_DOCUMENT_IS_NULL(XMLDOMDOC) THEN
NODE_ROWSET := DBMS_XMLDOM.item(DBMS_XMLDOM.GETCHILDNODES (DBMS_XMLDOM.MAKENODE(XMLDOMDOC)),0);
for i in 0..dbms_xmldom.getLength(DBMS_XMLDOM.getchildnodes(NODE_ROWSET))-1 loop
NODE_ROW := DBMS_XMLDOM.ITEM(DBMS_XMLDOM.GETCHILDNODES(NODE_ROWSET), i) ;
nodeList := DBMS_XMLDOM.GETELEMENTSBYTAGNAME(DBMS_XMLDOM.makeelement(NODE_ROW) , 'UE_ID');
IF vUE_ID <> DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0))) THEN
vUE_ID := DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.ITEM(nodeList, 0)));
--on ramasse le rst_id
SELECT RST_ID INTO vRST_ID
FROM PARITOP_RESULTAT RST
WHERE RST.PRC_ID = pPRC_ID
AND RST.UE_ID = vUE_ID
AND RST.RST_MONDE = pRST_MONDE
AND RST_A_SUPPRIMER = 0;
END IF;
GESTXML_PKG.PARITOP_ADDNODETOROW(XMLDOMDOC, NODE_ROW, 'RST_ID', vRST_ID);
end loop;
RESULT_DOC := ' '; --Ã garder, pour ne pas que ca fasse d'erreur lors du WriteToClob.
dbms_xmldom.writeToClob(DBMS_XMLDOM.MAKENODE(XMLDOMDOC), RESULT_DOC);
--Insertion du document XML dans la table "tableName"
GESTXML_PKG.PARITOP_INSERTXML(RESULT_DOC, pTABLENAME);
DBMS_XMLDOM.FREEDOCUMENT( XMLDOMDOC);
end if;
EXCEPTION
[â¦exception treatementâ¦]
END;
END;
The format of a XML clob is :
<ROWSET>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6223</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>92.307692307692307</CMP_INDICESELECTION>
<CMP_PVRES>94900</CMP_PVRES>
<CMP_PVAJUSTE>72678.017699115066</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>72678.017699115095</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>72678.017699115037</CMP_PVAJUSTEMAX>
<CMP_PV>148000</CMP_PV>
<CMP_VALROLE>129400</CMP_VALROLE>
<CMP_PVRESECART>4790</CMP_PVRESECART>
<CMP_PVRHAB>101778.01769911509</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>148000</CMP_PVA>
</ROW>
<ROW>
<PRC_ID>193</PRC_ID>
<UE_ID>8781</UE_ID>
<VEN_ID>6235</VEN_ID>
<RST_MONDE>0</RST_MONDE>
<CMP_SELMAN>0</CMP_SELMAN>
<CMP_INDICESELECTION>76.92307692307692</CMP_INDICESELECTION>
<CMP_PVRES>117800</CMP_PVRES>
<CMP_PVAJUSTE>118080</CMP_PVAJUSTE>
<CMP_PVAJUSTEMIN>118080</CMP_PVAJUSTEMIN>
<CMP_PVAJUSTEMAX>118080</CMP_PVAJUSTEMAX>
<CMP_PV>172000</CMP_PV>
<CMP_VALROLE>134800</CMP_VALROLE>
<CMP_PVRESECART>0</CMP_PVRESECART>
<CMP_PVRHAB>147180</CMP_PVRHAB>
<CMP_UTILISE>1</CMP_UTILISE>
<CMP_TVM>1</CMP_TVM>
<CMP_PVA>172000</CMP_PVA>
</ROW>
</ROWSET>
PARITOP_COMPARABLE TABLE :
RST_ID NUMBER(10) NOT NULL,
VEN_ID NUMBER(10) NOT NULL,
CMP_SELMAN NUMBER(1) NOT NULL,
CMP_UTILISE NUMBER(1) NOT NULL,
CMP_INDICESELECTION FLOAT(53) NOT NULL,
CMP_PVRES FLOAT(53) NULL,
CMP_PVAJUSTE FLOAT(53) NULL,
CMP_PVRHAB FLOAT(53) NULL,
CMP_TVM FLOAT(53) NULL
ROCEDURE PARITOP_INSERTXML (xmlDoc IN clob, tableName IN VARCHAR2)
AS
insCtx DBMS_XMLSave.ctxType;
rowss number;
BEGIN
--permet d'insÃ©rer les champs du XML dans la table passÃ©e en paramÃ¨tre.
--il suffit que les champs XML aient le mÃªme nom que les champs de la table
BEGIN
insCtx := DBMS_XMLSave.newContext(tableName); -- get context handle
DBMS_XMLSAVE.SETDATEFORMAT( insCtx, 'yyyy-MM-dd HH:mm:ss');--attention, case sensitive
DBMS_XMLSAVE.setIgnoreCase(insCtx, 1);
rowss := DBMS_XMLSAVE.INSERTXML(insCtx , xmlDoc);
DBMS_XMLSave.closeContext(insCtx);
EXCEPTION
[â¦]
END;
END;
PROCEDURE PARITOP_ADDNODETOROW (
XMLDOMDOC DBMS_XMLDOM.DOMDOCUMENT,
NODE_ROW dbms_xmldom.DOMNode,
NOM_NOEUD VARCHAR2,
VALEUR_NOEUD VARCHAR2)
AS
--PERMET D'AJOUTER UN NOEUD AVEC 1 SEULE VALEUR DANS une ROW D'UN XML.
--UTILE SURTOUT POUR LES CLÃS ÃTRANGÃRES
domElemAInserer DBMS_XMLDOM.DOMELEMENT;
NODE dbms_xmldom.DOMNode;
NODE_TMP dbms_xmldom.DOMNode;
BEGIN
domElemAInserer := DBMS_XMLDOM.createElement(XMLDOMDOC, NOM_NOEUD) ;
NODE := DBMS_XMLDOM.MAKENODE(domElemAInserer); --cast
NODE := DBMS_XMLDOM.APPENDCHILD(NODE_ROW,NODE);
NODE_TMP := DBMS_XMLDOM.MAKENODE(DBMS_XMLDOM.CREATETEXTNODE(XMLDOMDOC, VALEUR_NOEUD ) );
NODE := DBMS_XMLDOM.APPENDCHILD(NODE,NODE_TMP );
END;

Remove first line in the XML Document

Hi Friends,
In my File to File scenario when ever new mesg is appending to file at receiver side,it should remove <?xml version="1.0" encoding="ISO-8859-1"?> tag from the XML Document.This means <?xml version="1.0" encoding="ISO-8859-1"?> tag should appear once in a document.Plz suggest me to do this.
Thanks
pullarao.

Hi there,
you can either use XSLT (with output type="text") or Java, using the code:
try {
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
Document doc = docBuilder.parse(in);
TransformerFactory tf = TransformerFactory.newInstance();
Transformer trans = tf.newTransformer();
trans.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
DOMSource source = new DOMSource(doc);
OutputStream out = new ByteArrayOutputStream();
trans.transform(source, new StreamResult(out));
} catch (...
But as Bhavesh said, append mode is not recommended for XML files.
Best approach is collect pattern on BPM.
Regards,
Henrique.

String representation of the xml document

hi, I have created the following xml document using the DOM api. I want to the "function" to return a "string" - which represents the xml document i created. How do u do that?
As of now it doesnt return anything...
How do u return the entire xml document as character data..? just like
<root><elements>data</elements></root>....
anyhelp would be great.
import java.io.*;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import org.w3c.dom.*;
public class test1{
private static void function()throws IOException, DOMException{
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance ();
DocumentBuilder db = dbf.newDocumentBuilder ();
Document doc = db.newDocument ();
Element record = doc.createElement ("record");
Element name = doc.createElement ("name");
Element address = doc.createElement ("address");
Element zip = doc.createElement ("zip");
Text nameText = doc.createTextNode("bill");
Text addressText = doc.createTextNode("128, washington");
Text zipText = doc.createTextNode("10000");
doc.appendChild(record);
record.appendChild(name);
name.appendChild(nameText);
record.appendChild(address);
address.appendChild(addressText);
record.appendChild(zip);
zip.appendChild(zipText);
public static void main (String argv [])throws Exception {
function();
}

Brent,
Looks like you're using the Sun Java Parser. I'll show you how to do it with the Oracle XML Parser and you can extrapolate...
Document doc = new XMLDocument();
// Stuff here to build up the DOM Doc
// with elements, etc.
// Print the Document to a String
StringWriter sw = new StringWriter();
// Wrap the stringwriter in a printwriter
PrintWriter pw = new PrintWriter(sw);
// Print to the printwriter
((XMLDocument)doc).print(pw);
// return the string from the stringwriter
return sw.toString();

Not able to validate the xml document against DTD using SAX

Hi ,
i am not able to validate xml document against its DTD using SAX parser even after setting setValidating = true. even if the file is not correct according to DTD , it is not throwing any exception. what could be the reason.? please help..
kranthi
this is the code sample i used.
SAXParserFactory factory = SAXParserFactory.newInstance();
factory.setValidating(true);
     try {
factory.newSAXParser().parse(new File("sample.xml"), handler);
     } catch (SAXException e) {
     e.printStackTrace();                         System.exit(2);
     } catch (ParserConfigurationException e) {
e.printStackTrace();
}

Hi karthik
Thanks for your response
Actually iam a beginner in java coding hence struggling to come up with the things
I tried putting your code and onserver side i see it is returning 09:12:17,234 INFO [STDOUT] [root: null]
actually the same program i wrote in java
and the same method i was calling from the main
and it is working fine and the xml document is getting displayed one important thing to be noted here is that the factory.newDocumentBuilder().parse(new File(filename));is returing XmlDocument
and the printing takes place
but the in same method public static Document parseXMLFile(String filename, boolean b) in servlet
the line factory.newDocumentBuilder().parse(new File(filename)); is returning DeferredDocumentImpl
and this creating problem , had it returned XmlDocument
i would have printed the elements one one
but as it is returning deferredimpl
iam unable to print the elements
could you please tell me why factory.newDocumentBuilder().parse(new File(filename)); is returning DeferredDocumentImpl
in servlets but in plain java pogram it is returing XmlDocument
Thanks
Bhanu

Exchange 2007 - The XML document ended unexpectedly.

Hello,
I'm trying to connect with a exchange server 2007 sp3 through EWS.
I can connect but when I try to retrieve a calendar item I'm getting this error:
The XML document ended unexpectedly.
It seems that the EWS/Exchange isn't well configurated.
I tried it in the EWSEditor and the result is the same.
I checked the connectivity in the shell and all the results were ok.
Any new idea to test?
Thanks!

Did you ever get a fix for this, i have the exact same issue and my MAC clients cannot use ews.

Exchange 2013 - The XML document ended unexpectedly

ExchangeService service = new ExchangeService(ExchangeVersion.Exchange2013);
service.Url = new Uri(exchangeUrl);
service.Credentials = new NetworkCredential(cred.Username, cred.Password);
FolderId parentFolderId = new FolderId(WellKnownFolderName.Calendar, mailbox);
var item = UserConfiguration.Bind(service, name, parentFolderId,
UserConfigurationProperties.BinaryData);
item.BinaryData = value;
item.Update();
Everytime when I'm calling the Exchange Web Services for Exchange 2013 I'm getting the following message...
Microsoft.Exchange.WebServices.Data.ServiceXmlDeserializationException: The XML document ended unexpectedly.
   at Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
   at Microsoft.Exchange.WebServices.Data.SoapFaultDetails.ParseDetailNode(EwsXmlReader reader)
   at Microsoft.Exchange.WebServices.Data.SoapFaultDetails.Parse(EwsXmlReader reader, XmlNamespace soapNamespace)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ReadSoapFault(EwsServiceXmlReader reader)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ProcessWebException(WebException webException)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
   at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
   at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()
   at Microsoft.Exchange.WebServices.Data.ExchangeService.GetUserConfiguration(String name, FolderId parentFolderId, UserConfigurationProperties properties)
   at Microsoft.Exchange.WebServices.Data.UserConfiguration.Bind(ExchangeService service, String name, FolderId parentFolderId, UserConfigurationProperties properties)
I the dev environment everything is working fine, but not in integration. Any ideas? Please help.
Thanks,
Bernhard

It sounds like it failing to parse the SOAP response that's coming back from EWS, you need to enable tracing and have a look at the response
http://msdn.microsoft.com/en-us/library/office/dd633676(v=exchg.80).aspx , are you running the same Service Pack/Rollup version in dev and production?
Cheers
Glen

The XML document builds on itself when called twice. Help!!!

When I run the Sample program for the Oracle classgen for Java
the XML document node repeats itself when called the second
time. This is what I mean:
import oracle.xml.classgen.*;
import oracle.xml.parser.*;
public class TestWidl
static WIDL w1 = new WIDL();
public static void main (String args[])
test();
test();
static void test ()
try
DTD dtd = w1.getDTDNode();
w1.setNAME("WIDL1");
w1.setVERSION(WIDL.VERSION_1_0);
SERVICE s1 = new SERVICE("Service1", "Service_URL");
s1.setINPUT("File");
s1.setOUTPUT("File");
BINDING b1 = new BINDING("Binding1");
b1.setTYPE(BINDING.TYPE_INPUT);
BINDING b2 = new BINDING("Binding2");
b2.setTYPE(BINDING.TYPE_OUTPUT);
VARIABLE v1 = new VARIABLE("Variable1",
VARIABLE.NULLOK_FALSE);
v1.setTYPE(VARIABLE.TYPE_STRING);
v1.setUSAGE(VARIABLE.USAGE_INTERNAL);
v1.setVALUE("value");
VARIABLE v2 = new VARIABLE("Variable2",
VARIABLE.NULLOK_TRUE);
v2.setTYPE(VARIABLE.TYPE_STRING1);
v2.setUSAGE(VARIABLE.USAGE_HEADER);
VARIABLE v3 = new VARIABLE("Variable3",
VARIABLE.NULLOK_FALSE);
v3.setTYPE(VARIABLE.TYPE_STRING2);
v3.setUSAGE(VARIABLE.USAGE_FUNCTION);
v3.setMASK("mask");
CONDITION c1 = new CONDITION("CRef1", "CMatch1");
c1.setSERVICE("Service1");
c1.setTYPE(CONDITION.TYPE_SUCCESS);
CONDITION c2 = new CONDITION("CRef2", "CMatch2");
c2.setTYPE(CONDITION.TYPE_RETRY);
CONDITION c3 = new CONDITION("CRef3", "CMatch3");
c3.setSERVICE("Service3");
c3.setTYPE(CONDITION.TYPE_FAILURE);
REGION r1 = new REGION("Region1", "Start", "End");
b1.addNode(r1);
b1.addNode(v1);
b1.addNode(c1);
b1.addNode(v2);
b2.addNode(c2);
b2.addNode(v3);
w1.addNode(s1);
w1.addNode(b1);
w1.addNode(b2);
w1.validateContent();
w1.print(System.out);
catch (Exception e)
System.out.println(e.toString());
e.printStackTrace();
The XML output looks like this:
First Call to test():
<?xml version = '1.0' encoding = 'ASCII'?>
<!DOCTYPE WIDL SYSTEM "file:/home/hmiranda/tmp/WIDL_dtd.txt">
<WIDL NAME="WIDL1" VERSION="1.0">
<SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
OUTPUT="File"/>
<BINDING NAME="Binding1" TYPE="Input">
<REGION NAME="Region1" START="Start" END="End"/>
<VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
USAGE="Internal" VALUE="value"/>
<CONDITION REF="CRef1" MATCH="CMatch1" SERVICE="Service1"
TYPE="Success"/>
<VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
USAGE="Header"/>
</BINDING>
<BINDING NAME="Binding2" TYPE="Output">
<CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
<VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
USAGE="Function" MASK="mask"/>
</BINDING>
</WIDL>
Second Call to test:
Please note how service1 repeats itself. I would expect that
the XML string would look like the first output:
How can I fix this??
<?xml version = '1.0' encoding = 'ASCII'?>
<!DOCTYPE WIDL SYSTEM "file:/home/hmiranda/tmp/WIDL_dtd.txt">
<WIDL NAME="WIDL1" VERSION="1.0">
<SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
OUTPUT="File"/>
<BINDING NAME="Binding1" TYPE="Input">
<REGION NAME="Region1" START="Start" END="End"/>
<VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
USAGE="Internal" VALUE="value"/>
<CONDITION REF="CRef1" MATCH="CMatch1" SERVICE="Service1"
TYPE="Success"/>
<VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
USAGE="Header"/>
</BINDING>
<BINDING NAME="Binding2" TYPE="Output">
<CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
<VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
USAGE="Function" MASK="mask"/>
</BINDING>
<SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
OUTPUT="File"/>
<BINDING NAME="Binding1" TYPE="Input">
<REGION NAME="Region1" START="Start" END="End"/>
<VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
USAGE="Internal" VALUE="value"/>
<CONDITION REF="CRef1" MATCH="CMatch1" SERVICE="Service1"
TYPE="Success"/>
<VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
USAGE="Header"/>
</BINDING>
<BINDING NAME="Binding2" TYPE="Output">
<CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
<VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
USAGE="Function" MASK="mask"/>
</BINDING>
</WIDL>
Any Help is appreciated.
Hector.
null

Hector Miranda (guest) wrote:
: When I run the Sample program for the Oracle classgen for Java
: the XML document node repeats itself when called the second
: time. This is what I mean:
: import oracle.xml.classgen.*;
: import oracle.xml.parser.*;
: public class TestWidl
: static WIDL w1 = new WIDL();
: public static void main (String args[])
: test();
: test();
: static void test ()
: try
: DTD dtd = w1.getDTDNode();
: w1.setNAME("WIDL1");
: w1.setVERSION(WIDL.VERSION_1_0);
: SERVICE s1 = new SERVICE("Service1", "Service_URL");
: s1.setINPUT("File");
: s1.setOUTPUT("File");
: BINDING b1 = new BINDING("Binding1");
: b1.setTYPE(BINDING.TYPE_INPUT);
: BINDING b2 = new BINDING("Binding2");
: b2.setTYPE(BINDING.TYPE_OUTPUT);
: VARIABLE v1 = new VARIABLE("Variable1",
: VARIABLE.NULLOK_FALSE);
: v1.setTYPE(VARIABLE.TYPE_STRING);
: v1.setUSAGE(VARIABLE.USAGE_INTERNAL);
: v1.setVALUE("value");
: VARIABLE v2 = new VARIABLE("Variable2",
: VARIABLE.NULLOK_TRUE);
: v2.setTYPE(VARIABLE.TYPE_STRING1);
: v2.setUSAGE(VARIABLE.USAGE_HEADER);
: VARIABLE v3 = new VARIABLE("Variable3",
: VARIABLE.NULLOK_FALSE);
: v3.setTYPE(VARIABLE.TYPE_STRING2);
: v3.setUSAGE(VARIABLE.USAGE_FUNCTION);
: v3.setMASK("mask");
: CONDITION c1 = new CONDITION("CRef1", "CMatch1");
: c1.setSERVICE("Service1");
: c1.setTYPE(CONDITION.TYPE_SUCCESS);
: CONDITION c2 = new CONDITION("CRef2", "CMatch2");
: c2.setTYPE(CONDITION.TYPE_RETRY);
: CONDITION c3 = new CONDITION("CRef3", "CMatch3");
: c3.setSERVICE("Service3");
: c3.setTYPE(CONDITION.TYPE_FAILURE);
: REGION r1 = new REGION("Region1", "Start", "End");
: b1.addNode(r1);
: b1.addNode(v1);
: b1.addNode(c1);
: b1.addNode(v2);
: b2.addNode(c2);
: b2.addNode(v3);
: w1.addNode(s1);
: w1.addNode(b1);
: w1.addNode(b2);
: w1.validateContent();
: w1.print(System.out);
: catch (Exception e)
: System.out.println(e.toString());
: e.printStackTrace();
: The XML output looks like this:
: First Call to test():
: <?xml version = '1.0' encoding = 'ASCII'?>
: <!DOCTYPE WIDL SYSTEM "file:/home/hmiranda/tmp/WIDL_dtd.txt">
: <WIDL NAME="WIDL1" VERSION="1.0">
: <SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
: OUTPUT="File"/>
: <BINDING NAME="Binding1" TYPE="Input">
: <REGION NAME="Region1" START="Start" END="End"/>
: <VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
: USAGE="Internal" VALUE="value"/>
: <CONDITION REF="CRef1" MATCH="CMatch1"
SERVICE="Service1"
: TYPE="Success"/>
: <VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
: USAGE="Header"/>
: </BINDING>
: <BINDING NAME="Binding2" TYPE="Output">
: <CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
: <VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
: USAGE="Function" MASK="mask"/>
: </BINDING>
: </WIDL>
: Second Call to test:
: Please note how service1 repeats itself. I would expect that
: the XML string would look like the first output:
: How can I fix this??
: <?xml version = '1.0' encoding = 'ASCII'?>
: <!DOCTYPE WIDL SYSTEM "file:/home/hmiranda/tmp/WIDL_dtd.txt">
: <WIDL NAME="WIDL1" VERSION="1.0">
: <SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
: OUTPUT="File"/>
: <BINDING NAME="Binding1" TYPE="Input">
: <REGION NAME="Region1" START="Start" END="End"/>
: <VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
: USAGE="Internal" VALUE="value"/>
: <CONDITION REF="CRef1" MATCH="CMatch1"
SERVICE="Service1"
: TYPE="Success"/>
: <VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
: USAGE="Header"/>
: </BINDING>
: <BINDING NAME="Binding2" TYPE="Output">
: <CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
: <VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
: USAGE="Function" MASK="mask"/>
: </BINDING>
: <SERVICE NAME="Service1" URL="Service_URL" INPUT="File"
: OUTPUT="File"/>
: <BINDING NAME="Binding1" TYPE="Input">
: <REGION NAME="Region1" START="Start" END="End"/>
: <VARIABLE NAME="Variable1" NULLOK="False" TYPE="String"
: USAGE="Internal" VALUE="value"/>
: <CONDITION REF="CRef1" MATCH="CMatch1"
SERVICE="Service1"
: TYPE="Success"/>
: <VARIABLE NAME="Variable2" NULLOK="True" TYPE="String1"
: USAGE="Header"/>
: </BINDING>
: <BINDING NAME="Binding2" TYPE="Output">
: <CONDITION REF="CRef2" MATCH="CMatch2" TYPE="Retry"/>
: <VARIABLE NAME="Variable3" NULLOK="False" TYPE="String2"
: USAGE="Function" MASK="mask"/>
: </BINDING>
: </WIDL>
: Any Help is appreciated.
: Hector.
Move
WIDL w1 = new WIDL();
out of test() and modify it as
public class TestWidl
static WIDL w1 = new WIDL(); ...
and this will work.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Error when parsing the XML document

hi all.
i have the next problem.
the sender sistem send to XI an XML. some tags send a '#' caracter.
Sender Service send:
Torre B1 - B#Unimev
when Im traying to test XML inbound, XI show the next error:
Error when parsing the XML document (Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0x14(:main:, row:1, col:992))
XML:
<?xml version="1.0" encoding="UTF-8" ?>
- <ZDEBMAS6>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
 <TABNAM>EDI_DC40</TABNAM>
 <MANDT>300</MANDT>
 <DOCNUM>0000000000339708</DOCNUM>
 <DOCREL>640</DOCREL>
 <STATUS>30</STATUS>
 <DIRECT>1</DIRECT>
 <OUTMOD>2</OUTMOD>
 </EDI_DC40>
- <E1KNA1M SEGMENT="1">
 <MSGFN>009</MSGFN>
 <REGIO>07</REGIO>
 <STCD1>20147972750</STCD1>
 <FITYP>01</FITYP>
 <STCDT>80</STCDT>
 <STCD3>0</STCD3>
- <Z1KNA1M SEGMENT="1">
 <MSGFN>009</MSGFN>
 <KUNNR>0001000563</KUNNR>
 <ZZSOCRCV>3100</ZZSOCRCV>
 <ZZGBDAT>00000000</ZZGBDAT>
 <ZZAD_STREET_CO>Torre B1 - B Unimev</ZZAD_STREET_CO>
 <ZZAD_ROOMNUM_CO>PB</ZZAD_ROOMNUM_CO>
 <ZZAD_FLOOR_CO>E</ZZAD_FLOOR_CO>
 <ZZAD_PSTCD1_CO>M5521AAR</ZZAD_PSTCD1_CO>
 <ZZAD_CITY1_CO>Mendoza</ZZAD_CITY1_CO>
 <ZZAD_REGIO_CO>07</ZZAD_REGIO_CO>
 </Z1KNA1M>
 <Z1ADRCM SEGMENT="1">
 <MSGFN>009</MSGFN>
 <KUNNR>0001000563</KUNNR>
 <STREET>Torre B1 - B Unimev</STREET>
 <FLOOR>PB</FLOOR>
 <HOUSE_NUM2>E</HOUSE_NUM2>
 <CITY1>Mendoza</CITY1>
 <POST_CODE1>5521</POST_CODE1>
 <COUNTRY>AR</COUNTRY>
 <REGION>07</REGION>
 <LANGU>S</LANGU>
 </Z1ADRCM>
 </E1KNA1M>
 </IDOC>
</ZDEBMAS6>
Message was edited by: Rodrigo Pertierra
Message was edited by: Rodrigo Pertierra

Hi Rodrigo,
Do you use a specific "encoding" like UTF-8 or ISO-8859-1 in your Sender CC.
Try changing the Transfer mode to Binary instead of Text.
Also go through these links:-
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
Invalid char in XML from inbound IDoc
Hope this provides a solution.
Regards.
Praveen

XSQL: How to embed the XML document(s) instead of posting?

Dear all.
I'm trying to use XSQL for a self-contained database schema setup. This setup should be able to handle DML (INSERT/UPDATE/DELETE), PL/SQL calls etc and I thought XSQL looks perfect for the job. As such, I wouldn't be using XSQL as a publishing framework but as kind of an ETL tool. The only output I would be interested in would be the xsql-status in order to check that the number of rows processed matches my expectations. I would prefer XSQL to run entirely within the database and not depend on any servlet container.
However, it seems that XSQL's only way of obtaining the canonical XML (ROWSET/ROW) that is used by xsql:insert-request/xsql:update-request/xsql:delete-request is through HTTP POST/GET. It doesn't seem that it's possible to embed the XML directly in the page, nor does it seem possible to handle more than one XML.
I'm trying to achieve something like this:
<?xml version="1.0"?>
<page connection="scott" xmlns:xsql="urn:oracle-xsq">
<xsql:insert-request table="DEPT">
<ROWSET>
<ROW>
<DEPTNO>-10</DEPTNO>
<DNAME>NEW DEPT 1</DNAME>
<LOC>COPENHAGEN</LOC>
</ROW>
<ROW>
<DEPTNO>-20</DEPTNO>
<DNAME>NEW DEPT 2</DNAME>
<LOC>LONDON</LOC>
</ROW>
</ROWSET>
</xsql:insert-request>
<xsql:insert-request table="EMP">
<ROWSET>
<ROW>
<EMPNO>-10</EMPNO>
<ENAME>NEW EMP 1</ENAME>
</ROW>
<ROW>
<EMPNO>-20</EMPNO>
<ENAME>NEW EMP 2</ENAME>
</ROW>
</ROWSET>
</xsql:insert-request>
</page>
or perhaps
<?xml version="1.0"?>
<page connection="scott" xmlns:xsql="urn:oracle-xsq">
<request>
<parameters>
<dept>
<ROWSET>
<ROW>
<DEPTNO>-10</DEPTNO>
<DNAME>NEW DEPT 1</DNAME>
<LOC>COPENHAGEN</LOC>
</ROW>
<ROW>
<DEPTNO>-20</DEPTNO>
<DNAME>NEW DEPT 2</DNAME>
<LOC>LONDON</LOC>
</ROW>
</ROWSET>
</dept>
</parameters>
</request>
<xsql:insert-request table="DEPT" param="dept"/>
<xsql:insert-request table="EMP" param="emp"/>
</page>
I need both INSERT/UPDATE/DELETE so xsql:insert-param isn't enough, would also need an xsql:update-param and xsql:delete-param.
A way of referring to the canonical XML through an URI or XPath expression (referring to a registered XML document in the database) would also be cool.
Perhaps implementing custom action handlers would work but not sure whether they'll be able to refer to any child XML elements within them? Furthermore, the syntax for these would also be slightly inconvenient:
<xsql:action handler=com.ellebaek-consulting.xsql.InsertActionHandler" table="DEPT">
My alternative would be to re-implement an extended version of XSQL (XSQLX :-)?) but I'm trying to avoid that.
Any pointers and ideas are very much appreciated.
Thanks in advance.
Best regards
Finn Ellebaek Nielsen

Hi.
Thanks for your reply but the article only talks about how to query data with XSQL and I need to INSERT/UPDATE/DELETE data embedded in XSQL pages into the database so I'm afraid that the article doesn't apply.
Cheers
Finn

Inserting a long XML document into XMLType

I'm trying to load the following document into an XMLType column in 10.2. I've tried every example I can find and can push the data into CLOBs using the Java work around just fine (http://www.oracle.com/technology/sample_code/tech/java/codesnippet/xmldb/HowToLoadLargeXML.html).
Can anyone provide a solution or let me know if there is a limitation please?
Given the table;
SQL> describe xmltable_1
Name Null? Type
DOC_ID NUMBER
XML_DATA XMLTYPE
How do I load this data into 'XML_DATA'?
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Rand McNally and ESRI</origin>
<pubdate>1996</pubdate>
<title>ESRI Cities Geodata Set</title>
<geoform>vector digital data</geoform>
<onlink>\\OIS23\C$\Files\Working\Metadata\world\cities.shp</onlink>
</citeinfo>
</citation>
<descript>
<abstract>World Cities contains locations of major cities around the world. The cities include national capitals for each of the countries in World Countries 1998 as well as major population centers and landmark cities. World Cities was derived from ESRI's ArcWorld database and supplemented with other data from the Rand McNally New International Atlas</abstract>
<purpose>606 points, 4 descriptive fields. Describes major world cities.</purpose>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>1996</caldate>
</sngdate>
</timeinfo>
<current>publication date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>None planned</update>
</status>
<spdom>
<bounding>
<westbc>
-165.270004</westbc>
<eastbc>
177.130188</eastbc>
<northbc>
78.199997</northbc>
<southbc>
-53.150002</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>city</themekt>
<themekey>cities</themekey>
</theme>
</keywords>
<accconst>none</accconst>
<useconst>none</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>unknown</cntper>
<cntorg>unknown</cntorg>
</cntperp>
<cntpos>unknown</cntpos>
<cntvoice>555-1212</cntvoice>
</cntinfo>
</ptcontac>
<datacred>ESRI</datacred>
<native>Microsoft Windows NT Version 4.0 (Build 1381) Service Pack 6; ESRI ArcCatalog 8.1.0.570</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>no report available</attraccr>
<qattracc>
<attraccv>1000000</attraccv>
<attracce>no report available</attracce>
</qattracc>
</attracc>
<logic>no report available</logic>
<complete>no report available</complete>
<posacc>
<horizpa>
<horizpar>no report available</horizpar>
</horizpa>
<vertacc>
<vertaccr>no report available</vertaccr>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<title>ESRI</title>
</citeinfo>
</srccite>
<srcscale>20000000</srcscale>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1996</caldate>
</sngdate>
</timeinfo>
<srccurr>publication date</srccurr>
</srctime>
<srccontr>no report available</srccontr>
</srcinfo>
<procstep>
<procdesc>no report available</procdesc>
<procdate>Unknown</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Entity point</sdtstype>
<ptvctcnt>606</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>0.000001</latres>
<longres>0.000001</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>North American Datum of 1927</horizdn>
<ellips>Clarke 1866</ellips>
<semiaxis>6378206.400000</semiaxis>
<denflat>294.978698</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
cities</enttypl>
</enttyp>
<attr>
<attrlabl>FID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>NAME</attrlabl>
<attrdef>The city name. Spellings are based on Board of Geographic Names standards and commercial atlases.</attrdef>
<attrdefs>ESRI</attrdefs>
</attr>
<attr>
<attrlabl>COUNTRY</attrlabl>
<attrdef>An abbreviated country name.</attrdef>
</attr>
<attr>
<attrlabl>POPULATION</attrlabl>
<attrdef>Total population for the entire metropolitan area. Values are from recent census or estimates.</attrdef>
</attr>
<attr>
<attrlabl>CAPITAL</attrlabl>
<attrdef>Indicates whether a city is a national capital (Y/N).</attrdef>
</attr>
</detailed>
<overview>
<eaover>none</eaover>
<eadetcit>none</eadetcit>
</overview>
</eainfo>
<distinfo>
<stdorder>
<digform>
<digtinfo>
<transize>0.080</transize>
</digtinfo>
</digform>
</stdorder>
</distinfo>
<metainfo>
<metd>20010509</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>ESRI</cntorg>
<cntper>unknown</cntper>
</cntorgp>
<cntaddr>
<addrtype>unknown</addrtype>
<city>unknown</city>
<state>unknown</state>
<postal>00000</postal>
</cntaddr>
<cntvoice>555-1212</cntvoice>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>
rtacce>Vertical Positional Accuracy is expressed in meters. Vertical accuracy figures were developed by comparing elevation contour locations on 1:24,000 scale maps to elevation values at the same location within the digital database. Some manual interpolation was necessary to complete this test. The analysis results are expressed as linear error at a 90% confidence interval.</vertacce>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>National Imagery and Mapping Agency</origin>
<pubdate>1994</pubdate>
<title>Operational Navigational Chart</title>
<geoform>map</geoform>
<pubinfo>
<pubplace>St.Louis, MO</pubplace>
<publish>National Imagery and Mapping Agency</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>1000000</srcscale>
<typesrc>stable-base material</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>1974</begdate>
<enddate>1994</enddate>
</rngdates>
</timeinfo>
<srccurr>Publication dates</srccurr>
</srctime>
<srccitea>ONC</srccitea>
<srccontr>All information found on the source with the exception of aeronautical data</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>National Imagery and Mapping Agency</origin>
<pubdate>199406</pubdate>
<title>Digital Aeronautical Flight Information File</title>
<geoform>model</geoform>
<pubinfo>
<pubplace>St. Louis, MO</pubplace>
<publish>National Imagery and Mapping Agency</publish>
</pubinfo>
</citeinfo>
</srccite>
<typesrc>magnetic tape</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>1994</caldate>
</sngdate>
</timeinfo>
<srccurr>Publication date</srccurr>
</srctime>
<srccitea>DAFIF</srccitea>
<srccontr>Airport records (name, International Civil Aviation Organization, position, elevation, and type)</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>Defense Mapping Agency</origin>
<pubdate>1994</pubdate>
<title>Jet Navigational Chart</title>
<geoform>map</geoform>
<pubinfo>
<pubplace>St.Louis, MO</pubplace>
<publish>Defense Mapping Agency</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>2,000,000</srcscale>
<typesrc>stable-base material</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>1974</begdate>
<enddate>1991</enddate>
</rngdates>
</timeinfo>
<srccurr>Publication date</srccurr>
</srctime>
<srccitea>JNC</srccitea>
<srccontr>All information found on the source with the exception of aeronautical data. JNCs were used as source for the Antartica region only.</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>USGS EROS Data Center</origin>
<pubdate></pubdate>
<title>Advance Very High Resolution Radiometer</title>
<geoform>remote-sensing image</geoform>
<pubinfo>
<pubplace>Sioux Falls, SD</pubplace>
<publish>EROS Data Center</publish>
</pubinfo>
</citeinfo>
</srccite>
<srcscale>1000000</srcscale>
<typesrc>magnetic tape</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>199003</begdate>
<enddate>199011</enddate>
</rngdates>
</timeinfo>
<srccurr>Publication date</srccurr>
</srctime>
<srccitea>AVHRR</srccitea>
<srccontr>6 vegetation types covering the continental US and Canada</srccontr>
</srcinfo>
<procstep>
<procdesc>For the first edition DCW, stable-based positives were produced from the original reproduction negatives (up to 35 per ONC sheet). These were digitized either through a scanning-raster to vector conversion or hand digitized into vector form. The vector data was then tagged with attribute information using ARC-INFO software. Transformation to geographic coordinates was performed using the projection graticules for each sheet. Digital information was edge matched between sheets to create large regional datasets. These were then subdivided into 5 x 5 degree tiles and converted from ARC/INFO to VPF. The data was then pre-mastered for CD-ROM. QC was performed by a separate group for each step in the production process.</procdesc>
<procdate>199112</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute</cntorg>
</cntorgp>
<cntpos>Applications Division</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>380 New York St.</address>
<city>Redlands</city>
<state>CA</state>
<postal>92373</postal>
<country>US</country>
</cntaddr>
<cntvoice>909-793-2853</cntvoice>
<cntfax>909-793-5953</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdate>199404</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Geonex</cntorg>
</cntorgp>
<cntpos></cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>8950 North 9th Ave.</address>
<city>St. Petersburg</city>
<state>FL</state>
<postal>33702</postal>
<country>US</country>
</cntaddr>
<cntvoice>(813)578-0100</cntvoice>
<cntfax>(813)577-6946</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Transferred digitally directly into the VPF files.</procdesc>
<procdate>199408</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Geonex</cntorg>
</cntorgp>
<cntpos></cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>8950 North 9th Ave.</address>
<city>St. Petersburg</city>
<state>FL</state>
<postal>33702</postal>
<country>US</country>
</cntaddr>
<cntvoice>813-578-0100</cntvoice>
<cntfax>813-577-6946</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Stable-based positives were produced from the original reproduction negatives (up to 35 per ONC sheet). These were digitized either through a scanning-raster to vector conversion or hand digitized into vector form. The vector data was then tagged with attribute information using ARC-INFO software. Transformation to geographic coordinates was performed using the projection graticules for each sheet. Digital information was edge matched between sheets to create large regional datasets. These were then subdivided into 5 x 5 degree tiles and converted from ARC/INFO to VPF. The data was then pre-mastered for CD-ROM. QC was performed by a separate group for each step in the production process.</procdesc>
<procdate>199112</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Environmental Systems Research Institute</cntorg>
</cntorgp>
<cntpos>Applications Division</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>380 New York St.</address>
<city>Redlands</city>
<state>CA</state>
<postal>92373</postal>
<country>US</country>
</cntaddr>
<cntvoice>909-793-2853</cntvoice>
<cntfax>909-793-5953</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Daily AVHRR images were averaged for two week time periods over the entire US growing season. These averaged images, their rates of change, elevation information, and other data were used to produce a single land classification image of the contental US. The VMap-0 data set extended this coverage over the Canadian land mass, however vegetation classification was further subdivided into nine vegetation types.</procdesc>
<procdate>199402</procdate>
<srcprod>EROS data</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>USGS Eros Data Center</cntorg>
</cntorgp>
<cntpos></cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address></address>
<city>Sioux Falls</city>
<state>SD</state>
<postal></postal>
<country>US</country>
</cntaddr>
<cntvoice></cntvoice>
<cntfax></cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>The Eros data (raster files) were converted to vector polygon, splined (remove stairstepping), thinned (all ploygons under 2km2 were deleted), and tied to existing DCW polygons (water bodies, built-up areas). The resulting file was tiled and converted to a VPF Vegetation coverage for use in the DCW. All processing was performed using ARC-INFO software.</procdesc>
<procdate>199412</procdate>
<srcprod>VMap-0 Vegetation Coverage</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Geonex</cntorg>
</cntorgp>
<cntpos></cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>8950 North 9th Ave.</address>
<city>St. Petersburg</city>
<state>FL</state>
<postal>33702</postal>
<country>US</country>
</cntaddr>
<cntvoice>813-578-0100</cntvoice>
<cntfax>813-577-6946</cntfax>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Data was translated from VPF format to ArcInfo Coverage format. The coverages were then loaded into a seamless ArcSDE layer.</procdesc>
<procdate>02152001</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>Geodesy Team, Harvard University</cntorg>
</cntorgp>
<cntemail>[email protected]</cntemail>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Complete chain</sdtstype>
</sdtsterm>
<sdtsterm>
<sdtstype>Label point</sdtstype>
</sdtsterm>
<sdtsterm>
<sdtstype>GT-polygon composed of chains</sdtstype>
</sdtsterm>
<sdtsterm>
<sdtstype>Point</sdtstype>
</sdtsterm>
<vpfterm>
<vpflevel>3</vpflevel>
<vpfinfo>
<vpftype>Node</vpftype>
</vpfinfo>
<vpfinfo>
<vpftype>Edge</vpftype>
</vpfinfo>
<vpfinfo>
<vpftype>Face</vpftype>
</vpfinfo>
</vpfterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<geograph>
<latres>0.000000</latres>
<longres>0.000000</longres>
<geogunit>Decimal degrees</geogunit>
</geograph>
<geodetic>
<horizdn>D_WGS_1984</horizdn>
<ellips>WGS_1984</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257224</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>Mean Sea Level</altdatum>
<altunits>1.0</altunits>
</altsys>
</vertdef>
</spref>
<eainfo>
<detailed>
<enttyp>
<enttypl>
lc.pat</enttypl>
</enttyp>
<attr>
<attrlabl>FID</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Shape</attrlabl>
<attrdef>Feature geometry.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Coordinates defining the features.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>AREA</attrlabl>
<attrdef>Area of feature in internal units squared.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>PERIMETER</attrlabl>
<attrdef>Perimeter of feature in internal units.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Positive real numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LC#</attrlabl>
<attrdef>Internal feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>LC-ID</attrlabl>
<attrdef>User-defined feature number.</attrdef>
<attrdefs>ESRI</attrdefs>
</attr>
<attr>
<attrlabl>LCAREA.AFT_ID</attrlabl>
</attr>
<attr>
<attrlabl>LCPYTYPE</attrlabl>
<attrdef>Land cover poygon type</attrdef>
<attrdefs>NIMA</attrdefs>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Rice Field</edomvd>
</edom>
<edom>
<edomv>2</edomv>
<edomvd>Cranberry bog</edomvd>
</edom>
<edom>
<edomv>3</edomv>
<edomvd>Cultivated area, garden</edomvd>
</edom>
<edom>
<edomv>4</edomv>
<edomvd>Peat cuttings</edomvd>
</edom>
<edom>
<edomv>5</edomv>
<edomvd>Salt pan</edomvd>
</edom>
<edom>
<edomv>6</edomv>
<edomvd>Fish pond or hatchery</edomvd>
</edom>
<edom>
<edomv>7</edomv>
<edomvd>Quarry, strip mine, mine dump, blasting area</edomvd>
</edom>
<edom>
<edomv>8</edomv>
<edomvd>Oil or gas</edomvd>
</edom>
<edom>
<edomv>10</edomv>
<edomvd>Lava flow</edomvd>
</edom>
<edom>
<edomv>11</edomv>
<edomvd>Distorted surface area</edomvd>
</edom>
<edom>
<edomv>12</edomv>
<edomvd>Unconsolidated material (sand or gravel, glacial moraine)</edomvd>
</edom>
<edom>
<edomv>13</edomv>
<edomvd>Natural landmark area</edomvd>
</edom>
<edom>
<edomv>14</edomv>
<edomvd>Inundated area</edomvd>
</edom>
<edom>
<edomv>15</edomv>
<edomvd>Undifferentiated wetlands</edomvd>
</edom>
<edom>
<edomv>99</edomv>
<edomvd>None</edomvd>
</edom>
</attrdomv>
</attr>
<attr>
<attrlabl>TILE_ID</attrlabl>
<attrdef>VPF Format tile ID</attrdef>
<attrdefs>NIMA</attrdefs>
</attr>
<attr>
<attrlabl>FAC_ID</attrlabl>
</attr>
</detailed>
<overview>
<eaover>The DCW used a product-specific attribute coding system that is composed of TYPE and STATUS designators for area, line, and point features; and LEVEL and SYMBOL designators for text features. The TYPE attribute specifies what the feature is, while the STATUS attribute specifies the current condition of the feature. Some features require both a TYPE and STATUS code to uniquely identify their characteristics. In order to uniquely identify each geographic attribute in the DCW, the TYPE and STATUS attribute code names are preceded by the two letter coverage abbreviation and a two letter abbreviation for the type of graphic primitive present. The DCW Type/Status codes were mapped into the FACC coding scheme. A full description of FACC may be found in Digital Geographic Information Exchange Standard Edition 1.2, January 1994.</eaover>
<eadetcit>Entities (features) and Attributes for DCW are fully described in: Department of Defense, 1992, Military Specification Digital Chart of the World (MIL-D-89009): Philadelphia, Department of Defense, Defense Printing Service Detachment Office.</eadetcit>
</overview>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>NIMA</cntorg>
</cntorgp>
<cntpos>ATTN: CC, MS D-16</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>6001 MacArthur Blvd.</address>
<city>Bethesda</city>
<state>MD</state>
<postal>20816-5001</postal>
<country>US</country>
</cntaddr>
<cntvoice>301-227-2495</cntvoice>
<cntfax>301-227-2498</cntfax>
</cntinfo>
</distrib>
<distliab>None</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>VPF</formname>
<formverd>19930930</formverd>
<formspec>Military Standard Vector Product Format (MIL-STD-2407). The current version of this document is dated 28 June 1996. Edition 3 of VMap-0 conforms to a previous version of the VPF Standard as noted. Future versions of VMap-0 will conform to the current version of VPF Standard.</formspec>
<transize>0.172</transize>
</digtinfo>
<digtopt>
<offoptn>
<offmedia>CD-ROM</offmedia>
<recfmt>ISO 9660</recfmt>
</offoptn>
</digtopt>
</digform>
<fees>Not Applicable</fees>
</stdorder>
</distinfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>USGS Map Sales</cntorg>
</cntorgp>
<cntaddr>
<addrtype>mailing address</addrtype>
<address>Box 25286</address>
<city>Denver</city>
<state>CO</state>
<postal>80225</postal>
<country>US</country>
</cntaddr>
<cntvoice>303-236-7477</cntvoice>
<cntfax>303-236-1972</cntfax>
</cntinfo>
</distrib>
<distliab>None</distliab>
<stdorder>
<digform>
<digtinfo>
<transize>0.172</transize>
</digtinfo>
</digform>
<fees>$82.50 per four disk set</fees>
<ordering>For General Public: Payment (check, money order, purchase order, or Government account) must accompany order.
Make all drafts payable to Dept. of the Interior- US Geological Survey.
To provide a general idea of content, a sample data set is available from the TMPO Home Page at:</ordering>
</stdorder>
</distinfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Geodesy Team, Harvard University</cntorg>
<cntper>Geodesy Team</cntper>
</cntorgp>
<cntemail>[email protected]</cntemail>
</cntinfo>
</distrib>
<resdesc>Geodesy layer</resdesc>
<distliab>None</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>SHP</formname>
<transize>0.172</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>geodesy.harvard.edu</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>none</fees>
</stdorder>
<availabl>
<timeinfo>
<sngdate>
<caldate>1992</caldate>
</sngdate>
</timeinfo>
</availabl>
</distinfo>
<metainfo>
<metd>20010226</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Geodesy Team</cntorg>
<cntper>REQUIRED: The person responsible for the metadata information.</cntper>
</cntorgp>
<cntvoice>REQUIRED: The telephone number by which individuals can speak to the organization or individual.</cntvoice>
<cntemail>[email protected]</cntemail>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>

Have you tired the directory and bfile methods? Here is the example for that in the Oracle XML Developer's Guide:
CREATE DIRECTORY xmldir AS 'path_to_folder_containing_XML_file';
Example 3-3 Inserting XML Content into an XMLType Table
INSERT INTO mytable2 VALUES (XMLType(bfilename('XMLDIR', 'purchaseOrder.xml'),
nls_charset_id('AL32UTF8')));
1 row created.
The value passed to nls_charset_id() indicates that the encoding for the file to be read is UTF-8.
ben

Inserting Namespace in XML document using 4.6C(no XLST)

Hi all,
I'm writing a program in which I need to convert data into XML, all this works fine using CL_XML_DOCUMENT.Create_With_Data. I was also able to insert the encoding as asked by the EAI tool who will interpret the XML file I have generated. Now they have returned to me, saying they also need the following tag:
<FILE>
 <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
 <asx:values> <CONTROL>
 </CONTROL>
 <DNB>
 </DNB>
 </asx:values>
 </asx:abap></FILE>
I have read about this on SDN and found several posts in which people using 4.7(CALL TRANSFORMATION) are asking to get rid of that tag, but not how to insert it without the use of XSLT.
I have already tried the following:
call method l_dom->set_attribute(
name = 'xmlns:asx'
value = 'http://www.sap.com/abapxml version=1.0' ).
This however is not giving the expected result, if someone can help me with this, I would be very gratefull.
In the meantime I continue trying.
Thanks in advance

hi, before you set the attribute, you need to create a Namespace element preliminary.
Try the following code:
ELEMENT = DOCUMENT->CREATE_SIMPLE_ELEMENT_NS(
NAME = 'abap'
PREFIX = 'asx'
PARENT = DOCUMENT ).
ATTRIBUTE = DOCUMENT->create_namespace_decl(
NAME = 'XMLNS'
PREFIX = 'asx'
URI = 'http://www.sap.com/abapxml').
ELEMENT->SET_ATTRIBUTE_NODE_NS(
NEW_ATTR = ATTRIBUTE).
Hope my reply will be useful.
thanks

Please help to read the XML document with XMLTable

Hi Gurus,
I am not very familiar with XML parsing. It seems to me it should be very easy to get the data. For some reason, I am having a problem to get the data.
SELECT *
FROM util.hlsr_online_entries e,
XMLTABLE(
xmlnamespaces(
 'http://tempuri.org/' as "dt",
 'urn:schemas-microsoft-com:xml-diffgram-v1' as "dg"),
'/DataTable/dg:diffgram/DocumentElement/JrShowCustomerHeifers'
PASSING XMLTYPE(e.entry_data)
COLUMNS
SeqNo FOR ORDINALITY,
DocumentID NUMBER PATH 'DocumentID',
ClubName VARCHAR2(100) PATH 'ClubName') as test
WHERE e.ref_id = 33422
The above query does not bring any data for me. My hunts is the problem with DocumentElement tab. I have been trying a different variation to handle.
Please help me out to tune the query
I have the following XML document from the DotNet developer
<?xml version="1.0" encoding="utf-8"?>
<DataTable xmlns="http://tempuri.org/">
<xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
 <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:MainDataTable="JrShowCustomerHeifers" msdata:UseCurrentLocale="true">
 <xs:complexType>
 <xs:choice minOccurs="0" maxOccurs="unbounded">
 <xs:element name="JrShowCustomerHeifers">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="DocumentID" type="xs:int" minOccurs="0" />
 <xs:element name="ClubName" type="xs:string" minOccurs="0" />
 <xs:element name="LastName" type="xs:string" minOccurs="0" />
 <xs:element name="FirstName" type="xs:string" minOccurs="0" />
 <xs:element name="PreferredName" type="xs:string" minOccurs="0" />
 <xs:element name="Email" type="xs:string" minOccurs="0" />
 <xs:element name="Exhibitor" type="xs:string" minOccurs="0" />
 <xs:element name="AnimalName" type="xs:string" minOccurs="0" />
 <xs:element name="RegistryNo" type="xs:string" minOccurs="0" />
 <xs:element name="DateofBirth" type="xs:string" minOccurs="0" />
 <xs:element name="NameofSire" type="xs:string" minOccurs="0" />
 <xs:element name="SireRegistryNo" type="xs:string" minOccurs="0" />
 <xs:element name="NameofDam" type="xs:string" minOccurs="0" />
 <xs:element name="DamRegistryNo" type="xs:string" minOccurs="0" />
 <xs:element name="Tattoo" type="xs:string" minOccurs="0" />
 <xs:element name="SecondaryTattoo" type="xs:string" minOccurs="0" />
 <xs:element name="UniversalIDNumber" type="xs:string" minOccurs="0" />
 <xs:element name="Tattoo_Location" type="xs:string" minOccurs="0" />
 <xs:element name="Secondary_Tattoo_Location" type="xs:string" minOccurs="0" />
 <xs:element name="OracleBreedID" type="xs:int" minOccurs="0" />
 <xs:element name="JrValidationBreedName" type="xs:string" minOccurs="0" />
 <xs:element name="ValidationDate" type="xs:dateTime" minOccurs="0" />
 <xs:element name="ValidatedBy" type="xs:string" minOccurs="0" />
 <xs:element name="ValidationComment" type="xs:string" minOccurs="0" />
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:choice>
 </xs:complexType>
 </xs:element>
</xs:schema>
<diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
 <DocumentElement xmlns="">
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers1" msdata:rowOrder="0">
 <DocumentID>18442</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>113</AnimalName>
 <RegistryNo>C1026447</RegistryNo>
 <DateofBirth>01/14/2013</DateofBirth>
 <NameofSire>808 GAME DAY 808 LH</NameofSire>
 <SireRegistryNo>C961101</SireRegistryNo>
 <NameofDam>SADDIE 7/7 LE</NameofDam>
 <DamRegistryNo>C941067</DamRegistryNo>
 <Tattoo>113</Tattoo>
 <SecondaryTattoo />
 <UniversalIDNumber>1194F020</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location />
 <OracleBreedID>6383</OracleBreedID>
 <JrValidationBreedName>Beefmaster</JrValidationBreedName>
 <ValidationDate>2014-11-25T08:39:00-06:00</ValidationDate>
 <ValidatedBy>laineyb</ValidatedBy>
 <ValidationComment />
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers2" msdata:rowOrder="1">
 <DocumentID>18473</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>KPH PURPLE CORALEE 349</AnimalName>
 <RegistryNo>P43461953</RegistryNo>
 <DateofBirth>11/04/2013</DateofBirth>
 <NameofSire>PURPLE MOXY 22X ET</NameofSire>
 <SireRegistryNo>P43126458</SireRegistryNo>
 <NameofDam>TCC CORKY 6603</NameofDam>
 <DamRegistryNo>P42457119</DamRegistryNo>
 <Tattoo>349</Tattoo>
 <SecondaryTattoo>KPH</SecondaryTattoo>
 <UniversalIDNumber>1194F021</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>2014-12-01T11:55:00-06:00</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment />
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers3" msdata:rowOrder="2">
 <DocumentID>18474</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>LANGFORDS SWEET N SOUR 4107</AnimalName>
 <RegistryNo>43504761</RegistryNo>
 <DateofBirth>03/02/2014</DateofBirth>
 <NameofSire>LH TNT 1017</NameofSire>
 <SireRegistryNo>43199794</SireRegistryNo>
 <NameofDam>LANGFORDS LADY 2206 ET</NameofDam>
 <DamRegistryNo>43315143</DamRegistryNo>
 <Tattoo>4107</Tattoo>
 <SecondaryTattoo />
 <UniversalIDNumber>1194F018</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location />
 <OracleBreedID>6398</OracleBreedID>
 <JrValidationBreedName>Hereford</JrValidationBreedName>
 <ValidationDate>2014-11-24T14:26:00-06:00</ValidationDate>
 <ValidatedBy>Validator</ValidatedBy>
 <ValidationComment />
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers4" msdata:rowOrder="3">
 <DocumentID>18475</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>PURPLE CCC LYDIA 19A</AnimalName>
 <RegistryNo>P43406978</RegistryNo>
 <DateofBirth>02/05/2013</DateofBirth>
 <NameofSire>PURPLE MB WOMANIZER 14UET</NameofSire>
 <SireRegistryNo>P42945146</SireRegistryNo>
 <NameofDam>PURPLE CMCC NASTIA 9U</NameofDam>
 <DamRegistryNo>P42927201</DamRegistryNo>
 <Tattoo>19A</Tattoo>
 <SecondaryTattoo />
 <UniversalIDNumber>1194F017</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location />
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>2014-12-01T11:55:00-06:00</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment />
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers5" msdata:rowOrder="4">
 <DocumentID>18477</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>PURPLE SGW EDEN 12B</AnimalName>
 <RegistryNo>P43521932</RegistryNo>
 <DateofBirth>04/02/2014</DateofBirth>
 <NameofSire>RST TIME'S A WASTIN' 0124</NameofSire>
 <SireRegistryNo>43123163</SireRegistryNo>
 <NameofDam>PURPLE SM WONDER WOMAN 160Y</NameofDam>
 <DamRegistryNo>P43235169</DamRegistryNo>
 <Tattoo>12B</Tattoo>
 <SecondaryTattoo>12B</SecondaryTattoo>
 <UniversalIDNumber>1194F015</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>2014-12-01T11:56:00-06:00</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment />
 </JrShowCustomerHeifers>
 </DocumentElement>
</diffgr:diffgram>
</DataTable>

Hi odie_63,
Good evening. I am not sure what you are suggesting. Please provide me the example how to solve the problem. I am very new to XML parsing.
In the meantime, I am having another problem to get the data because .net developer changes the webservice format. To me it is supposed to work fine. May be my eyes are getting blurred so, I can't see where I am wrong.
Thanks in advance. Please help me out.
SELECT exh.docid,exh.clubname,exh.lname,exh.fname,exh.exhibitor,exh.animalname
FROM util.hlsr_online_entries e,
XMLTABLE(
xmlnamespaces(
 'http://webservices.hlsr.net/JrShowOracleService/' as "dt",
 'urn:schemas-microsoft-com:xml-diffgram-v1' as "dg"),
'/dt:GetJrShowCustomerHeifersResponse/GetJrShowCustomerHeifersResult/dg:diffgram/DocumentElement/JrShowCustomerHeifers'
PASSING XMLTYPE(e.entry_data)
COLUMNS
SeqNo FOR ORDINALITY,
DocID NUMBER PATH 'DocumentID',
ClubName VARCHAR2(100) PATH 'ClubName',
LName VARCHAR2(100) PATH 'LastName',
FName VARCHAR2(100) PATH 'FirstName',
Email VARCHAR2(100) PATH 'Email',
Exhibitor VARCHAR2(100) PATH 'Exhibitor',
AnimalName VARCHAR2(100) PATH 'AnimalName',
RegNo VARCHAR2(100) PATH 'RegistryNo',
DOB VARCHAR2(100) PATH 'DateofBirth',
SireName VARCHAR2(100) PATH 'NameofSire',
SireRegNo VARCHAR2(100) PATH 'SireRegistryNo',
Dam VARCHAR2(100) PATH 'NameofDam',
DamRegNo VARCHAR2(100) PATH 'DamRegistryNo',
Tattoo VARCHAR2(100) PATH 'Tattoo',
SecTattoo VARCHAR2(100) PATH 'SecondaryTattoo',
UnivIDNum VARCHAR2(100) PATH 'UniversalIDNumber',
TattooLoc VARCHAR2(100) PATH 'Tattoo_Location',
OraBreedID NUMBER PATH 'OracleBreedID',
Breed VARCHAR2(100) PATH 'JrValidationBreedName',
ValDate VARCHAR2(100) PATH 'ValidationDate'
) as exh
WHERE e.ref_id = 33432
<GetJrShowCustomerHeifersResponse xmlns="http://webservices.hlsr.net/JrShowOracleService/">
<GetJrShowCustomerHeifersResult>
 <xs:schema id="NewDataSet" xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
 <xs:element name="NewDataSet" msdata:IsDataSet="true" msdata:MainDataTable="JrShowCustomerHeifers" msdata:UseCurrentLocale="true">
 <xs:complexType>
 <xs:choice minOccurs="0" maxOccurs="unbounded">
 <xs:element name="JrShowCustomerHeifers">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="DocumentID" type="xs:int" minOccurs="0"/>
 <xs:element name="ClubName" type="xs:string" minOccurs="0"/>
 <xs:element name="LastName" type="xs:string" minOccurs="0"/>
 <xs:element name="FirstName" type="xs:string" minOccurs="0"/>
 <xs:element name="PreferredName" type="xs:string" minOccurs="0"/>
 <xs:element name="Email" type="xs:string" minOccurs="0"/>
 <xs:element name="Exhibitor" type="xs:string" minOccurs="0"/>
 <xs:element name="AnimalName" type="xs:string" minOccurs="0"/>
 <xs:element name="RegistryNo" type="xs:string" minOccurs="0"/>
 <xs:element name="DateofBirth" type="xs:string" minOccurs="0"/>
 <xs:element name="NameofSire" type="xs:string" minOccurs="0"/>
 <xs:element name="SireRegistryNo" type="xs:string" minOccurs="0"/>
 <xs:element name="NameofDam" type="xs:string" minOccurs="0"/>
 <xs:element name="DamRegistryNo" type="xs:string" minOccurs="0"/>
 <xs:element name="Tattoo" type="xs:string" minOccurs="0"/>
 <xs:element name="SecondaryTattoo" type="xs:string" minOccurs="0"/>
 <xs:element name="UniversalIDNumber" type="xs:string" minOccurs="0"/>
 <xs:element name="Tattoo_Location" type="xs:string" minOccurs="0"/>
 <xs:element name="Secondary_Tattoo_Location" type="xs:string" minOccurs="0"/>
 <xs:element name="OracleBreedID" type="xs:int" minOccurs="0"/>
 <xs:element name="JrValidationBreedName" type="xs:string" minOccurs="0"/>
 <xs:element name="ValidationDate" type="xs:string" minOccurs="0"/>
 <xs:element name="ValidatedBy" type="xs:string" minOccurs="0"/>
 <xs:element name="ValidationComment" type="xs:string" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:choice>
 </xs:complexType>
 </xs:element>
 </xs:schema>
 <diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
 <DocumentElement xmlns="">
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers1" msdata:rowOrder="0">
 <DocumentID>18442</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>113</AnimalName>
 <RegistryNo>C1026447</RegistryNo>
 <DateofBirth>01/14/2013</DateofBirth>
 <NameofSire>808 GAME DAY 808 LH</NameofSire>
 <SireRegistryNo>C961101</SireRegistryNo>
 <NameofDam>SADDIE 7/7 LE</NameofDam>
 <DamRegistryNo>C941067</DamRegistryNo>
 <Tattoo>113</Tattoo>
 <SecondaryTattoo/>
 <UniversalIDNumber>1194F020</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location/>
 <OracleBreedID>6383</OracleBreedID>
 <JrValidationBreedName>Beefmaster</JrValidationBreedName>
 <ValidationDate>11/25/2014</ValidationDate>
 <ValidatedBy>laineyb</ValidatedBy>
 <ValidationComment/>
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers2" msdata:rowOrder="1">
 <DocumentID>18473</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>KPH PURPLE CORALEE 349</AnimalName>
 <RegistryNo>P43461953</RegistryNo>
 <DateofBirth>11/04/2013</DateofBirth>
 <NameofSire>PURPLE MOXY 22X ET</NameofSire>
 <SireRegistryNo>P43126458</SireRegistryNo>
 <NameofDam>TCC CORKY 6603</NameofDam>
 <DamRegistryNo>P42457119</DamRegistryNo>
 <Tattoo>349</Tattoo>
 <SecondaryTattoo>KPH</SecondaryTattoo>
 <UniversalIDNumber>1194F021</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>12/01/2014</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment/>
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers3" msdata:rowOrder="2">
 <DocumentID>18474</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>LANGFORDS SWEET N SOUR 4107</AnimalName>
 <RegistryNo>43504761</RegistryNo>
 <DateofBirth>03/02/2014</DateofBirth>
 <NameofSire>LH TNT 1017</NameofSire>
 <SireRegistryNo>43199794</SireRegistryNo>
 <NameofDam>LANGFORDS LADY 2206 ET</NameofDam>
 <DamRegistryNo>43315143</DamRegistryNo>
 <Tattoo>4107</Tattoo>
 <SecondaryTattoo/>
 <UniversalIDNumber>1194F018</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location/>
 <OracleBreedID>6398</OracleBreedID>
 <JrValidationBreedName>Hereford</JrValidationBreedName>
 <ValidationDate>11/24/2014</ValidationDate>
 <ValidatedBy>Validator</ValidatedBy>
 <ValidationComment/>
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers4" msdata:rowOrder="3">
 <DocumentID>18475</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>PURPLE CCC LYDIA 19A</AnimalName>
 <RegistryNo>P43406978</RegistryNo>
 <DateofBirth>02/05/2013</DateofBirth>
 <NameofSire>PURPLE MB WOMANIZER 14UET</NameofSire>
 <SireRegistryNo>P42945146</SireRegistryNo>
 <NameofDam>PURPLE CMCC NASTIA 9U</NameofDam>
 <DamRegistryNo>P42927201</DamRegistryNo>
 <Tattoo>19A</Tattoo>
 <SecondaryTattoo/>
 <UniversalIDNumber>1194F017</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location/>
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>12/01/2014</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment/>
 </JrShowCustomerHeifers>
 <JrShowCustomerHeifers diffgr:id="JrShowCustomerHeifers5" msdata:rowOrder="4">
 <DocumentID>18477</DocumentID>
 <ClubName>Perrin FFA</ClubName>
 <LastName>Hamman</LastName>
 <FirstName>Kaily</FirstName>
 <Email>[email protected]</Email>
 <Exhibitor>Hamman, Kaily</Exhibitor>
 <AnimalName>PURPLE SGW EDEN 12B</AnimalName>
 <RegistryNo>P43521932</RegistryNo>
 <DateofBirth>04/02/2014</DateofBirth>
 <NameofSire>RST TIME'S A WASTIN' 0124</NameofSire>
 <SireRegistryNo>43123163</SireRegistryNo>
 <NameofDam>PURPLE SM WONDER WOMAN 160Y</NameofDam>
 <DamRegistryNo>P43235169</DamRegistryNo>
 <Tattoo>12B</Tattoo>
 <SecondaryTattoo>12B</SecondaryTattoo>
 <UniversalIDNumber>1194F015</UniversalIDNumber>
 <Tattoo_Location>TATTOO - Left Ear</Tattoo_Location>
 <Secondary_Tattoo_Location>TATTOO - Right Ear</Secondary_Tattoo_Location>
 <OracleBreedID>6389</OracleBreedID>
 <JrValidationBreedName>Polled Hereford</JrValidationBreedName>
 <ValidationDate>12/01/2014</ValidationDate>
 <ValidatedBy>Hannah</ValidatedBy>
 <ValidationComment/>
 </JrShowCustomerHeifers>
 </DocumentElement>
 </diffgr:diffgram>
</GetJrShowCustomerHeifersResult>
</GetJrShowCustomerHeifersResponse>
Thanks again.

Generic Populating the XML document using Java Class Generator and Reflection

I am looking for a generic source code in order to convert the data parsed from any tabular text form ( tab delimited for example that maps certain XML Schema created form Database Schema for Oracle.
I know it is possible to generate XML DTD or XSD from Oracle database table schema by XSU utility from XDK. And also it is possible to create Java source files from an XML DTD or XSD by using XML Clas Generator.
I believe there must be some generic code that parses tabular text data and converts them to XML format using above mentioned generated Java source files and may be Java reflection mechanism.
If anyone has any tool or knows any free ware that helps me, I would like to know about it, and I would really appreciate it.

1. Read the XML file into a DMO object, walk the DOM to find the list, insert your new entry as a child, write the DOM back to a file.
2. If the XML is not in a file, but in a string, then you can do the same with string input and output.

How to keep the XML document in javadocs

Hi,
I have a class with javadocs containing <?xml....> ... </xml> document in it. I have tried to use <pre> to keep the structure. When javadoc is run it strips all the XML tags. Is it possible to keep these lines as is and not being interpreted?
Thanks,
-Ashish

Hello,
try to use <pre> and </pre> html tag around your XML document, and in your XML document change the < and > by their html special codes
Merc?.

Insertion in the xml document

Similar Messages

Maybe you are looking for