Adding XML fragments to a document in a XMLType table

Hi,
Is there a direct way to insert an XML fragment into a
document held in a XMLtype, or does this have to be done
via the updatexml function?
thanks
Pete

Thank you Jeffrey. I converted the file to PDF and it worked! Very happy.

Similar Messages

Adding xml fragment to SOAP body (SAAJ)

Hi all,
we are using SOAP (or better SAAJ) in a modular design as packaging/enveloping format for arbitrary payloads which are generated by different modules.
How is it possible to add a xml fragment (as InputStream or DOM Node) to a SOAP Body ?
Nick
[email protected]

Hi Vicky,
I guess, we have a little misunderstanding here. The core SOAP specification defines the structure of the envelope, the "SOAP with attachments" specification extends that by defining how to add binary attachments. This is accomplished by using MIME. Every attachment is another MIMEPart, but the SOAP Envelope always has to be present as first MIMEPart. Now I don't want to add any attachments, I only want to construct a SOAP Envelope that contains arbitrary xml docs (fragments) in the body.
Look at the example below, the tags with namespace "S" belong to the SOAP specification and are built by our SOAP layer, the tags with namespace "m" belong to some other namespace and are generated by a totally different component.
My question was how I could add (within SAAJ) the xml fragment starting with "m:PurchaseOrder" to the envelope without having to add element by element.
<S:Envelope>
     <S:Header>
          ...optional header tags
     </S:Header>
     <S:Body>
                <!---from here it is a different namespace, SOAP doesn't know about PurchaseOrders>
          <m:PurchaseOrder>
               <m:position>
                    <m:article>0815</m:article>
                    <m:description>mainboard</m:description>
                    <m:price>50</m:price>
               </m:position>
               <m:position>
                    <m:article>0816</m:article>
                    <m:description>cpu</m:description>
                    <m:price>100</m:price>
               </m:position>
          </PurchaseOrder>
                <!---from here, it is SOAP again>
     </S:Body>
</S:Envelope>

How to marshal XML fragments with JAXB

Hello,
I have Object unashamed from XML. I would like to insert part of this object in another XML document. I�m using Cocoon Transformer for this. In startElement then I detect element which I would like replace I would like to write something like this:
Marshaller m = jc.createMarshaller();
m.marshal(myElem, contentHandler);
However this method try to marshal it as whole document with: <?xml version="1.0" encoding="UTF-8" ?> This probably case problems for next Transformer.
I have this problem in Cocoon and with SAX, but there should be some general solution to marshal JAXB objects as XML fragments, not whole documents. However I can�t found it.
Thanks for any help
Arek Stryjski

In JAXB mailing list I got this answer:
It currently doesn't have any explicit support for fragment marshalling,
but like you said, you can easily write an XMLFilter that blocks
start|endDocument. In your case, you just need to:
Marshaller m = jc.createMarshaller();
m.marshal(myElem, new FragmentFilter(contentHandler));
where FragmentFilter is:
class FragmentFilter extends XMLFilterImpl {
FragmentFilter( ContentHandler handler ) {
setContentHandler(handler);
public void startDocument() {}
public void endDocument() {}
Perhaps this could be another example.
regards,
Kohsuke KAWAGUCHI

How to include a URL in an XML fragment

Hello , my general question is how can I include a URL as a literal in an XML fragment , I tried this(please look at the bold part) but it would'nt work , I am getting a compile error because supposedly "<" is a special character in XML so how do I escape it or indeed how do I represent my URL? Your help is highly appreciated
<EndpointReference xmlns="http://schemas.xmlsoap.org/ws/2003/03/addressing [b]<https://webmail.bearingpoint.com/exchweb/bin/redir.asp?URL=http://schemas.xmlsoap.org/ws/2003/03/addressing> ">
<Address>https://secure-ausomxbxa.crmondemand.com/Services/Integration;j <https://webmail.bearingpoint.com/exchweb/bin/redir.asp?URL=https://secure-ausomxbxa.crmondemand.com/Services/Integration;j> sessionid=</Address>
<ServiceName xmlns:ns1="urn:crmondemand/ws/opportunity/10/2004">ns1:Opportunity</ServiceName>
</EndpointReference>

I don't know why you would want to surround your URL with < and > characters.
But the XML rule for escaping those characters in text nodes and attributes is that you escape < as < and > as >. The fact that URLs are involved in your case doesn't make any difference to that rule.
And normally if you're using XML software (e.g. Transformer, or Xerces's serializer) to write the document, it will take care of that detail for you. On the other hand if you're using ordinary java.io classes to write the document, you have to apply that rule yourself.

How To Store XML Fragments Using Functions Such As XMLElement

Hi
Not sure what I am missing. I wish to store XML fragments in variables so can pass around and concatenate with other fragments to make final XML document. Even before attempting to concatenate XML fragments, I am struggling to store any XML fragment in a variable. I am trying to use simple functions such as XMLElement to generate XML so can store in variable. I have seen many examples of XMLElement in SQL select statement. Can XMLElement be used in plsql? XMLElement says it returns value of type XMLType. Functions such as XMLElement make generating XML easier than creating all tags manually.
Below is simple example that demonstrates what I would like to do. I would like to be able to pass the XML fragment as either XMLType or clob. I receive error saying PLS-00201: identifier 'XMLELEMENT' must be declared
declare
vTheData XMLType;
vTheDataClob clob;
begin
vTheData:= XMLelement("empno",'1234567');
vTheDataClob:= xmlelement("empno",'1234567').getclobval();
end;
Where as I can use below, but surely don't have to use select into from dual method. I just expect can use XMLElement function in plsql same as sql, such as most other functions eg length, rtrim etc.
declare
vTheData XMLType;
vTheDataClob clob;
begin
select xmlelement("empno",'1234567')
into vTheData
from dual;
select xmlelement("empno",'1234567').getclobval()
into vTheDataClob
from dual;
end;
Hope this makes sense.
Thanks

Having said that, is there a more elegant way to achieve below. That is populate two XML fragments and concatenate together.
Sure, why not just only one statement?
select XMLConcat(
XMLElement( ... )
, XMLElement( ... )
into vTheResult
from dual;
As a second question, is it better to build and pass XML fragments as XMLType or clob?
I would say stay with XMLType but it depends on your requirement.
I generally avoid passing around pieces of data, SQL/XML functions are powerful in the way they can be used with set operations, so using them in a piecewise approach kinda negates what they're for.

Migrating V9 to V10: Update XML Fragment CLOB does not work anymore

I have an XML Schema that contains an element, named Operazione, mapped to a CLOB.
I just migrate to Oracle 10.1.0.2.0 from version 9.2.0.2.0 and the code I developed does not work anymore.
To get a CLOB on v 9.2.0.2.0 I issued the following statement:
select extractValue(value(p),'/operazione.log/Operazione') from XMT_OPERAZIONE_LOG p
where existsNode(value(p),'/operazione.log/Journal[NumeroElettronico=1234567890]') = 1
To make it working on V10 I have to change it as follow:
select extract(value(p),'/operazione.log/Operazione').getClobVal() from XMT_OPERAZIONE_LOG p
where existsNode(value(p),'/operazione.log/Journal[NumeroElettronico=1234567890]') = 1
So using extract intead of extractValue and adding getClobVal() I was able to read the CLOB.
The problem that I was not able to solve is related to CLOB update. In V9 just adding the âfor updateâ clause I was able to change the CLOB value on DB.
In V10 if I run the V9 statement I get the error:
ORA-03113: end-of-file on communication channel
If I use the statement modified for V10, adding the âfor updateâ clause, I get the CLOB and I can change the CLOB value but nothing goes on the DB. Probably I am working on a copy of the DB CLOB.
If I remove the getClobVal() I get an OPAQUE type that I can use on a XMLType but, still, nothing is stored on DB.
Any suggestion ?
I tried with both OCI and Thin Client

Can anybody help me ?
Is it better to use different strategies ( eg. Stored Procedure, DBMS_XMLSTORE etc, etc. ) ?
Any experience updatating XML Fragment CLOB on Oracle V10 ?

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;

How to store XML fragments in a XMLTYPE column

Hi all,
maybe just another newbie question.
I've imported a lot of xml documents into an Oracle table with a xmltype column (stored as CLOB). Now I try to select a specific part of these documents and store thsi xml fragment in another table, also in a xmltype column.
Unfortunately this doesn't work, I get ORA-19010: Cannot insert XML fragments.
What can I do to store part of a xml document?
Best regards
Matthias

Is there a way to transform the xml fragments into valid xml documents?

Using XMLAgg with non-wellformed XML fragments

Hi,
with XMLAgg one can create a non-wellformed XML-Fragement ( i.e. with multiple root elements ) like
<foo>bar1</foo>
<foo>bar2</foo>
where each foo element comes from a table row ( e.g. from a single-column table with the rows 'bar1' and 'bar2' ).
However, I wasn't able to get a similar result when creating multiple elements per row. I defined a function that returns a non-wellformed fragment like
<foo>bar1</foo>
<oof>bar1</oof>
per row, but I couldn't aggregate these fragments using XMLAgg. The result should look like ( 2 elements per row )
<foo>bar1</foo>
<oof>bar1</oof>
<foo>bar2</foo>
<oof>bar2</oof>
Instead, i got an "LPX-00245: extra data after end of document" error ( whole error see below ).
I wonder why it is possible to create non-wellformed fragments with XMLAgg, but why there seems to be impossible to aggregate them.
Regards,
Pat
The whole error message ( sorry, the DBMS is configured for german language ):
ORA-29400: Data Cartridge-Fehler
ORA-31011: XML-Parsing nicht erfolgreich
ORA-19202: Fehler bei XML-Verarbeitung
LPX-00245: extra data after end of document
Error at line 1
aufgetreten
ORA-06512: in "TEST.DOC", Zeile 31
29400. 00000 - "data cartridge error\n%s"
*Cause:    An error has occurred in a data cartridge external procedure.
This message will be followed by a second message giving
more details about the data cartridge error.
*Action:   See the data cartridge documentation
for an explanation of the second error message.

Even in 9i I can aggregate without root element:
SQL> set timing off
SQL> select * from v$version where rownum = 1
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
1 row selected.
SQL> with t as (
select 1 id, xmltype( '<foo>bar1</foo>') xml from dual union all
select 1, xmltype( '<foo>bar1</foo>') from dual union all
select 2, xmltype( '<foo>bar1</foo>') from dual union all
select 2, xmltype( '<foo>bar1</foo>') from dual
select xmlagg(xml) xml from (
        select id, xmlagg(xml) xml from t group by id)
XML
<foo>bar1</foo>
<foo>bar1</foo>
<foo>bar1</foo>
<foo>bar1</foo>
1 row selected.

Generating XML fragment

Hopefully a quick one that I'm just missing.
I have a child table:
create table files (docid number(9), filename varchar2(200), filetype varchar2(30));
insert into files values (1, '1.pdf', 'primary');
insert into files values (2, '2.pdf', 'primary');
insert into files values (2, '3.pdf', 'secondary');
insert into files values (2, '4.pdf', 'tertiary');
insert into files values (2, '5.pdf', 'pending');
insert into files values (3, '6.pdf', 'secondary');
insert into files values (3, '7.pdf', 'secondary');What I need is an XML fragment to add to the parent document XML to indicate whether a document has a child filetype of some (but not all) of the permitted types.
The rules are:
if a 'primary' exists, create an element <orig>Y</orig>, otherwise create an element <orig>N</orig>
if a 'secondary' exists, create an element <alt>Y</alt>, otherwise create an element <alt>N</alt>
if a 'tertiary' exists, create an element <fin>Y</fin>, otherwise create an element <fin>N</fin>
if a 'pending' exists, do nothing
the result would be something similar to the following for a given docid:
docid 1 : <orig>Y</orig><alt>N</alt><fin>N</fin>
docid 2 : <orig>Y</orig><alt>Y</alt><fin>Y</fin>
docid 3 : <orig>N</orig><alt>Y</alt><fin>N</fin>I've got a brute force solution in hand, but I'm pretty sure there's a more elegant way.

Hi,
Here's one way, if you want to create one fragment at a time for a given DOCID :
SQL> SELECT xmlagg(
2           case ftype
3             when 'primary' then xmlelement("orig", ftype_exists)
4             when 'secondary' then xmlelement("alt", ftype_exists)
5             when 'tertiary' then xmlelement("fin", ftype_exists)
6           end
7         ) as result
8 FROM (
9    SELECT t.column_value as ftype
10         , case when count(f.filetype) != 0 then 'Y' else 'N' end as ftype_exists
11    FROM files f
12         RIGHT OUTER JOIN
13           TABLE(
14             sys.odcivarchar2list( 'primary'
15                                 , 'secondary'
16                                 , 'tertiary' )
17           ) t
18             ON t.column_value = f.filetype
19             AND f.docid = 1
20    GROUP BY t.column_value
21 );
RESULT
<orig>Y</orig><alt>N</alt><fin>N</fin>
For multiple DOCID in the same query, a slight modification using a partitioned outer join :
SQL> SELECT docid
2       , xmlagg(
3           case ftype
4             when 'primary' then xmlelement("orig", ftype_exists)
5             when 'secondary' then xmlelement("alt", ftype_exists)
6             when 'tertiary' then xmlelement("fin", ftype_exists)
7           end
8         ) as result
9 FROM (
10    SELECT f.docid
11         , t.column_value as ftype
12         , case when count(f.filetype) != 0 then 'Y' else 'N' end as ftype_exists
13    FROM files f
14         PARTITION BY (f.docid)
15         RIGHT OUTER JOIN
16           TABLE(
17             sys.odcivarchar2list( 'primary'
18                                 , 'secondary'
19                                 , 'tertiary' )
20           ) t
21             ON t.column_value = f.filetype
22    GROUP BY f.docid, t.column_value
23 )
24 GROUP BY docid
25 ;
     DOCID RESULT
         1 <orig>Y</orig><fin>N</fin><alt>N</alt>
         2 <orig>Y</orig><fin>Y</fin><alt>Y</alt>
         3 <orig>N</orig><fin>N</fin><alt>Y</alt>

Wrapping xml-fragment into AnyDocument looses runtime type information

I would like to store a fragment of xml in a database. However, to stay XML compatible,
I don't want to have <xml-fragment> tags. To avoid this, I attempt to "wrap"
the xml-fragment inside of an AnyDocument using the following code:
private static AnyDocument wrap(final XmlObject o) {
final AnyDocument anyDocument = AnyDocument.Factory.newInstance();
final AnyDocument.Any any = anyDocument.addNewAny();
any.set(o);
return anyDocument;
The problem, is that somehow my runtime type is getting lost after the wrapping
occurs.
Here is how the data looks BEFORE wrap (o.save()):
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xsi:type="loc:AddTermRequestT" xmlns:loc="http://www.overture.com/service/common/local"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:dis="http://www.overture.com/service/display">
<loc:accountId>1123223ZZZ</loc:accountId>
<loc:term>dog</loc:term>
<loc:price>0.55</loc:price>
</xml-fragment>
Note that in the above XML the runtime type is set as: xsi:type="loc:AddTermRequestT
Here is how the data looks after I attempt to wrap it with AnyDocument:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:any xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:dis="http://www.overture.com/service/display"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:loc="http://www.overture.com/service/common/local">
<loc:accountId>1123223ZZZ</loc:accountId>
<loc:term>dog</loc:term>
<loc:price>0.55</loc:price>
</xsd:any>
The runtime type is gone and it's not clear how to parse the new XML.
Am I doing something wrong? Why does the runtime type go away? Is this the correct
way to "warp" some fragment with a valid document.
Again, the intent here is to store something to the database that a different
tool can understand later.
Thanks.
-AP_

Use:
xmlOptions.setSaveOuter();

The size of a XML document stored in a XMLType table

Is there a way to find out (via SQL) the size of a XML document stored in a XMLType table or XMLType column (storage OR based)?
For instance in the way you could it retrieve if the XML document was stored in an XMLType column (CLOB based)
SQL> r
1 select dbms_lob.getlength(t.gegevens.getclobval()) "SIZE"
2 from hgo.hgo010_detam t
3* where rownum < 2
SIZE
2750

Is there a way to find out (via SQL) the size of a XML document stored in a XMLType table or XMLType column (storage OR based)?
For instance in the way you could it retrieve if the XML document was stored in an XMLType column (CLOB based)
SQL> r
1 select dbms_lob.getlength(t.gegevens.getclobval()) "SIZE"
2 from hgo.hgo010_detam t
3* where rownum < 2
SIZE
2750

Using value of a variable in XML fragment

Hi,
I am assigning an xml fragment to a webservice variable. The XML fragment is as mentioned below:
<ns2:ArrayOfKeyValuePair xmlns:ns2="http://www.themindelectric.com/package/com.taw.cca.common/"
xsi:type="soapenc:Array"
soapenc:arrayType="ns2:KeyValuePair[1]"
xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item xsi:type="ns2:KeyValuePair">
<key xsi:type="xsd:string">key</key>
*<value xsi:type="xsd:string" > 1234</value>*
</item>
</ns2:ArrayOfKeyValuePair>
In the above mentioned xml fragment, for the tag value I need to pass the data of a variable instead of the hardcoded string 1234. How can I resolve my issue?
Thanks

In the worst case, you could always resort to using scriptlets to retrieve the parameter. and set it up as an attribute in the local page scope.
<%
String param = (String)request.getParameter("collection");
Collection userCollection = (Collection)request.getAttribute(param);
pageContext.setAttribute("local_collection", userCollection);
%>
<forEach var="user" items="${local_collection}">
,,,I think this should work.
JSTL is great, but it can't yet replace every scriptlet, much as I would like it to.

Generating an XML Document from an internal table in ABAP

Good day to all of you;
With ABAP, in the R/3 system, I'm trying to figure out a way to accomplish the following:
1) SELECT a set of Purchase Order data into an internal table.
2) Generate an XML document, containing the above data, using a specific schema.
I've been playing around with function module SAP_CONVERT_TO_XML_FORMAT which has the following interface:
CALL FUNCTION 'SAP_CONVERT_TO_XML_FORMAT'
      EXPORTING
      I_FIELD_SEPERATOR    = ''
      I_LINE_HEADER        = ''
        I_FILENAME           = v_fname
      I_APPL_KEEP          = ''
      I_XML_DOC_NAME      = v_docname
      IMPORTING
        PE_BIN_FILESIZE      = v_byte
      TABLES
        I_TAB_SAP_DATA       = i_SapData
      CHANGING
        I_TAB_CONVERTED_DATA = i_XMLData
      EXCEPTIONS
        CONVERSION_FAILED    = 1
        OTHERS               = 2.
I'm uncertain as to whether or not the Export parameter, I_XML_DOC_NAME refers to some schema or definition and therefore have been excluding it. In doing so, the generated XML document seems to use the field name/type information from my itab for the tags.
If this function module requires an XML Document Name, how do I create one and where do I store it in R/3? If this is not the recommended solution, is anyone familiar with a way to load an XML schema, retrieve some data then have SAP generate an XML document using the schema?
Many thanks for any help available.
T

Hai Phillips
Try with the following Code
This program exports an internal table to an XML file.
Report ZPRUEBA_MML_13 *
Export an internal table to XML document *
NO BORRAR ESTE CODIGO *
REPORT ZPRUEBA_MML_13.
PANTALLA SELECCION *
    PARAMETERS: GK_RUTA TYPE RLGRAP-FILENAME.
PANTALLA SELECCION *
TYPE TURNOS *
TYPES: BEGIN OF TURNOS,
    LU LIKE T552A-TPR01,
    MA LIKE T552A-TPR01,
    MI LIKE T552A-TPR01,
    JU LIKE T552A-TPR01,
    VI LIKE T552A-TPR01,
    SA LIKE T552A-TPR01,
    DO LIKE T552A-TPR01,
END OF TURNOS.
TYPE TURNOS *
TYPE SOCIO *
TYPES: BEGIN OF SOCIO,
    NUMERO LIKE PERNR-PERNR,
    REPOSICION LIKE PA0050-ZAUVE,
    NOMBRE LIKE PA0002-VORNA,
    TURNOS TYPE TURNOS,
END OF SOCIO.
TYPE SOCIO *
ESTRUCTURA ACCESOS *
DATA: BEGIN OF ACCESOS OCCURS 0,
    SOCIO TYPE SOCIO,
END OF ACCESOS.
ESTRUCTURA ACCESOS *
START OF SELECTION *
START-OF-SELECTION.
    PERFORM LLENA_ACCESOS.
    PERFORM DESCARGA_XML.
END-OF-SELECTION.
END OF SELECTION *
FORM LLENA_ACCESOS *
FORM LLENA_ACCESOS.
REFRESH ACCESOS.
CLEAR ACCESOS.
MOVE: '45050' TO ACCESOS-SOCIO-NUMERO,
              'MOISES MORENO' TO ACCESOS-SOCIO-NOMBRE,
              '0' TO ACCESOS-SOCIO-REPOSICION,
              'T1' TO ACCESOS-SOCIO-TURNOS-LU,
              'T2' TO ACCESOS-SOCIO-TURNOS-MA,
              'T3' TO ACCESOS-SOCIO-TURNOS-MI,
              'T4' TO ACCESOS-SOCIO-TURNOS-JU,
              'T5' TO ACCESOS-SOCIO-TURNOS-VI,
              'T6' TO ACCESOS-SOCIO-TURNOS-SA,
              'T7' TO ACCESOS-SOCIO-TURNOS-DO.
APPEND ACCESOS.
CLEAR ACCESOS.
MOVE: '45051' TO ACCESOS-SOCIO-NUMERO,
              'RUTH PEÑA' TO ACCESOS-SOCIO-NOMBRE,
              '0' TO ACCESOS-SOCIO-REPOSICION,
              'T1' TO ACCESOS-SOCIO-TURNOS-LU,
              'T2' TO ACCESOS-SOCIO-TURNOS-MA,
              'T3' TO ACCESOS-SOCIO-TURNOS-MI,
              'T4' TO ACCESOS-SOCIO-TURNOS-JU,
              'T5' TO ACCESOS-SOCIO-TURNOS-VI,
              'T6' TO ACCESOS-SOCIO-TURNOS-SA,
              'T7' TO ACCESOS-SOCIO-TURNOS-DO.
APPEND ACCESOS.
ENDFORM.
FORM LLENA_ACCESOS *
FORM DESCARGA_XML *
FORM DESCARGA_XML.
DATA: L_DOM TYPE REF TO IF_IXML_ELEMENT,
              M_DOCUMENT TYPE REF TO IF_IXML_DOCUMENT,
              G_IXML TYPE REF TO IF_IXML,
              W_STRING TYPE XSTRING,
              W_SIZE TYPE I,
              W_RESULT TYPE I,
              W_LINE TYPE STRING,
              IT_XML TYPE DCXMLLINES,
              S_XML LIKE LINE OF IT_XML,
              W_RC LIKE SY-SUBRC.
DATA: XML TYPE DCXMLLINES.
DATA: RC TYPE SY-SUBRC,
BEGIN OF XML_TAB OCCURS 0,
              D LIKE LINE OF XML,
END OF XML_TAB.
CLASS CL_IXML DEFINITION LOAD.
G_IXML = CL_IXML=>CREATE( ).
CHECK NOT G_IXML IS INITIAL.
M_DOCUMENT = G_IXML->CREATE_DOCUMENT( ).
CHECK NOT M_DOCUMENT IS INITIAL.
WRITE: / 'Converting DATA TO DOM 1:'.
CALL FUNCTION 'SDIXML_DATA_TO_DOM'
EXPORTING
              NAME = 'ACCESOS'
              DATAOBJECT = ACCESOS[]
IMPORTING
              DATA_AS_DOM = L_DOM
CHANGING
              DOCUMENT = M_DOCUMENT
EXCEPTIONS
              ILLEGAL_NAME = 1
              OTHERS = 2.
IF SY-SUBRC = 0.
              WRITE 'Ok'.
ELSE.
              WRITE: 'Err =',
              SY-SUBRC.
ENDIF.
CHECK NOT L_DOM IS INITIAL.
W_RC = M_DOCUMENT->APPEND_CHILD( NEW_CHILD = L_DOM ).
IF W_RC IS INITIAL.
              WRITE 'Ok'.
ELSE.
              WRITE: 'Err =',
              W_RC.
ENDIF.
CALL FUNCTION 'SDIXML_DOM_TO_XML'
EXPORTING
              DOCUMENT = M_DOCUMENT
IMPORTING
              XML_AS_STRING = W_STRING
              SIZE = W_SIZE
TABLES
              XML_AS_TABLE = IT_XML
EXCEPTIONS
              NO_DOCUMENT = 1
              OTHERS = 2.
IF SY-SUBRC = 0.
              WRITE 'Ok'.
ELSE.
              WRITE: 'Err =',
              SY-SUBRC.
ENDIF.
LOOP AT IT_XML INTO XML_TAB-D.
              APPEND XML_TAB.
ENDLOOP.
CALL FUNCTION 'WS_DOWNLOAD'
EXPORTING
              BIN_FILESIZE = W_SIZE
              FILENAME = GK_RUTA
              FILETYPE = 'BIN'
TABLES
              DATA_TAB = XML_TAB
EXCEPTIONS
              OTHERS = 10.
IF SY-SUBRC <> 0.
              MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.
FORM DESCARGA_XML *
Thanks & regards
Sreenivasulu P

How to include variable inside XML Fragment in assign ?

HI..how are you today.
i need to assign an XML Fragment...like this into a variable:
<tns:pCmds>put @Encoded_Filename@</tns:pCmds>
<tns:pCmds>bye</tns:pCmds>
that Encoded_Filename is a variable..but of course..it is taking the whole put ...as a string...how can i tell bpel that the @@ is a variable?
i remember having some escape char to do so, but can figure out now..
Thanks in advance
P.

ok, i got what you were saying about CDATA, but i think my problem is the opposite..i WANT my string to be parsed..
when i assign <tag> put @filename@ </tag> i need that variable to be replaced..and right now, it is taken all as a simple string...

Adding XML fragments to a document in a XMLType table

Similar Messages

Maybe you are looking for