FIXED: BUG in Oracle XSLT processor

Edit: I fixed it by just importing all of the Jdev libraries. My bad for being a dolt.
I am trying to detect certain values in an XML document that start with $ (the dollar sign) character. This has some conflicts with the syntax for XSL variables. The following code gives an exception when running in the Oracle XSLT...
<xsl:template name="interpretToken">
<xsl:param name="token" />
<xsl:choose>
<xsl:when test="starts-with($token, '$')" >
<a><xsl:attribute name="href">
<xsl:value-of select='replace($token, "\$", "#")' />
</xsl:attribute>
<xsl:value-of select='replace($token, "\$", "")' />
</a>
</xsl:when>
</xsl:choose>
</xsl:template>
(note that this isn't the best way to write the above code, but replace suffices)
When I run this in the XSLT of JDev 10.1.3.2, the following stack trace is given:
Exception in thread "Thread-1" java.lang.NoClassDefFoundError: oracle/i18n/text/OraNormalizer
     at oracle.xml.util.UnicodeUtil.<clinit>(UnicodeUtil.java:35)
     at oracle.xml.xslt.XSLSAXPrintDriver.printAttributes(XSLSAXPrintDriver.java:492)
     at oracle.xml.xslt.XSLSAXPrintDriver.startElement(XSLSAXPrintDriver.java:408)
     at oracle.xml.xslt.XSLEventHandler.reportStartElement(XSLEventHandler.java:267)
     at oracle.xml.xslt.XSLEventHandler.characters(XSLEventHandler.java:863)
     at oracle.xml.xslt.XSLValueOf.processAction(XSLValueOf.java:143)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:181)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:157)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLCallTemplate.processAction(XSLCallTemplate.java:132)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:181)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:157)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLCallTemplate.processAction(XSLCallTemplate.java:132)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:181)
     at oracle.xml.xslt.XSLCondition.processAction(XSLCondition.java:157)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:242)
     at oracle.xml.xslt.XSLApplyTemplates.processAction(XSLApplyTemplates.java:142)
     at oracle.xml.xslt.XSLNode.processChildren(XSLNode.java:480)
     at oracle.xml.xslt.XSLTemplate.processAction(XSLTemplate.java:205)
     at oracle.xml.xslt.XSLStylesheet.execute(XSLStylesheet.java:581)
     at oracle.xml.xslt.XSLStylesheet.execute(XSLStylesheet.java:548)
     at oracle.xml.xslt.XSLProcessor.processXSL(XSLProcessor.java:333)
     at oracle.xml.xslt.XSLProcessor.processXSL(XSLProcessor.java:181)
     at oracle.xml.xslt.XSLProcessor.processXSL(XSLProcessor.java:218)
     at oracle.xml.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:121)
     at oracle.xml.async.XSLTransformer.run(XSLTransformer.java:136)
     at java.lang.Thread.run(Thread.java:595)
No line number in my XSLT is written, but I have isolated it to the above code in the XSL file. This is some bug in the Oracle implementation, because when I run it against Saxon9, it produces output without complaint. Please help me with a work around for detecting the dollar sign and removing it for the output or can I find an oracle xslt patched package.
Thanks a lot. - astewart / [email protected]
Message was edited by:
astewart
Message was edited by:
astewart
Message was edited by:
astewart

Hi,
You have posted to the wrong forum. Try posting to one of the XML forums such as:
General XML
Ron

Similar Messages

How can I stop the oracle XSLT processor from inserting extra whitespace in HTML?

How can I stop the oracle XSLT processor from inserting extra whitespace in HTML?

Use <xsl:output mode="html" indent="no"/> as a top-level element child of your <xsl:stylesheet> element.

Oracle XSLT Processor

Hi
I am using oracle XSLT processor. There is a need to print current year in HTMl page.
I have used year() function in xalan org.apache.xalan.lib.ExsltDatetime class to print curreent year in XSLT file. But it is not displaying anything
Please anybody can help on this?
My xslt looks like this
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:cal="http://www.oracle.com/XSL/Transform/java/org.apache.xalan.lib.ExsltDatetime"
version="1.0">
<xsl:template match="/">
Copyright © <xsl:value-of select="cal:year()">
</xsl:template>
</xsl:stylesheet>

So I suppose you're using this from Java ?
What's the version of the processor?

Need to use Xalan in place of Oracle XSLT processor

We are working with Oracle BPEL 10.1.3.3. We have a requirement to use Xalan as the XSLT processor to preserve existing investment into transformation maps built using Contivo (which is certified to work with Xalan).
That said, we are having some trouble getting the Xalan processor to kick in going the java:exec route. For some reason, we end up with Oracle's XSLT processor in spite of asking for the Xalan implementation.
TransformerFactory tFactory = new org.apache.xalan.processor.TransformerFactoryImpl();
Transformer transformer = tFactory.newTransformer(new StreamSource(xslInURI));
System.out.println(tFactory.toString()+transformer.toString());
Strangely enough, the above snippet prints:
[email protected]Transformer@e39f6b
Wondering if anybody else has used Xalan successfully in conjunction with 10.1.3.3 bits. Appreciate your help.

please copy and paste the following in your xpath-functions.xml file
<function id="processXSLT" arity="2">
<classname>com.collaxa.cube.xml.xpath.functions.xml.GetElementFromXSLTFunction</classname>
<property id="namespace-uri">
<value>http://schemas.oracle.com/xpath/extension/xalan/xslt</value>
</property>
<property id="namespace-prefix">
<value>xalan</value>
</property>
</function>
This function would try to find the default transformer factory using
TransformerFactory.newInstance()
so you might need to place the xalan transformer factory properties file in the beginning of your classpath (server.xml ) or pass it as jvm system property like below:
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl

Bug in Oracle XSchema Processor for Java v1 (recently released)

Running the sample file is giving the following error. Is this a bug
Thanks
Exception in thread "main" java.lang.NoSuchMethodError
at oracle.xml.parser.schema.XSDBuilder.initParser(XSDBuilder.java:260)
at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:179)
at XSDSetSchema.main(XSDSetSchema.java:24)
null

ah, yes. the 1k limit again. fantastic...
code (note: this is hardcoded and terribly unpolished...but it works...):
import javax.security.auth.login.Configuration;
import javax.security.auth.login.AppConfigurationEntry;
import java.util.ArrayList;
import java.util.StringTokenizer;
import java.util.HashMap;
import java.util.Map;
public class CITestAuthenticationConfiguration extends Configuration {
private static ArrayList appConfigurationList = new ArrayList();
public CITestAuthenticationConfiguration(){}
public AppConfigurationEntry[] getAppConfigurationEntry(String applicationName){
Map map = new HashMap();
AppConfigurationEntry ace = new AppConfigurationEntry(
"CITestLoginModule",
AppConfigurationEntry.LoginModuleControlFlag.REQUIRED,
map
AppConfigurationEntry[] aceArray = new AppConfigurationEntry[1];
aceArray[0] = ace;
return aceArray;
public void refresh()
// Right now this is a load once scheme and we will not implement the
// refresh method
public static boolean addAppConfigurationEntry ( String flag, String module, String options )
// REMOVED FOR BREV[i]Long postings are being truncated to ~1 kB at this time.

XSL-FO Stylesheets (Oracle XSLT processor via command line)

How does one go about editing BIP XSL-FO stylesheets converted from the MSWord plug in by using external tools?
The converted files have many, many calls to Oracle functions that are unrecognized by the editing tools.
We are using Stylus Studio and are getting errors on functions calls such as:
<xsl:variable name="_XDOXSLTCTX" select="xdoxslt:set_xslt_locale($_XDOCTX, $_XDOLOCALE, $_XDOTIMEZONE, $_XDOCALENDAR, concat($_XDODFOVERRIDE,' ',$_XDOCURMASKS,' ',$_XDONFSEPARATORS))"/>
This is but one example of course. There are many calls in each template and they are quite varied.
Is there a way to "register" these with the tools so that they can call them (via tnsnames?). Even to having them ignored would be preferable to having the previewer completely fail.
Scott

Hi Scott.
there's a JavaAPI which you can use. So it's not really a command line interface, but perhaps it can fullfill you requirements.
Regards
Rainer

How can I make my XSLT processor accept html code ?

In my applications the Oracle xslt processor wont accept simple HTML tags within an XML source while transforming the source into HTML. Both processors either will throw parser exceptions or ignore the HTML code in the XML source completely, though output-escaping is explicitly enabled.
In detail, I want to transform an XML source like this...
<element>
Hello, this is a <b>XML</b> text source mingled with html<sup>TM</sup>
</element>
... with an XSL Stylesheet like this...
<xsl:stylesheet>
<xsl:output method=html cdata-sections=element/>
<xsl:template match=element>
<html>
<body>
<xsl:value-of select=. output-escaping=yes/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
... which should result in a HTML code like this ...
<html>
<body>
Hello, this is a <b>XML</b> text source mingled with html<sup>TM</sup>
</body>
</html>
The result, however, is always like this:
<html>
<body>
Hello, this is a XML text source mingled with htmlTM
</body>
</html>
This means that the additional HTML tags inside the XML source have been completely ignored by the XSLT processor though I enabled the output-escaping.
If anybody should think now that mingling HTML with XML text is stupid because I could also format the result with the XSL Stylesheet itself, he might be right, of course, but: I cant avoid this because in my application the XML source results from a users web form entry. The user working with the form must be able to decide whether he wants to include HTML in his text or not. In any case, any HTML code he enters should just be transported WITHOUT ANY CHANGES to the resulting HTML page, not omitted without comments! It seems quite simple to me, but the XSLT processor doesnt want to agree with me in this point :-(
So, once again in brief: Is there any possibility to tell my XSLT processor not to parse, transform or manipulate HTML tags, but to transport them unchanged to the output ?
After weeks of research any helping sign would be a great relief...
Many thanks in advance.

I don't understand the answer, can you please expand. I am trying to do a similar thing by creating an output buffer,
assemble a mix of text and html tags and then output this buffer later. All of the html tags are skipped or re-escaped in the final html:
In this example I want to print the IPRCROP, then add an html break (<br>).
Example 1. Use xsl:text with escape = yes
<xsl:variable name="buffy">
<xsl:for-each select="documents/document">
<xsl:value-of select="IPRCROP"/>
<xsl:text disable-output-escaping="yes"><br></br></xsl:text>
</xsl:for-each>
</xsl:variable>
<xsl:value-of select="$buffy"/>
In this case the <br> and </br> end up re-escaped in the output html as #60 etc. so they appear literally as
ALFALFA <br> BARLEY <br>
and in source as: ALFALFA< br > < /br >BARLEY
Example 2, try as pure text, it just skips the <br></br> altogether
<xsl:variable name="buffy">
<xsl:for-each select="documents/document">
<xsl:value-of select="IPRCROP"/>
<xsl:text><br></br></xsl:text>
</xsl:for-each>
</xsl:variable>
<xsl:value-of select="$buffy"/>
output = ALFALFABARLEY

Oracle XSLT Transformation not preserving space in text element

If we have a BPEL process which is calling a XSLT transformation contains the code similar as below:
for Populating an element with white space only
<tns:TargetField>
<xsl:text disable-output-escaping="yes"> </xsl:text> 
</tns: TargetField>
Our expected result / output would be:
<tns:TargetField> </tns: TargetField> 
But, we get:
<tns:TargetField/>
Oracle XSLT is ignoring the white space even if we try with preserve space in XSD, or in XSLT this is not producing the expected output.
This looks a BUG with Oracle XSLT Transformation .
For a workaround solution we can use below XSLT snippet:
*<tns:TargetField>*
*<xsl:value-of select="string(' ')"/> *
*</tns:TargetField>*
This is returning Output:
*<tns:TargetField> </tns:TargetField> *
Any other work around do you find?
Edited by: panks on Jul 29, 2011 12:37 PM

The workaround only works with one white space, if one put more white spaces, it do not work.
<tns:TargetField>
<xsl:value-of select="string(' ')"/> 
</tns:TargetField>
This is returning Output:
<tns:TargetField> </tns:TargetField> 
Edited by: user10697506 on Aug 10, 2011 3:27 PM

XSLT processor help

Hi ,
my expected out put is ..
<AA>200</AA>
<AA>150</AA>
<AA>300</AA>
<BB>650</BB>
<AA>50</AA>
<BB>50</BB>
my xsl logic:
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
<xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
<xsl:template match="/">
<xsl:apply-templates select=".//LIST_G_REP_TRX_DETAIL_INFO"/>
</xsl:template>
<xsl:template match="LIST_G_REP_TRX_DETAIL_INFO">
<xsl:variable name="t1" as="element(AA)*">
    <xsl:for-each-group select="G_REP_TRX_DETAIL_INFO[C_TAX_REPORTING_NAME = '01']" group-by="concat(C_BILLING_TP_TAX_REG_NUM,C_TAX_REPORTING_NAME)">
      <AA><xsl:value-of select="sum(current-group()/C_FUNCTIONAL_TOTAL)"/></AA>
    </xsl:for-each-group>
</xsl:variable>
<xsl:for-each-group select="$t1" group-by="(position() - 1) idiv 3">
    <xsl:copy-of select="current-group()"/>
    <BB><xsl:value-of select="sum(current-group())"/></BB>
</xsl:for-each-group>
</xsl:template>
</xsl:stylesheet>unfortunatly when i use Oracle XSLT processor iam getting like below
<AA>200</AA>
<AA>150</AA>
<AA>300</AA>
<AA>50</AA>
<BB>2.001503005E10</BB>
But with the same XSL i am getting my expected o/p with both Saxon 9.2 and AltvovaXML tools.
may i know how i can my o.p with Oracle XSLT processor
Thanks
kumar

I was facing java heap space error with one of my large report. If you are running oc4j, make sure you allocate enough heap size for JVM to process reports. In my case heap size was 512MB. After changing it to 2GB and enabling AggresiveHeap the error went away and performance improvement was amazing.
This link has more details on how to set these JVM commandline options:
http://docs.oracle.com/cd/B10464_05/core.904/b10379/optj2ee.htm#i1006219

Oracle XSL Processor Bug

Description
We are currently using the XMLData class (oracle.jbo.html.databeans.XmlData)
We submit an XML document having some empty XML elements. We apply an XSL Transformation but we receive a non-conform XML Document in output!!
The problem happens when one of the XML elements is empty. Oracle XSL Processor doesn't close my open tag <textarea> with a </textarea>
XSL template:
<xsl:template name="LigneAvecDetail">
<xsl:param name="value"/>
<xsl:param name="name"/>
<xsl:param name="checkboxtag"/>
<xsl:param name="detail"/>
<tr>
<td xsl:use-attribute-sets='LigneDetailStyle'>
<xsl:choose>
<xsl:when test="string-length($value) < 1">
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
</input>
</xsl:when>
<xsl:otherwise>
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
<xsl:attribute name="checked">TRUE</xsl:attribute>
</input>
</xsl:otherwise>
</xsl:choose>
<xsl:value-of select="$checkboxtag"/>
<textarea rows="2" name="S1" cols="20"><xsl:value-of select="$detail"/></textarea>
</td>
<xsl:call-template name="GroupeRadioBouton">
<xsl:with-param name="value" select="$value"/>
<xsl:with-param name="name" select="$name"/>
</xsl:call-template>
</tr>
</xsl:template>
Here my XML document:
<Results>
<DRIOQ_BilanMe_view>
<NoSommaire>1</NoSommaire>
<AutreInfo>Autre information pertinente au dossier</AutreInfo>
<IdIntervenant>1</IdIntervenant>
<PoumonsRx></PoumonsRx>
<PoumonsTdm></PoumonsTdm>
<PoumonsAutre>B</PoumonsAutre>
<PoumonsAutreDetail>Le commentaire de l'autre detail du poumon</PoumonsAutreDetail>
<OsScint></OsScint>
<OsRx>I</OsRx>
<OsRxDetail>Le commentaire du detail RX de l'os</OsRxDetail>
<OsTdm></OsTdm>
<OsTdmDetail></OsTdmDetail>
<OsAutre></OsAutre>
<OsAutreDetail></OsAutreDetail>
<FoieEnzymes>B</FoieEnzymes>
<FoieEchographie>M</FoieEchographie>
<FoieTdm>I</FoieTdm>
<FoieAutre>B</FoieAutre>
<FoieAutreDetail>Le commentaire de l'autre detail du foie</FoieAutreDetail>
</DRIOQ_BilanMe_view>
</Results>
Thanks!

This is a known bug in the HTML Output method of 2.0.2.6 which is incorrectly
outputting elements like:
<script/>
and
<textarea/>
as
<script> instead of <script></script>
and
<textarea> instead of <textarea></textarea>
This will be fixed in 2.0.2.7. The workaround
is to have some content defaulted into the <textarea> so that it's not an empty element.

BUG: Oracle Schema Processor does not work in Servlets

We found a bug with Oracle's Schema Processor. It does not work in Servlets.
When we try to validate a XML document in a Servlet it does not work, but we can execute the same code in a stand alone application and it works.
The following is the code we are using:
try {
File f =new File(filename);
FileReader r = new FileReader(f);
DOMParser dp = new DOMParser();
URL url = createURL (filename);
dp.setValidationMode(false);
dp.setSchemaValidationMode(true);
dp.setPreserveWhitespace(true);
dp.parse(url);
System.out.println("it is parsed");
} catch(Exception e){System.out.println("there is Error"+e.getMessage());}
null

I don't think this is related to Servlets per se.
Check that the Schema processor classes used by the servlet container, and your application are the same.
Java does not have proper versioning of classes, I have seen many applications collapse. People compiled their code on developer machines, where it worked fine, but when moved to a production machine they failed because the production machine had a different version of classes. Usually the name of the class doesn't change, but either a method or a variable is missing in several classes. VM doesn't complain but simply crashes.
In your Schema Processor classes that are used by the servlet engine might be different from the one that the app uses. Do a search on the file system to see how many copy of the same class bundle (zip, jar) you have on the system.

XSLT Processor Bug? format-number() on large numbers

For numbers 100,000,000.00 and higher, I'm getting extra digits and rounding errors.
How can I use some custom Java code in the XSL stylesheet so the correct value is displayed (i.e. w/o rounding)? I'm getting a value of 100000000.00 and I need to insert the commas. Sometimes the correct value is displayed, other times, additional numbers are appended and the amount is rounded.

The XSLT processor uses java.text.DecimalFormat under the covers as the XSLT 1.0 specification suggests. I would imagine any problems with format-number() actually boil down to problems with java.text.DecimalFormat.
You can use Java Extension functions to perform custom Java in your stylesheet.
See the file .\extfunc.html in the root directory of the XML Parser for Java V2
distribution.

Problem with Enable scalable feature of XSLT processor

Hi Gurus,
I'm using BI Publisher 10.1.3.4.1. I've having a report, when running in a specific sequence (i.e. after running with XML dataset 1 then dataset 2), will yield an error. Here is the log I got in the xdo.log.
[061411_110902953][][EXCEPTION] java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
     at oracle.apps.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:91)
     at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:256)
     at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:81)
     at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:678)
     at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
     at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
     at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
     at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:86)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
     at oracle.xdo.parser.v2.FilePageManager.pageLength(FilePageManager.java:242)
     at oracle.xdo.comp.CXMLStream.ensureReadCapacity(CXMLStream.java:1543)
Then I tried turning off "Enable scalable feature of XSLT processor" (under the FO Processing, default is ON) This error cannot be reproduced again (i.e. my report can run in whatever sequence without an error).
Would anyone explain to me what actually is the difference between setting the "Enable scalable feature of XSLT processor" to true and false. I'll be running the same report template with thousands of pages in some cases and I'm anxious whether turning OFF the "scalable feature" will make the performance suffer.
Thanks in advance,
Jonathan

Are you running Enterprise Edition? I believe flashback database is only available with Enterprise.

XDK, XSLT Processor, Add JARs statically

Hello,
while using XDK's Oracle XSLT Extensions I'm facing an issue with class visibility after adding it via "loadjava" tool.
I'm getting the following exception during transformation:
     oracle.xml.xpath.XPathException: Extension function error: Class not found ...
     oracle.xml.xslt.XSLStylesheet.flushErrors(XSLStylesheet.java:2495)
The docs say the following: (Using the XSLT Processor for Java)
"Note: The XSL class loader only knows about statically added JARs and paths in the CLASSPATH and those specified by wrapper.classpath. Files added dynamically are not visible to XSLT processor."
So it's rather clear that loadjava adds classes dynamically. That explains the error message.
The question however is: how to add classes statically?
Thanks a lot in advance for you help!

Trying some stuff at home now until we can call each other.
Java version is a bit old, isn't it...?
On my DB version at home (12.1.0.1), server side, it mentions:
[oracle@localhost ~]$ java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.11) (rhel-1.61.1.11.11.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
Will try to figure out what the local XDK stuff says.
My $CLASSPATH is not set. The Oracle Java JDK version mentions:
[oracle@localhost bin]$ $ORACLE_HOME/jdk/bin/java -version
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)
After setting the environment on server database side, I get...
[oracle@localhost oracle.xdk_11.1.0]$ oraxsl -v
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/xml/parser/v2/oraxsl
Caused by: java.lang.ClassNotFoundException: oracle.xml.parser.v2.oraxsl
    at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: oracle.xml.parser.v2.oraxsl. Program will exit.
[oracle@localhost oracle.xdk_11.1.0]$ echo $PATH
/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oracle/bin:/u01/app/oracle/product/12.1.0/dbhome_1/bin
[oracle@localhost oracle.xdk_11.1.0]$ echo $LD_LIBRARY_PATH
/u01/app/oracle/product/12.1.0/dbhome_1/lib
[oracle@localhost oracle.xdk_11.1.0]$ echo $JAVA_HOME
/u01/app/oracle/product/12.1.0/dbhome_1/jdk/bin
[oracle@localhost oracle.xdk_11.1.0]$ echo $ORACLE_HOME
/u01/app/oracle/product/12.1.0/dbhome_1
[oracle@localhost oracle.xdk_11.1.0]$ echo $CLASSPATH
/u01/app/oracle/product/12.1.0/dbhome_1/lib/xmlparserv2.jar:/u01/app/oracle/product/12.1.0/dbhome_1/lib/xsu12.jar:/u01/app/oracle/product/12.1.0/dbhome_1/lib/xml.jar
[oracle@localhost oracle.xdk_11.1.0]$ oraxsl -v
Release version: Oracle XML Developers Kit 12.1.0.1.0 - Production
oraxsl: Number of arguments specified (1) is illegal
usage: oraxsl options* source? stylesheet? result?
            -w                          Show warnings
            -e <error log>              A file to write errors to
            -l <xml file list>          List of files to transform
            -d <directory>              Directory with files to transform
            -x <source extension>       Extensions to exclude
            -i <source extension>       Extensions to include
            -s <stylesheet>             Stylesheet to use
            -r <result extension>       Extension to use for results
            -o <result directory>       Directory to place results
            -p <param list>             List of Params
            -t <# of threads>           Number of threads to use
            -v                          Verbose mode
            -debug                      Debug mode
            -m <version #>              XSLT Version, 1 or 2
Please refer to the readme file for more information on the above options
[oracle@localhost oracle.xdk_11.1.0]$ java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.11) (rhel-1.61.1.11.11.el6_4-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
[oracle@localhost oracle.xdk_11.1.0]$ export PATH=$ORACLE_HOME/jdk/bin:$PATH
[oracle@localhost oracle.xdk_11.1.0]$ java -version
java version "1.6.0_37"
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

Reporting bugs in oracle products

Is there a webpage whre I can report bugs in oracle
products.
Thanks,
Artur...

The only place I'm aware of short of calling Oracle is metalink.oracle.com but you have to have paid for Oracle support to access
the web site. From there you can file a TAR(Technical Assistance Request) and a support person will research your problem and
either find an existing fix or classify it as a new bug.

FIXED: BUG in Oracle XSLT processor

Similar Messages

Maybe you are looking for