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.
URIResolvers base parameter with xsltc and cascaded imports

URIResolvers base parameter with xsltc and cascaded imports

2006-08-14       - By Yash Talwar
Reply:     1     2     3     4     5     6     7  

Hi  Holger,
I will look into this and reply back.

Thanks!


Yash Talwar




Holger Dehnhardt <dehnhardt@(protected)>
14/08/2006 09:28 AM
Please respond to
dehnhardt


To
xalan-j-users@(protected)
cc

Subject
Re: URIResolvers base parameter with xsltc and cascaded imports






Hello!
Sorry for asking again, but I really need some advice with the problem
described below.
Is anyone here who has written an URIResolver or can help in any way, or
should I ask on the developers list?

Thanks Holger

Am Montag, 24. Juli 2006 17:26 schrieb Holger Dehnhardt:
> Hello,
>
> I'm trying to write my own URIResolver to keep track of changes in
imported
> stylesheets when compiling the main stylesheet.
> Lets have this layout
>
> 1) http://localhost/main.xsl includes layouts/heads.xsl
> 2) heads.xsl includes ../helpers/someFunctions.xsl
> 3) http://localhost/main.xsl includes layouts/footers.xsl
>
> The interface method "resolve" in my uri-resolver is called three times
> with the following parameters:
>
> 1) href=layouts/heads.xsl base=http://localhost/main.xsl
> 2) href=../helpers/someFunctions.xsl base=http://localhost/main.xsl
> 3) href=layouts/footers.xsl base=http://localhost/main.xsl
>
> even if the file is included from another stylesheet like 2), the base
does
> not change.
> Storing the base is no solution,
> in 1) the base would be http://localhost/layouts/heads.xsl
> but in 2) it would be http://localhost/helpers/someFunctions.xsl
> and 3) would fail.
>
> Is this expected behaviour and if so, how can I manually keep track of
the
> base?
>
> Thanks Holger



<br><font size=2 face="sans-serif">Hi &nbsp;Holger,</font>
<br><font size=2 face="sans-serif">I will look into this and reply back.</font>
<br>
<br><font size=2 face="sans-serif">Thanks!</font>
<br>
<br><font size=2 face="sans-serif"><br>
Yash Talwar<br>
</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Holger Dehnhardt &lt;dehnhardt
@(protected)&gt;</b>
</font>
<p><font size=1 face="sans-serif">14/08/2006 09:28 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
dehnhardt</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">xalan-j-users@(protected)<
/font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">Re: URIResolvers base parameter
with xsltc and cascaded imports</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hello!<br>
Sorry for asking again, but I really need some advice with the problem
<br>
described below.<br>
Is anyone here who has written an URIResolver or can help in any way, or
<br>
should I ask on the developers list?<br>
<br>
Thanks Holger<br>
<br>
Am Montag, 24. Juli 2006 17:26 schrieb Holger Dehnhardt:<br>
&gt; Hello,<br>
&gt;<br>
&gt; I'm trying to write my own URIResolver to keep track of changes in
imported<br>
&gt; stylesheets when compiling the main stylesheet.<br>
&gt; Lets have this layout<br>
&gt;<br>
&gt; 1) http://localhost/main.xsl includes layouts/heads.xsl<br>
&gt; 2) heads.xsl includes ../helpers/someFunctions.xsl<br>
&gt; 3) http://localhost/main.xsl includes layouts/footers.xsl<br>
&gt;<br>
&gt; The interface method &quot;resolve&quot; in my uri-resolver is called
three times<br>
&gt; with the following parameters:<br>
&gt;<br>
&gt; 1) href=layouts/heads.xsl base=http://localhost/main.xsl<br>
&gt; 2) href=../helpers/someFunctions.xsl base=http://localhost/main.xsl<br>
&gt; 3) href=layouts/footers.xsl base=http://localhost/main.xsl<br>
&gt;<br>
&gt; even if the file is included from another stylesheet like 2), the
base does<br>
&gt; not change.<br>
&gt; Storing the base is no solution,<br>
&gt; in 1) the base would be http://localhost/layouts/heads.xsl<br>
&gt; but in 2) it would be http://localhost/helpers/someFunctions.xsl<br>
&gt; and 3) would fail.<br>
&gt;<br>
&gt; Is this expected behaviour and if so, how can I manually keep track
of the<br>
&gt; base?<br>
&gt;<br>
&gt; Thanks Holger<br>
</font></tt>
<br>