Xsl:include xsl:import and clob

I can use xslprocessor.processXSL to perform transformation where the XML and XSL are in CLOBs.
However, is it possible to perform transformation if the XML and XSLs are in CLOBs and the XSL have xsl:include and xsl:import?
Thanks and Regards,
Andy

It will be supported in later release.

Similar Messages

Xsl:include, dynamic href attribute

Is it possible to use a xsl parameter or variable for the href attribute of xsl:include ?
I tried
<xsl:param name="xxx" />
and then <xsl:include href="{$xxx}"/>
or even
<xsl:include>
<xsl:attribute name="href">
<xsl:value-of select="$xxx" />
</xsl:attribute>
</xsl:include>
None of this works (I haven't tried with other xslt processors than Oracle).
Any suggestions ?
null

I have attempted the same thing before as well. The only way I was able to dynamically build the xsl:include was to declare a new namespace e.g xmlns:out="output.xsl" in my XSL file and do something like the following:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:out="output.xsl">
<xsl:namespace-alias stylesheet-prefix="out" result-prefix="xsl"/>
<xsl:varible name="xxx" select=" 'myFile.xsl' "/>
<xsl:template match="/">
<out:stylesheet version="1.0">
<out:template match="/">
<out:include>
<xsl:attribute name="href">
<xsl:value-of select="$xxx" />
</xsl:attribute>
</out:include>
</out:template>
</out:stylesheet>
</xsl:template>
</xsl:stylesheet>
When applied to any valid XML document this produces the XSL file you are after as the output.
To use this output against your intended XML source consider the following: A Java program can very quickly apply the above stylesheet to any XML source to get the output you want... then apply that XSL result to the actual XML document you are wanting to transform. From here you can do what you want with the transformed result.

Xsl:include msg - document following root element must be well-formed

I am getting the following message when I try to execute a transaction that takes an XML file & transforms it. The message is:
"[ERROR]: XSLTransform error: javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed."
The transaction loads an xml input file, and then transforms it. The transformation stylesheet does some formatting to the xml. The stylesheet has an include in it that adds an element to the output.
Input XML data
<?xml version="1.0" encoding="UTF-8"?>
<Rowset>
    <Row>
        <ItemNo>00000000001884304</ItemNo>
        <ItemDesc>Test Item Description</ItemDesc>
    </Row>
</Rowset>
Expected output:
<?xml version="1.0" encoding="UTF-8"?>
<Item>
    <Items ItemDesc="Test Item Description" RawItemNo="00000000001884304" dotties="...................." editedItemNo="1884304" supernova="**********" />
</Item>
If I point the <xsl:include to a web folder on a test box, it will read & translate the data into the expected output. However, when I have both the initial stylesheet and the include stylesheet in the same Web folder in MII, I get the above message. If the URL is any different, it generates an IO error.
The initial stylesheet is
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
<xsl:output method="xml" />
<xsl:include href="http://myserver:myport/XMII/CM/foldername/testcalls_2.xsl"/>
<xsl:variable name="wrkitem" select="//ItemNo"/>
<xsl:template match="Row">
     <xsl:call-template name="RowEdit"/>
</xsl:template>
<xsl:template name="RowEdit" match="Row">
      <Item>
     <xsl:element name="Items" use-attribute-sets="RowChange">
           </xsl:element>
       </Item>
</xsl:template>
<xsl:attribute-set name="RowChange">
     <xsl:attribute name="RawItemNo">
           <xsl:value-of select="//ItemNo"/>
     </xsl:attribute>
     <xsl:attribute name="editedItemNo">
          <xsl:call-template name="removeLeadingZeros">
               <xsl:with-param name="originalString" select="$wrkitem"/>
          </xsl:call-template>
     </xsl:attribute>
     <xsl:attribute name="ItemDesc">
               <xsl:value-of select="//ItemDesc"/>
     </xsl:attribute>
     <xsl:attribute name="dotties">
          <xsl:call-template name="dots">
                     <xsl:with-param name="count" select="20"/>
              </xsl:call-template>
     </xsl:attribute>
     <xsl:attribute name="supernova">
          <xsl:call-template name="stars">
          </xsl:call-template>
     </xsl:attribute>
</xsl:attribute-set>
<xsl:template name="dots">
        <xsl:param name="count" select="1"/>
      <xsl:if test="$count > 0">
        <xsl:text>.</xsl:text>
        <xsl:call-template name="dots">
          <xsl:with-param name="count" select="$count - 1"/>
        </xsl:call-template>
      </xsl:if>
</xsl:template>
<xsl:template name="removeLeadingZeros">
<xsl:param name="originalString"/>
<xsl:choose>
    <xsl:when test="starts-with($originalString,'0')">
      <xsl:call-template name="removeLeadingZeros">
        <xsl:with-param name="originalString">
          <xsl:value-of select="substring-after($originalString,'0' )"/>
        </xsl:with-param>
      </xsl:call-template>
    </xsl:when>
    <xsl:otherwise>
      <xsl:value-of select="$originalString"/>
    </xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>
and the stylesheet being called by the xsl:include -
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template name="stars" match="Item">
<Stars>
     <xsl:element name="BBB">
          <xsl:text>**********</xsl:text>
     </xsl:element>
</Stars>
</xsl:template>
</xsl:stylesheet>
FYI, both of the stylesheets above are in the same folder on the WEB tab in MII. The full name (properties tab) is:
foldername/WEB/Test/stylesheet.xsl
Also, I am able to browse & view each of them in IE. The url they are at is:
http://server:port/XMII/CM/foldername/test/stylesheet.xsl
Both stylesheets appear to be well-formed.
If I use any other syntax other than the full URL, the error it generates is an IO Exception on the included stylesheet. The markup message above makes me believe that it is at least attempting to handle the included stylesheet.
In the Link editor of the xsl Transformation Incoming tab, there are two assignments being made.
1. Transform property
object= xsl_transformation_0
property=Transform
expression="db://foldername/WEB/Test/stylesheet.xsl" (this is the initial, not included stylesheet)
Link type=Assign Value
2. Input property
object= xsl_transformation_0
property=Input
Expression=testitems_0.XmlContent
Link type=Assign XML
Running MII 12.0
Thoughts? Any input appreciated.

In the first one you have two namespaces both with the same prefix.
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" and xmlns:xsi="http://xxxxxx/webservices/sites/"
Thanks,
Gaurav Jain
Flex SDK Team
http://www.gauravj.com/blog

How to copy a table with LONG and CLOB datatype over a dblink?

Hi All,
I need to copy a table from an external database into a local one. Note that this table has both LONG and CLOB datatypes included.
I have taken 2 approaches to do this:
1. Use the CREATE TABLE AS....
SQL> create table XXXX_TEST as select * from XXXX_INDV_DOCS@ext_db;
create table XXXX_TEST as select * from XXXX_INDV_DOCS@ext_db
ERROR at line 1:
ORA-00997: illegal use of LONG datatype
2. After reading some threads I tried to use the COPY command:
SQL> COPY FROM xxxx/pass@ext_db TO xxxx/pass@target_db REPLACE XXXX_INDV_DOCS USING SELECT * FROM XXXX_INDV_DOCS;
Array fetch/bind size is 15. (arraysize is 15)
Will commit when done. (copycommit is 0)
Maximum long size is 80. (long is 80)
CPY-0012: Datatype cannot be copied
If my understanding is correct the 1st statement fails because there is a LONG datatype in XXXX_INDV_DOCS table and 2nd one fails because there is a CLOB datatype.
Is there a way to copy the entire table (all columns including both LONG and CLOB) over a dblink?
Would greatelly appriciate any workaround or ideas!
Regards,
Pawel.

Hi Nicolas,
There is a reason I am not using export/import:
- I would like to have a one-script solution for this problem (meaning execute one script on one machine)
- I am not able to make an SSH connection from the target DB to the local one (although the otherway it works fine) which means I cannot copy the dump file from target server to local one.
- with export/import I need to have an SSH connection on the target DB in order to issue the exp command...
Therefore, I am looking for a solution (or a workaround) which will work over a DBLINK.
Regards,
Pawel.

Xsl:include and xml:import

I want to use another stylesheet within the original one.
the documentation just said how to declare an
xsl:include or xsl:import element as top level, but no examples about how to call the imported or included stylesheet.
I'll appreciate any examples you can provide to me .
Thanks
Chris

I've done this, and the way i think about it is that each "imported" XSL document combines (or are appended) into the XSL document that imports the other XSL documents. As such, all of the template matching that is occuring has to be consistent with the way the XML tags are matching up with XSL templates.
It is important that the templates in each imported XSL document will match up to the XML tags that the templates are designed to transform.
In other words, if i have an employee list <emp>, and an XSL template matching the <emp> element, i can produce a transformation on the list itself. now, i can define a transformation for a child element of <emp> by "importing" the XSL document that defines the template match for the child element (for example, "emp/lastName" can be what the second XSL document matches on).
Long story short, if you can paste the imported XSL into the importing XSL and things still work, then you can separate them out into multiple modular XSL files for inclusion.
-dave
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Christos Kouros ([email protected]):
I want to use another stylesheet within the original one.
the documentation just said how to declare an
xsl:include or xsl:import element as top level, but no examples about how to call the imported or included stylesheet.
I'll appreciate any examples you can provide to me .
Thanks
Chris<HR></BLOCKQUOTE>
null

XSU XSLT and using xsl:include href=""

I'm runing XDK 9.2 on an 8.1.7.4 database. I'm trying to transform the output of the XSU into a flat text file using a set of XSLT files. The main xslt includes the other xslt template files and then calls their templates by name as needed for different types of data in the XSU output.
I have the main xslt in a table of BFILEs that I read from and pass to the DBMS_XMLQUERY.SETXSLT procedure as a CLOB. I get the following errors when I run the main procedure to generate the flat text file:
oracle.xml.sql.OracleXMLSQLException: <Line 41, Column 35>: XSL-1002: (Error) Error while processing include XSL file (header.xslt).
at oracle.xml.sql.query.OracleXMLQuery.setXSLT(OracleXMLQuery.java:818)
at oracle.xml.sql.query.OracleXMLStaticQuery.setXSLT(OracleXMLStaticQuery.java:481)
"header.xslt" is one of the included xslts. Is there some way to specify the other xslts? I have tried loading them into the BFILE table, but it still doesn't work.

Hi I have tried out the code i.e. transforming a node and getting out a string representation. Following is code that works using JAXP apis.
import javax.xml.parsers.*;
import javax.xml.transform.*;
import javax.xml.transform.stream.*;
import javax.xml.transform.dom.*;
import org.w3c.dom.*;
import org.xml.sax.*;
import java.io.*;
public class XMLString {
public void xmlInString(Document document) throws Exception{
TransformerFactory tf = TransformerFactory.newInstance();
Transformer transformer =
tf.newTransformer();
StringWriter stWriter = new StringWriter();
transformer.transform(new DOMSource(document), new StreamResult(stWriter));
String strDOM = stWriter.toString();
System.out.println("String dom");
StringReader strIn = new StringReader(strDOM);
BufferedReader buffIn = new BufferedReader(strIn);
BufferedWriter bufOut = new BufferedWriter(new FileWriter("out.txt"));
String out = null;
while((out=buffIn.readLine()) != null){
bufOut.write(out, 0, out.length());
bufOut.flush();
bufOut.close();
public static void main(String args[]){
try{
XMLString strXML = new XMLString();
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
InputSource inputSource = new InputSource("input.xml");
Document doc = db.parse(inputSource);
strXML.xmlInString(doc);
}catch(Exception e){
System.out.println(e.getMessage());
e.printStackTrace();
I am using the xalan and xerces versions that come with the Java XML Winter pack from sun's website. The problem could lie with the underlying transformation processor you are using. It may not support transforming to a string or it could have a bug. So my advice is to find out what version transformation processor you are using. And look at the vendor's documentation to find any reference to this feature. Otherwise try using the Java XML Winter pack.

Problems faced when using xsl:include and extension functions

I am Working in XML and XSLT using Oracle's XML Parser V2.
Previously i had worked in Microsoft technology using MSXMLParser.
I am facing some problems in XSLT. They are as below...
1. Using <xsl-include href="Somexsl.xsl">
the oraclexmlparser processor is giving the error : XSL-1002: Error while processing include XSL file (no protocol: Submenu.xsl).
* Can u tell me why i am getting this error, and what is the fix for this.
The same case with <xsl:import> too.
2. In case i have to write some functions in the previous WD of xsl i used these statements
<?xml version='1.0'?>
<!DOCTYPE PageRoot SYSTEM "../../Common/dtd/PageNavBar.dtd">
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/TR/WD-xsl"
xmlns:html="http://www.w3.org/TR/REC-html40"
result-ns="">
<xsl:script xmlns:xsl="uri:xsl"><![CDATA[
var strWebContentPath = "/SurSITE/Content/";
var strWebImagePath = "/SurSITE/sursitegraphics/";
function IncScript()
return "<script language='javascript' src='/SurSITE/Includes/avalidations.js'></script>";
]]>
</xsl:script>
To call the function i used this
<xsl:eval no-entities='true'> IncScript();</xsl:eval>
* Can u tell me how do i do this now, i tried with the code above using the current name space (<xsl:stylesheet version="1.1"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" />)
Please use the example given above.
I will be very greatfull to u if u can give me some suggestion or help for the above said problems.
Thanking you and eagerly waiting for your reply(s).
null

The current version is "1.0" not "1.1"
You haven't included the code for what your <xsl:include>
statement looks like, which seems to be what it's complaining
about...
XSLT 1.0 has no <xsl:eval>, this is a microsoft specific tag
from a pre-XSLT-1.0 version.
XSLT 1.0 has no <xsl:script> element either.

Using xsl:import and trying to access a variable defined in another xsl

Hi
I am having a a.xsl file with contents liek this :
<xsl:variable name="PersonId" select="'1910'"/>
inside b.xsl i am importing a.xsl like
<xsl:import href="a.xsl"/>
<xsl:value-of select="$PersonId"/>
This is working fine when i am testing it standalone.
when i port the code to weblogic server (meaning when all the
project related files are placed in proper location in
weblogic) and start the application then i get the error msg :
xsl:1031 variable not defined 'PersonId'.
i tried giving the enite path like :http://localhost:7001/....
even then problem remains unresolved.
am i making any mistake ?
Thank you
Regards
Jaya

This works fine for me with Oracle XSL Processor 9.0.2C

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:variable name="PersonId" select="1910"/>
</xsl:stylesheet>and

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:import href="a.xsl"/>
<xsl:template match="/">
<xsl:value-of select="$PersonId"/>
</xsl:template>
</xsl:stylesheet>Make sure you're using the latest version of the XDK in your
weblogic environment.

Xsl:import and xsl:call-template errors for xslt in mediator (ORAMED-03601)

Hello,
I decided for performance issues with bpel execution to use a mediator instead.
In my requester i have a mediator that justs recieves an xml message, uses an xsl transformation (version 2) on that message and then sends it to the EBS.
The xsl file that's works correctly when used in a bpel process has both <xsl:import..../>and <xsl:call_template.../> tags.
When i tried and used the same xsl in the mediator i get an ORAMED-03601 error:
ORAMED-03601:[Invalid transformer configuration]Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "xsl/Xform_PriceListListABMReqMsg_to_PriceListEBMReqMsg.xsl"Possible Fix:Check log file for any exceptions and contact Oracle Support Services for further help
It works correctly again if i comment/remove all the imports and call-template and incorporate them in the xsl file itself.
Do anyone know if there are some limitations using xsl in a mediator instead of a bpel?

Hi,
I have a problem with call-template. I have passed
sed some parameter with call-template tag and used
that parameter in the conditional check tag <xsl:if>
i am getting the error. Can any body tell how to use
this? I actuall want to dynamically pass the tag name
as the parameter and check the attribute value of the
tag passed in the if condition and then i want to
person some action. How can i do it?
Here is the call-template code:
<xsl:call-template name="selected-unselected">
<xsl:with-param
ram name="currentTag">motor-carrier</xsl:with-param>
</xsl:call-template>
Here is the template definition:
<xsl:template name="selected-unselected">
<xsl:param
m name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./{$currentTag}/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./{$currentTag}/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>
Here is the sample xml code:
<motor-carrier selected="true"/>
<motor-truck selected="false"/>
<sched-mobile-equip selected="false"/>
Here instead of writing the condition check for every
tag i want to write it once and dynamically pass the
tag name as parameter to the template. If the
attribute of the tag has value true then one message
should be displayed otherwise a different message
should be displayed.try this:
<xsl:template name="selected-unselected">
     <xsl:paramm name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./*[name()=$currentTag]/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./*[name()=$currentTag]/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>

How to include XSL-Files stored in CLOBs in XSL-Files

Hi everybody!
Using a "standard" XSL-Parser, one can use
<xsl:include href="to-be-included.xsl" />
So, if i use the pl/sql xsl-parser, can I do anything simular to this, to include another xsl-document, which is stored in CLOB ?
Any idea or suggestion ?
Norbert

Please refer to the following post:
how to write DBUri-refs in XSLT stylesheets ?

Problem with xsl:import and xsl:apply-templates select="element_name"

I import a xsl tranformation into another xsl file.
During the transformation i want to limit the transformation to certain xml elements using the select attribute in apply-templates. However if I want restrict to xml elements whose templates are defined in the imported file, they will not be called.
I'm using currently JWSDP1.4 but problem was also with 1.3.
Can anybody help: Is this not xslt spec compliant or just a bug inXALAN ?
regards pszawlow

Solved it by myself:
the problem was not the import but the following:
xml file: looks like:
<a>
   <b>
   </b>
    <c>
    </c>
</a>xsl file looked like and should omit output of <c> </c>:
<xsl:template match="/">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
However / is not the level <a>, which I thought. So there was no matching <b>.
I changed the xsl file to:
<xsl:template match="/">
<xsl:apply-templates />
</xsl:template>
<xsl:template match="a">
<xsl:apply-templates select="b" />
</xsl:template>
<xsl:template match="b">
</xsl:template>
and it worked !

Xsl:import and precedence?

I am following Steve's example on using "ColumnOverrides.xsl"
(page 700) to create drill down links for certain values I'm
returning. Problem is, my generic:
<xsl:template match="ROW/*">
<td valign="top"><xsl:apply-templates/></td>
</xsl:template>
...seems to be taking precedence over the templates I am
<xsl:import>ing:
<xsl:template match="ROW/Team">
<td>
<xsl:apply-templates/>
</td>
</xsl:template>
<xsl:template match="ROW/League">
<td>
<xsl:apply-templates/>
</td>
</xsl:template>
The ROW/Team and ROW/League returned values are not in hyperlink
form.
I can verify that the import is working by changing the ROW/*
template to specify ROW/Team. When I do that, the value for team
remains normal/un-hyperlinked, but the value for ROW/League is
now the correct hyperlink! So, that leads me to believe that the
ROW/* is taking precedence over the ROW/Team and ROW/League
imports.
Steve's book says to use xsl:import to make sure imported
templates take higher predcedence. Am I missing something?
Thanks. Excuse my lenghtly post.

I figured it out. The <xsl:import>'s have to be in a particular
order as well.

Xsl:include and WAR Files

          We are trying to deploy our application using WAR file approach. We are using
          Weblogic 6.0 SP2 All our JSP and servlets are working fine.
          We have our reports generated based on XSL files. XSL files are put into the war
          file.
          In my transformation servlet, I am loading the original xsl file by calling getResourceAsStream(xslFileName);
          During the xsl transformation if we have any includes for another xsl file, I
          am getting an exception
          java.net.MalformedURLException: no protocol: myIncluded.xsl
          Basically in my original XSL file I have the following line
          <xsl:include href="myIncluded.xsl" />
          Could somebody tell me what I should doing to get rid off this exception.
          Thanks in advance
          SK


The href attribute needs a protocal to determin what kind of uri it is dealing with file,http, etc..
try changing this
<xsl:include href="myIncluded.xsl" />to this
<xsl:include href="file://./myIncluded.xsl" />
or this
<xsl:include href="file://myIncluded.xsl" />
I'm not sure how this plays out seeing how your using the getResourceAsStream method. I dont know if getting a resource this way will allow the xsl processor to resolve the url correctly or not. You may have to use a jar protocal or something like that to get it to work. You may even need to specify the absolute url to the include file.

xsl:include in XSL Workshop

I am trying to use <xsl:include> for some proxy stylesheet. I use the form
<xsl:include href="filename.xsl" />
I get the following error when process the stylesheet:
'Bad URI found while including/importing file: no protocol: filename.xsl'
Currently I am just working with the workshops, I have not deployed the xsl stilesheets yet to the server.
Everything works as expected in XMLSpy.
Does anybody have an example of a working <xsl:include>?

what about putting that file in the respository? or set up the XMLDIR and put it there? I have never done it but just a though.
Ben

Gif file in a xsl:include

Hi,
Can a .gif file be included in a xsl:include?
I cannot use <img src="/images/delete.gif"/> since the "src" part is
1)going to be dynamic and
2)cannot be returned as a TAG in the XML as well.
Thanks in advance...

why can't you make the image path a variable or parameter...
<xsl:param name="imgPath" select="your_code_or_set_it_externally" />
<IMG>
     <xsl:attribute name="SRC">
          <xsl:value-of select="$imgPath" />
     </xsl:attribute>
</IMG>

Xsl:include xsl:import and clob

Similar Messages

Maybe you are looking for