DBMS_XDB.createResource(path, XMLTYPE) removes the XML declaration

Hi,
I'm writing out XML documents to the XMLDB repository by looping through a view which has an XMLTYPE column and writing each instance of that column using the 2nd form of createresource specified in the PL/SQL Packages and Types Reference.
DBMS_XDB.CREATERESOURCE(
path IN VARCHAR2,
data IN SYS.XMLTYPE)
RETURN BOOLEAN;
It creates the resource but the xml is missing the <?xml version="1.0" encoding="UTF-8"?> declaration.
Any idea of why this is happening and how I can fix it, preferably without having to mess about with converting XMLTYPE to VARCHAR2 and prepending the declaration.
Thanks,
Chris
Oops forgot the version info. Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 on Windows
Edited by: chrisis on Oct 16, 2009 2:31 PM

I had VERSION NO VALUE, STANDALONE NO VALUE on the XMLRoot function.

Similar Messages

How to remove the standalone="yes" attribute in the xml declaration?

Hi,
I am using JAXB 2.0 to generate XML files. Can anyone tell me how to remove the standalone="yes" attribute in the xml declaration? Thanks in advance.
-Joey

Just open the file with your favorite text program and type away. If you get a permissions problem (file is locked by...) then just stop tomcat and open/edit/save the file and restart tomcat.
I also think that the admin context that comes with tomcat might allow you to modify/add/edit your users (not sure though)

Force the xml declaration to show when the xmltype in generated

Hi.
I use oracle 9.2i .
When i generate the XML the xml declaration doesnt show.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
Only if i do a getclobval(), but that returns a string that has spaces and alot of other stuff that i don't want.
Is there any way to return the xml declaration when i call a xmltype?
I know i asked a similar question before, but the answer i got was to use getclobval... but must be another way..
I hope you can help me, cheers.

Maybe time to patch??
SQL> select * from v$version where rownum = 1
BANNER
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
1 row selected.
SQL> select xmltype
             ('<?xml version="1.0" encoding="UTF-8" standalone="no"?>'
              || xmlforest ('some_value' as "root_element")
             ) xml
from dual
XML
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<root_element>some_value</root_element>
1 row selected.

How to specify the XML Declaration for an XML variable

I need to set the XML declaration for my XML variable as
follows:
var employees:XML =
<?xml version="1.0" encoding="utf-8"?>
<employees>
<employee ssn="123-123-1234">
<name first="John" last="Doe"/>
<address>
<street>11 Main St.</street>
<city>San Francisco</city>
<state>CA</state>
<zip>98765</zip>
</address>
</employee>
<employee ssn="789-789-7890">
<name first="Mary" last="Roe"/>
<address>
<street>99 Broad St.</street>
<city>Newton</city>
<state>MA</state>
<zip>01234</zip>
</address>
</employee>
</employees>;
However, if I specify <?xml version="1.0"
encoding="utf-8"?>, I get a design time and compile error. If I
remove it it works fine. But the server to which I send this XML is
expecting the declaration. Can somebody help me with this?
Thanks

I work mostly with the Java versions of the parser so you'll have to make the translation to C++. As far as I know, you can't use the SAX API to access to the encoding.
You need to use the DOM along with Oracle's extension to the basic DOM functionality. Oracle's package, oracle.xml.parser.v2 defines a class which implements the Document interface called XMLDocument. This class has a method, getEncoding(), which returns the encoding. You would use the method in getDocument() in the Parser base class inherited by DOMParser to retrive the XMLDocument.
Jeff

How to exclude the XML declaration from each row of the result set?

Hi,
I have a table with an XMLTYPE column and would like to SELECT a set of rows. How can I exclude the XML declaration from each row in the result set? My query currently looks like this, I'm executing it through Spring JDBC:
SELECT XMLSerialize(CONTENT t1.xmltext) FROM myschema.event t1 WHERE XMLEXISTS('$e/Event' PASSING XMLTEXT AS "e") ORDER BY t1.time DESC
After selecting, in my application I convert each row into a String and concatenate all rows into one big string in order to parse it into a DOM model. I get a parser exception (org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed) because there are multiple XML declarations in my big string. Of course, I could manually check the String of each row whether it starts with the XML declaration, but it would be nicer if I could instruct the DB not to add it in the first place. Is there a way?
Thanks!
-- Daniela

Hi,
A couple of options I can think of :
SELECT XMLSerialize(CONTENT
XMLtransform(t1.xmltext,
xmltype('<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes"/>
<xsl:template match="/"><xsl:copy-of select="*"/></xsl:template>
</xsl:stylesheet>')
FROM myschema.event t1
WHERE XMLEXISTS('$e/Event' PASSING XMLTEXT AS "e")
ORDER BY t1.time DESC
;or simply,
SELECT XMLSerialize(CONTENT
extract(t1.xmltext,'/')
FROM myschema.event t1
WHERE XMLEXISTS('$e/Event' PASSING XMLTEXT AS "e")
ORDER BY t1.time DESC
;

How to remove the XML attribute value in Indesign file by javascript

Hi all,
How to remove the XML attribute value in Indesign file.

Try this,
if(elm.xmlElements[i].xmlAttributes[j].name == "aid:pstyle" || elm.xmlElements[i].xmlAttributes[j].name == "aid:cstyle")
Vandy

Omit the XML declaration when using the PHP MM_XSLTransform class

Hi
Is there any way to omit the XML declaration when using the
PHP MM_XSLTransform class?
When using the PHP MM_XSLTransform to transform some XML into
HTML, the XML declaration is faithfully delivered, which is
expected. In my case though this ends up in the body of the
document and is not desired. I wish to choose that the XML
declaration is not shown.
I have tried to use the <xsl:output method="xml"
encoding="utf-8" omit-xml-declaration="yes"/> in the XSL
stylesheet but the declaration still appears.
Any help?
all the best
Dave

Jim20005 wrote:
> I'm using XLS transfomation in DW for reading XML files.
Now (I'm just back
> form holiday), my webspace provider has updated to php
5.1.5. I'm getting this
> error:
Comment out line 301 and add two new lines immediately after
it like this:
// $xml = DOMDocument::loadXML($content);
$doc = new DOMDocument();
$err = $doc->loadXML($content);
This is part of a PHP 8.0.2 hotfix that can be obtained
directly from
Adobe support.
David Powers
Adobe Community Expert
Author, "Foundation PHP for Dreamweaver 8" (friends of ED)
http://foundationphp.com/

Remove XML declaration header in Oracle

Hi,
is there a way to remove the XML declaration <?xml version="1.0" ?> generated by oracle - ex
- <Envelope>
- <Body>
<?xml version="1.0" ?>
- <MSG09>
to
- <Envelope>
- <Body>
- <MSG09>
Thanks

Hi,
is there a way to remove the XML declaration <?xml version="1.0" ?> generated by oracle - ex
- <Envelope>
- <Body>
<?xml version="1.0" ?>
- <MSG09>
to
- <Envelope>
- <Body>
- <MSG09>
Thanks

How to remove the ?xml declaration.

Hi,
We are processing a large ASCII input file and converting it into XML. When we do it on a single go, the JVM crashes due to out of memory error.
We tried to write the XML output for a group of input lines into the file and start processing the next set. We get the <?xml> declarative tag every time we write to the file. How can we remove this?
Thanks in advance.

This is how I managed to do it. The latest xerces.xml.serializer package claims to do it as well for various sgml (html/xml etc) but the help is incomplete and I can find nothing on the internet to do this. Historically (ie a year ago) I've seen code such as XMLSerializer s = new XMLSerializer(Properties properties); s.serialize()... But this has been deprecated.
It seems a great shame to me that Microsoft is running away with decent usable implementations of the DOMDocument standards.
   * Serializes the given document to the writer, optionally omitting the xml declaration
   * @param source
   * @param output
   * @throws XMLException
public static void transform(Document source, Result output, boolean omitXmlDeclaration)
      throws XMLException
    try {
      if (output == null) {
        throw new IllegalArgumentException("Output result stream cannot be null");
      if (source == null) {
        throw new IllegalArgumentException("Source document cannot be null");
      Transformer transformer = TransformerFactory.newInstance().newTransformer();
      transformer.setOutputProperty("omit-xml-declaration", omitXmlDeclaration ? "yes" : "no");
      transformer.transform(new DOMSource(source), output);
    catch (Exception e) {
      Log.error("Error in transform", e);
      throw new XMLException(e);
}

Remove Structured Anchored Frame without disturbing the XML Structure - Reg.

Dear All,
Please any one help me!, How to remove the xml Structured Anchored Frame without disturbing the XML Structure.
Manually If I'm removing the XML Structured Anchored Frame, the XML Structured is gone.
I tried so many ways. If I am removing manually in Grouped Frame, then this problem is not happens.
I mean, Create 2 separate frames Move any xml structured contents to that frames. Group that 2 frames and make it anchored.
Now you can remove that anchored, this xml Structure is not disturbing (I mean not removed).
If I did the same in above method for Single Text Frame, this xml Structure is gone.
Kindly any one person resolve this problem, Thanks in advance!!!
Note:
(1) I tried through in InDesign CS6 Plug-In, this is working perfectly. But I need in Javascript to do this.
Thanks & Regards
T.R.Harihara SudhaN

Hm – if you can do it with a Group object, why don't you wrap around a group object?
With ExtendScript it's quite possible to create Groups with only one single object.
If we have a text frame selected, you could add a "helper" rectangle to the spread.
Group the text frame and the rectangle, then remove the rectangle from the group.
Now you have a Group with a single text frame.
var myTextFrame = app.selection[0];
var myHelperRectangle = app.documents[0].layoutWindows[0].activeSpread.rectangles.add();
var myGroup = app.documents[0].layoutWindows[0].activeSpread.groups.add([myTextFrame,myHelperRectangle]);
myGroup.rectangles[0].remove();
app.documents[0].select(myGroup);
Uwe

Oracle Service Bus 11g omit-xml-declaration="yes" not working in XSL-T

I have the requirement of removing the XML header from xsl output.
eg: <?xml version="1.0" encoding="UTF-8" ?> this part has to removed
I tried using the following in XSLT:
<xsl:output indent="yes" omit-xml-declaration="yes" />.
It seems to work in all online xml compilers. It does not work in work in OSB.
I posted the message in a JMS Queue and it contains the xml header.
Is this a work around for this issue?

I'm pretty sure XSLT has nothing to do with that PI.
After all, XSLT in OSB doesn't format text, it generates an XmlObject. The formatting (including adding the <?xml?> PI) are done by other parts of the engine. Probably the XmlBeans serializator.
The only option I see is to serialize the XML, then cut off everything until first ?>.
Why would you need that, I wonder? May be there is a better way.
Vlad @ genericparallel.com

How to specify XML declaration in an XML Variable

I had posted this question in the Flex Builder discussion,
but I am not sure if that was the right board, so posting it again
here:
I need to set the XML declaration for my XML variable as
follows:
var employees:XML =
<?xml version="1.0" encoding="utf-8"?>
<employees>
<employee ssn="123-123-1234">
<name first="John" last="Doe"/>
<address>
<street>11 Main St.</street>
<city>San Francisco</city>
<state>CA</state>
<zip>98765</zip>
</address>
</employee>
<employee ssn="789-789-7890">
<name first="Mary" last="Roe"/>
<address>
<street>99 Broad St.</street>
<city>Newton</city>
<state>MA</state>
<zip>01234</zip>
</address>
</employee>
</employees>;
However, if I specify <?xml version="1.0"
encoding="utf-8"?>, I get a design time and compile error. If I
remove it it works fine. But the server to which I send this XML is
expecting the declaration. How can I set the declaration?
Any help or pointer is appreciated.

I am not able to load the xml. Can anybody figure out the
problem :
I have used a LoadXML class :
package {
import flash.display.*;
import flash.events.*;
import flash.net.*;
// Demonstrates the code required to load external XML
public class LoadXML extends Sprite {
// The property that will eventually contain the loaded XML
private var novel:XML;
// The object used to load the XML
private var urlLoader:URLLoader;
// Constructor
public function LoadXML () {
// Specify the location of the external XML
var urlRequest:URLRequest = new URLRequest("novel.xml");
// Create an object that can load external text data
urlLoader = new URLLoader();
// Register to be notified when the XML finishes loading
urlLoader.addEventListener(Event.COMPLETE,
completeListener);
// Load the XML
urlLoader.load(urlRequest);
// Method invoked automatically when the XML finishes
loading
private function completeListener(e:Event):void {
// The string containing the loaded XML is stored in the
URLLoader
// object's data property (urlLoader.data). To create a new
XML
// instance from that loaded string, we pass it to the XML
constructor
novel = new XML(urlLoader.data);
trace(novel.toXMLString()); // Display the loaded XML, now
converted
// to an XML object
And in main.mxml :
myXml = new LoadXml ;
trace ( myXml.novel ) ;
The output is errenous

Removing an XML Schema through Enterprise Manager

Hi all,
I have created an XML schema using the Enterprise Manager. But the problem is that I can't remove it. When I use the menu option to remove the XML Schema, I get the following error:
VBO-8051: XML Schema cannot be dropped.
ORA-31000:Resource [User].[SchemaName] is not an XDB document
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 0
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 80
ORA-06512: at line 1
If anyone has any thoughts they would be greatly appreciated.
Thank you,
Mike

What was the URL used to register the schema. Is this the same URL that was passed to delete schema. You can check the list of registered schemas with the following query
SQL> desc user_xml_schemas
Name Null? Type
SCHEMA_URL VARCHAR2(700)
LOCAL VARCHAR2(3)
SCHEMA SYS.XMLTYPE(XMLSchema "http:
//xmlns.oracle.com/xdb/XDBSc
hema.xsd" Element "schema")
INT_OBJNAME VARCHAR2(4000)
QUAL_SCHEMA_URL VARCHAR2(2839)
SQL> select schema_url from user_xml_schemas
2 /
SCHEMA_URL
http://localhost:8080/home/SCOTT/xsd/purchaseOrder.xsd

Remove Empty XML Tags using module parameters

Hi All,
In my lanscape I have two PI Systems.
My scenario is an IDOC reaches 1st PI system gets converted into an EDIFACT and then goes to the 2nd PI and from there it gets routed to the respective AS2 Party.
I am using SOAP to pass message between the PI systems and B2B Toolkit's AS2 Adapter for the communication with AS2 party.
The issue is when the message is getting converted from IDOC to EDIFACT there are a few feilds with occurence 1..1 and due to these fields i get an empty XML tag at the output. These empty XML tags give me an error in the B2B Toolkit's AS2 Adapter Receiver Channel
I cannot change the occurence in the structure of the EDIFACT nor can I use an XSLT mapping to remove empty tags before the message reaches the Communication Channel.
I want to know if there are any module parameters which i can use either in SOAP Channel or the AS2 Channel to remove the XML Tags.

Hi Muni,
"1..1 means, you must send some values for that fields. try to find out why these are not getting any values."
This empty tag is expected. Before using B2B Toolkit's AS2 Adapter we used to use Seeburger's AS2 Adpater and the message used to get executed successfully with these empty tags.The issue is coming only when we are using B2B Toolkit's AS2 Adapter.
"if you want to stop sending(the fields which are not needed in target) you can you can disable the fields in the message mapping."
I cannot disable the feild in the mapping as some other message may use this field.
Thanks,
Farhaan

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

DBMS_XDB.createResource(path, XMLTYPE) removes the XML declaration

Similar Messages

Maybe you are looking for