Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
recover from document not found exceptions

recover from document not found exceptions

2007-06-29       - By Henry Zongaro
Reply:     1     2     3     4  

Hi, Adrian.

news <news@(protected)> wrote on 2007-06-18 11:36:18 AM:
> The spec says: "If there is an error retrieving the resource, then the
> XSLT processor may signal an error; if it does not signal an error, it
> must recover by returning an empty node-set."
> [http://www.w3.org/TR/xslt#function-document]
>
> I though that there is some "feature" or "property" that I can set in
> order to get that recovery.

There is no such feature today.  You can open a feature request in
Jira.[1]  Of course, all the contributors on this project are stretched
pretty thinly; if you were able to contribute the implementation for such
a feature or property, that would be greatly appreciated!

Thanks,

Henry
[1] http://issues.apache.org/jira/secure/CreateIssue!default.jspa
------------------------------------------------------------------
Henry Zongaro      XSLT Processors Development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)



<br><tt><font size=2>Hi, Adrian.</font></tt>
<br>
<br><tt><font size=2>news &lt;news@(protected)&gt; wrote on 2007-06-18
11:36:18 AM:<br>
&gt; The spec says: &quot;If there is an error retrieving the resource,
then the <br>
&gt; XSLT processor may signal an error; if it does not signal an error,
it <br>
&gt; must recover by returning an empty node-set.&quot; <br>
&gt; [http://www.w3.org/TR/xslt#function-document]<br>
&gt; <br>
&gt; I though that there is some &quot;feature&quot; or &quot;property&quot;
that I can set in <br>
&gt; order to get that recovery.<br>
</font></tt>
<br><tt><font size=2>There is no such feature today. &nbsp;You can open
a feature request in Jira.[1] &nbsp;Of course, all the contributors on
this project are stretched pretty thinly; if you were able to contribute
the implementation for such a feature or property, that would be greatly
appreciated!</font></tt>
<br><font size=2 face="sans-serif"><br>
Thanks,<br>
<br>
Henry</font>
<br><font size=2 face="sans-serif">[1] http://issues.apache.org/jira/secure
/CreateIssue!default.jspa<br>
------------------------------------------------------------------<br>
Henry Zongaro &nbsp; &nbsp; &nbsp;XSLT Processors Development<br>
IBM SWS Toronto Lab &nbsp; T/L 969-6044; &nbsp;Phone +1 905 413-6044<br>
mailto:zongaro@(protected)</font>
<br>
<br>