Xml-declaration="yes" in xsl:output

When I have a xml-declaration="yes" in my xsl:output, should I
get <?xml version="1.0" ... ?> in my output? I tried it on
Oracle xmlparser_v2_0_2 sample XSLSample.java and I did not get
the <?xml ...?> line. How do I modify the file so that it
outputs this line if I have xml-declaration="yes"?
Thanks.
Khun Yee
null

Khun Yee Fung (guest) wrote:
: When I have a xml-declaration="yes" in my xsl:output, should I
: get <?xml version="1.0" ... ?> in my output? I tried it on
: Oracle xmlparser_v2_0_2 sample XSLSample.java and I did not
get
: the <?xml ...?> line. How do I modify the file so that it
: outputs this line if I have xml-declaration="yes"?
: Thanks.
: Khun Yee
You should get this per the spec only it has not yet been
implemented. It will be in a future release.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

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

Xsl output placing %20 (spaces) in output

Xsl output placing %20 (spaces) in output when XSL file is
save by Dreamweaver CS3, I notice a problem in Dreamweaver CS3
today, when editing XSL files. Here is the xsl code
Note: I have no problems when using DW 8 for writing my xsl
style sheets. I suspect a setting in DW CS3 would fix this. My
current development environment is all hand coded, not using DW
server behaviors for any thing. Using MSXML2.DomDocument.4.0 for a
XML Parser.
Top part of file
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="
http://www.w3.org/1999/XSL/Transform"
version="1.0">
<xsl:output omit-xml-declaration="yes"/>
Works good this way (all the code on one line)
<xsl:value-of disable-output-escaping="yes"
select="url"/>?n=<xsl:value-of disable-output-escaping="yes"
select="navigationid"/>&p=<xsl:value-of
disable-output-escaping="yes" select="parentid"/>
I decided to make the code readable by placing the xsl calls
on separate lines using line return on the keyboard.
<xsl:value-of disable-output-escaping="yes"
select="url"/>?n=
<xsl:value-of disable-output-escaping="yes"
select="navigationid"/>&p=
<xsl:value-of disable-output-escaping="yes"
select="parentid"/>
The code above resulted in my query string having
%20%20%20%20%20 between the n= and value or p and value. It looks
like the DW CS3 is placing some character in the file that XSL
parser is interpreting as spaces (%20)
Note: Dreamweaver 8 does not have this problem. is there a
setting in CS3 to fix this, maybe a bug in DW CS3?
David Pearson

Hi,
The xsl:output is not yet implemented. This was specified in the README file.
Thanks,
Oracle XML Team
null

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/

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
;

Remove xml declarations when using xslt

Hi, i have created an xslt which transforms an xml file and then imports the information into a mysql database. It works and imports the information into the database but it also brings across the xml delcarations and the node names.
Is there a coldfusion way to remove these declarations, all i want is the information itself brought into the database.
Thanks
Chris

Hi Adam,
here is the code from the xsl file:
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE xsl:stylesheet [
    <!ENTITY nbsp " ">
    <!ENTITY copy "©">
    <!ENTITY reg    "®">
    <!ENTITY trade "™">
    <!ENTITY mdash "—">
    <!ENTITY ldquo "“">
    <!ENTITY rdquo "”">
    <!ENTITY pound "£">
    <!ENTITY yen    "¥">
    <!ENTITY euro "€">
]>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes" encoding="utf-8" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>
<xsl:template match="/">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
</head>
<body>
<xsl:for-each select="Items/Item[ItemType='Standard']">
<xsl:value-of select="EANNumber"/>
</xsl:for-each>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
And here is some sample data from the XML file:
<?xml version="1.0" encoding="UTF-8" ?>
<Items>
    <Item>
        <ItemType>Standard</ItemType>
        <EANNumber>111222333444</EANNumber>
    </Item>
</Items>
Thanks alot, i appreciate the help.
Chris

Is it possible to remove xml declaration from a target HTTP msg in PI 7.1?

Hello,
I am working on a SOAP to HTTP scenario in PI 7.1.
I am using a java mapping to create a target string. This target string does not contain XML declaration(<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>) in it.
To elaborate the issue, while testing the message mapping, this XML declaration is not being prefixed to the message content. But, in integration engine, the http target message is being prefixed by this XML declaration by default.
Output when tested in Operation Mapping(Desired result):
abc=123:def=456
Output been sent to receiver:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> abc=123:def=456
Is there any possibility to send a HTTP message to the receiver without this XML declartion. In other words, I need only the message content to be sent to the receiver.
Kindly suggest.
Regards,
Swetha

Hi,
You can use JAVA/or XSLT mapping
See this for Code
Remove Encoding UTF from xml declaration in PI

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);
}

Xslt does not output XML declaration

Hi there!
I have been trying for days to transform an XML doc into another one using an XSL stylesheet (that contains a <xsl:output method=xml/> tag...).
different methods:
-using xmltransform(xmltype(xmldoc), xmltype(xsldoc)) I get a xml fragment, without xml declaration...
even if i later parse it and generate a Domdocument with both xmldom.setVersion() and xmldom.setcharset(), i still don't get my xml declaration in my output tree...
-using dbms_xslprocessor, i get a <dummy/> document...probably a problem with the newStylesheet generation...by the way, could anyone explain to me what is the reference URl argument for nesStylesheet???
thanks for your help, I am getting crazy!!!

Hi there!
I have been trying for days to transform an XML doc into another one using an XSL stylesheet (that contains a <xsl:output method=xml/> tag...).
different methods:
-using xmltransform(xmltype(xmldoc), xmltype(xsldoc)) I get a xml fragment, without xml declaration...
even if i later parse it and generate a Domdocument with both xmldom.setVersion() and xmldom.setcharset(), i still don't get my xml declaration in my output tree...
-using dbms_xslprocessor, i get a <dummy/> document...probably a problem with the newStylesheet generation...by the way, could anyone explain to me what is the reference URl argument for nesStylesheet???
thanks for your help, I am getting crazy!!!

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)

Problems with the xsl element ---- xsl:output method="xml"/ ----

Hy, my problem is the next, I am trying to read a xml file and transform it in itself but when I do with XSLT, Internet Explorer doesnt show a xml file, just show me the text nodes of the xml file. I have the element <xsl:output method="xml"/>" in the xsl file but I dont Know what Iam doing wrong.
The next code is from the xsl file:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:template match="/">
<xsl:copy-of select="catalog"/>
</xsl:template>
</xsl:stylesheet>
The next code is from the xml file:
<?xml version="1.0" encoding="UTF-8"?>

<?xml-stylesheet type="text/xsl" href="PlantillaXSL.xml"?>
<catalog dni="4546545">
     <cd numero="2" id="5" color="red">
          <title>Empire Burlesque</title>
          <artist>Bob Dylan</artist>
          <country>USA</country>
          <company>Columbia</company>
          <price>10.90</price>
          <year>1985</year>
     </cd>
</catalog>
The result in internet explorer is:
Bob Dylan USA Columbia 10.90 1985

All right. I asked because it's unusual to use the ".xml" extension for an XSL file, so I thought it might be an error. But there's nothing wrong with that.
Next debugging step: is that XSL file actually being used? Insert some debugging code in it so that you can tell.

Xsl:output not yet implemented??

Is the xsl:output tag implemented in oracle
xslt?
I've tryed this in an xsl file:
<xsl:output method="xml" encoding="ISO-8859-1" omit-xml-declaration="no" doctype-system="Segnatura.dtd" indent="yes" />
With another xslt processor produces this header:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE Segnatura SYSTEM "Segnatura.dtd">
while with xdk the header is empty!!
I'm doing something wrong or not?
Please I really nead help on this topic.
Thanks
mauro

We fully implement <xsl:output>
the most common error is that programmer's accidentally use:
DocumentFragment processXSL(xsl,xml)
instead of the:
void processXSL(xsl,xml,PrintWriter)
Only the latter gives the XSLT processor a chance to control the serialization and implement the <xsl:output> hints.

XmlTransform() and an Unnecessary XML declaration

Is there a way to stop this code from producing an
unnecessary XML
declaration. When I run the following code it produces an XML
declaration after the body tag.
<body>
<?xml version="1.0" encoding="UTF-8"?>
Is there someway to control this, or do I just need to do
some string
parsing after the transformation?
<cfsavecontent variable="displayXSL">
<xsl:stylesheet version="1.0"
xmlns:xsl="
http://www.w3.org/1999/XSL/Transform">
<xsl:template match="table/thead" />
<xsl:template match="table/tr">
<div>
<strong><xsl:value-of
select="td[1]"/></strong>
</div>
</xsl:template>
</xsl:stylesheet>
</cfsavecontent>
</cfsilent><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML
1.1//EN"
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" />
<title>XSLT Fun</title>
</head>
<body>
<cfoutput>#xmlTransform(skillsXML,displayXSL)#</cfoutput>
</body>
</html>

Ian Skinner wrote:
> Is there a way to stop this code from producing an
unnecessary XML
> declaration.
Why yes, yes there is a way to stop this. Add the following
line to
your XSLT code Ian.
<xsl:output method="html" encoding="utf-8"/>

How to change xml declaration using jaxb Marshaller

please, my xml declaration, in the output file generated by jaxb: javax.xml.bind.Marshaller is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
I need to change it in:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="style.xsl"?>
I don't have idea about how to change.
thanks a lot alessandro

Hello.
public void saveJaxbObjectToFile(String packageName, Object myJaxbObject, String fileName)
throws JAXBException, ParserConfigurationException, TransformerConfigurationException,
TransformerException, FileNotFoundException, IOException {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setNamespaceAware(true);
DocumentBuilder db = dbf.newDocumentBuilder();
org.w3c.dom.Document document = db.newDocument();
JAXBContext jAXBContext = JAXBContext.newInstance(packageName);
Marshaller m = jAXBContext.createMarshaller();
m.marshal(myJaxbObject, document);
ProcessingInstruction processingInstruction = document.createProcessingInstruction("xml-stylesheet", "type=\"text/xsl\" href=\"style.xsl\"");
Node rootElement = document.getDocumentElement();
document.insertBefore(processingInstruction, rootElement);
TransformerFactory transformerFactory = TransformerFactory.newInstance();
Transformer transformer = transformerFactory.newTransformer();
transformer = transformerFactory.newTransformer();
transformer.setOutputProperty("indent", "yes");
transformer.setOutputProperty("encoding", "UTF-8");
transformer.setOutputProperty("version", "1.0");
FileOutputStream fos = new FileOutputStream(fileName);
transformer.transform(new DOMSource(document), new StreamResult(fos));
fos.flush();
fos.close();
Good luck.

XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context

Following is my development environment:
JDeveloper 9i Release Candidate
JDeveloper JVM 1.3.1
Oracle XML Parser v2 9.2.0.0.0
I'm using the Oracle XML Parser V2 9.2.0.0.0 library to apply a stylesheet to an XML document. However when I invoke the call to processor.processXSL() an XSLException is thrown with the following details:
oracle.xml.parser.v2.XSLException: <Line 1, Column 116>: XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context.
exception
Below is the sequence of events:
// Create an instance of XSLProcessor to perform the transformation
XSLProcessor processor = new XSLProcessor();
// create a Reader from a String object that contains the stylesheet text
StringReader r = new StringReader( stylesheet );
// create a new XSL stylesheet, passing it the Reader object reference
XSLStylesheet sheet = processor.newXSLStylesheet(r);
// apply the stylesheet
// the variable sheet represents the XSLStylesheet object
// the variable source represents the XMLDocument object
// this call throws the exception
DocumentFragment df =
processor.processXSL(sheet,source);
I've included the Stylesheet and source XML file I'm processing below.
Note: My application works fine when I use the Oracle XML Parser v2 9.0.1 library. (although I have to use new XSLStylesheet() in place of XSLProcessor.newXSLStylesheet())
Any ideas on what has changed between the two releases? I do have a reproducible test case that I can send on if required?
thanks in advance
private String stylesheet =
"<INSERT xsl:version=\"1.0\" xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\"> "+
"<xsl:output method=\"xml\" indent=\"yes\"/> "+
"<ROWSET table_name=\"acc_database\"> "+
" <xsl:for-each select=\"DATABASES/DATABASE\"> "+
" <ROW> "+
" <DBID><xsl:value-of select=\"DBID\"/></DBID> "+
" <DBNAME><xsl:value-of select=\"DBNAME\"/></DBNAME> "+
" <DBSIZE><xsl:value-of select=\"DBSIZE\"/></DBSIZE> "+
" <DBPATHNAME><xsl:value-of select=\"DBPATHNAME\"/></DBPATHNAME> "+
" <DBUSER><xsl:value-of select=\"DBUSER\"/></DBUSER> "+
" <DBPASSWORD><xsl:value-of select=\"DBPASSWORD\"/></DBPASSWORD> "+
" <ISAPPDB><xsl:value-of select=\"ISAPPDB\"/></ISAPPDB> "+
" <ISATTACHEDDB><xsl:value-of select=\"ISATTACHEDDB\"/></ISATTACHEDDB> "+
" <CONVERTDB><xsl:value-of select=\"CONVERTDB\"/></CONVERTDB> "+
" <VERSION><xsl:value-of select=\"VERSION\"/></VERSION> "+
" </ROW> "+
" </xsl:for-each> "+
"</ROWSET> "+
"</INSERT>";
<?xml version="1.0" encoding="ISO-8859-1"?>


<DATABASES>
<DATABASE>
<DBID>1</DBID>
<DBNAME>xmltest</DBNAME>
<DBSIZE>1</DBSIZE>
<DBPATHNAME>E:\xmltest.mdb</DBPATHNAME>
<DBUSER>xmltest</DBUSER>
<DBPASSWORD>oracle</DBPASSWORD>
<ISAPPDB>1</ISAPPDB>
<ISATTACHEDDB>0</ISATTACHEDDB>
<CONVERTDB>1</CONVERTDB>
<VERSION>4.0</VERSION>
<TABLES>
<TABLE PRIMARY_KEY="1">
<TBLID>1</TBLID>
<DBID>1</DBID>
<TBLNAME>xsu_test</TBLNAME>
<CNVTABLESTRUCT>1</CNVTABLESTRUCT>
<CNVMOVEDATA>1</CNVMOVEDATA>
<CNVRI>1</CNVRI>
<CNVVALIDATION>1</CNVVALIDATION>
<CNVDEFAULT>1</CNVDEFAULT>
<CNVADDTIMESTAMP>1</CNVADDTIMESTAMP>
<ATTACHTABLEBACKTOACCESS>1</ATTACHTABLEBACKTOACCESS>
<SAVEPASSWORD>0</SAVEPASSWORD>
<CNVMAKEUPDATEABLE>1</CNVMAKEUPDATEABLE>
<RETAINLOCALCOPY>0</RETAINLOCALCOPY>
<SYNCWITHSERVER>1</SYNCWITHSERVER>
<OWNERID>1</OWNERID>
<VALIDATIONTEXT></VALIDATIONTEXT>
<VALIDATIONRULE></VALIDATIONRULE>
<NUMBEROFROWS>1</NUMBEROFROWS>
<CACHINGTABLE>0</CACHINGTABLE>
<DESCRIPTION></DESCRIPTION>
<COLUMNS>
<COLUMN>
<COLID>1</COLID>
<TBLID>1</TBLID>
<COLNAME>id</COLNAME>
<COLTYPE>4</COLTYPE>
<COLTYPEDESC>Long</COLTYPEDESC>
<COLAUTOINCR>1</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>4</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>1</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
<COLUMN>
<COLID>2</COLID>
<TBLID>1</TBLID>
<COLNAME>name</COLNAME>
<COLTYPE>10</COLTYPE>
<COLTYPEDESC>Text</COLTYPEDESC>
<COLAUTOINCR>0</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>50</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>2</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
</COLUMNS>
<INDEXES>
<INDEX>
<INDID>1</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>id</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>0</ISPRIMARY>
<ISUNIQUE>0</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>0</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>1</INDCOLID>
<INDID>1</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
<INDEX>
<INDID>2</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>PK_xsu_test</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>1</ISPRIMARY>
<ISUNIQUE>1</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>1</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>2</INDCOLID>
<INDID>2</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
</INDEXES>
</TABLE>
</TABLES>
<RELATIONS>
</RELATIONS>
</DATABASE>
<ATTACHED_TABLES>
</ATTACHED_TABLES>
</DATABASES>

Your problem is that your stylesheet is illegal.
You're using the "simple form" of the stylesheet which
is equivalent to having a single root template.
If you use the simple form, you cannot use: <xsl:include>,
<xsl:import>, <xsl:output>, <xsl:param>
or any other <xsl:XXX> element which must be at the "top-level"
of the stylesheet.
The solution is to change from:
<INPUT xsl:version="1.0" xmlns:xsl="...">
   <xsl:output>
</INPUT>.
which is illegal to:
<xsl:stylesheet version="1.0" xmlns:xsl="...">
    <xsl:output>
    <xsl:template match="/">
      <INPUT>
      </INPUT>
    </xsl:template>
</xsl:stylesheet>

Xml-declaration="yes" in xsl:output

Similar Messages

Maybe you are looking for