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.
setSystemId not recursive for included stylesheets?

setSystemId not recursive for included stylesheets?

2003-02-06       - By Rhodes, Phillip C.
Reply:     1     2     3     4  

I am doing a transformation in jaxp, underlying it is xalan 2.4.1

I have several stylesheets, all have includes that are relative to a base
(e.g. /usr01/h3/rhodepc/d/jrun-16981/default-app/)  There is an xsl
subdirectory here.

All my includes in my stylesheets begin with the path "xsl/"

I have a master stylesheet, that will include one stylesheet, which in turn
includes another stylesheet, and so on...

I set the systemId on the first stylesheet, so that when it does an include
of the first stylesheet, the stylesheet is found.

However, this second stylesheet does an include (also relative).  This
include is resolved relative to the second stylesheet's location, not the
original location of the stylesheet, hence the document root moves from
stylesheet to stylesheet.

It seems that setSystemId is not used recursively for resolving the
stylesheets that are included...

Any help and guidance would be appreciated!

Here is more detail:
java.io.FileNotFoundException:
/usr01/h3/rhodepc/d/jrun-16981/default-app/xsl/purchasing/xsl/util/jsp/xmlui
.xsl (No such file or directory)

The file is located at
/usr01/h3/rhodepc/d/jrun-16981/default-app/xsl/util/jsp/xmlui.xsl

The include was (in the 2nd included xsl)

<xsl:include href="xsl/util/jsp/xmlui.xsl"/>

I had set the systemid on the first stylesheet to point to
"/usr01/h3/rhodepc/d/jrun-16981/default-app/"
So the first stylesheet is found.
The master stylesheet (the first one called) is located at
/usr01/h3/rhodepc/d/jrun-16981/default-app/xsl/purchasing/ebiz

Thanks very much.  Fighting this all day!



Phillip Rhodes