document( ' ')

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 ...

document( ' ')

document( ' ')

2006-12-27 - By Christine Li

Reply: 1 2 3 4 5

>which leads me to believe that Xalan is actually using the system id as a
>URI to load a resource. It seems kind of broken to require that any
>stylesheet that references itself be reloadable and that it actually
would
>reload it and reparse it.

You are right about this. For document function, the processor will reload
the document using the system id as a URI

Christine Li
XSLT Development
IBM Toronto Lab
Tel: (905)413-2601
Email: jycli@(protected)

dnfoote <dnfoote@(protected)>
27/12/2006 04:47 AM

To
xalan-j-users@(protected)
cc

Subject
Re: document('')

Mike,

Thanks for the quick response. What you are saying makes sense, but I was
hoping to use a dynamically generated stylesheet as an easy way to inject
some lookup info into the result. If Xalan was just using the system id
as
a unique identifier then I would be okay. But instead if I change the
code
to the following:

Source xsl = new StreamSource(new FileInputStream("media.xsl"));
xsl.setSystemId("MyXSL");
Transformer transformer = tFactory.newTransformer(xsl);

I get :

file:///C:/.../MyXSL; Line #34; Column #78; Can not load requested doc:
C:\...\MyXSL (The system cannot find the file specified)

which leads me to believe that Xalan is actually using the system id as a
URI to load a resource. It seems kind of broken to require that any
stylesheet that references itself be reloadable and that it actually would
reload it and reparse it.

I even thought, well, a StreamSource is not re-usable, so what if I use a
DOMSource. Same story, Xalan tries to reload the original stylesheet
using
the system id. This is really bumming me out :)

Mike Brown-3 wrote:
>
> dnfoote wrote:
>> I have done some testing with a style sheet that uses the document
>> function
>> with an empty string as its only argument. The document('') call
errors
>> out
>> complaining 'SystemId Unknown' if I invoke newTransformer as follows:
>>
>> Transformer transformer = tFactory.newTransformer(new StreamSource(new
>> FileInputStream("media.xsl")));
>>
>> instead of:
>>
>> Transformer transformer = tFactory.newTransformer(new
>> StreamSource("media.xsl"));
>
> Because when you constructed the StreamSource from a FileInputStream,
you
> didn't set the StreamSource's system ID, which is a URI to use as the
> document's ID and against which your processor's URIResolver will
resolve
> relative references like the '' (empty string) in that document() call.
>
> See the StreamSource API docs and set the system ID to a full URI like
> "file:///C:/path/to/media.xsl".
>
>> Is it true that Xalan cannot reference the stylesheet document tree
>> unless
>> it got the document from a URI in the first place?
>
> No, it's not true.
>
> However, every document has a URI / system ID, regardless of how the
> document
> was obtained, transmitted, or referred to in APIs. Maybe it represents
> where
> you got the doc from, maybe not. If you didn't set one, then one was
> assigned
> to it -- probably not very intelligently. If you did set one, but it
> wasn't a
> full URI, then the results are unpredictable and
implementation-dependent
> and
> sometimes wrong, as you've observed with your test stylesheet.
>
>> Has anyone else seen this behavior? Is it correct?
>
> First time I've seen it.
>
> Even though you weren't really setting the base URI / system ID
correctly,
> your stylesheet shouldn't have failed. I'd consider it a bug in Xalan,
> but
> others may disagree.
>

--
View this message in context:
http://www.nabble.com/document%28%27%27%29-tf2884411.html#a8060924
Sent from the Xalan - J - Users mailing list archive at Nabble.com.

 ><tt>which leads
me to believe that Xalan is actually using the system id as a 
>URI to load a resource.  It seems kind of broken to require that
any 
>stylesheet that references itself be reloadable and that it actually
would 
>reload it and reparse it.</tt>
 
 <tt>You are right about this. For document function, the
processor will reload the document using the system id as a URI</tt>
 
 Christine Li 
XSLT Development 
IBM Toronto Lab 
Tel: (905)413-2601 
Email: jycli@(protected)
 
 
 
<table width=100%>
<tr valign=top>
<td width=40%>dnfoote <dnfoote@(protected)
>

27/12/2006 04:47 AM
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right>To</div>
<td>xalan-j-users@(protected)
<tr valign=top>
<td>
<div align=right>cc</div>
<td>
<tr valign=top>
<td>
<div align=right>Subject</div>
<td>Re: document('')</table>
 
<table>
<tr valign=top>
<td>
<td></table>
 </table>
 
 
 <tt> 
Mike, 
 
Thanks for the quick response.  What you are saying makes sense, but
I was 
hoping to use a dynamically generated stylesheet as an easy way to inject 
some lookup info into the result.  If Xalan was just using the system
id as 
a unique identifier then I would be okay.  But instead if I change
the code 
to the following: 
 
Source xsl = new StreamSource(new FileInputStream("media.xsl")); 
xsl.setSystemId("MyXSL"); 
Transformer transformer = tFactory.newTransformer(xsl); 
 
I get : 
 
file:///C:/.../MyXSL; Line #34; Column #78; Can not load requested doc: 
C:\...\MyXSL (The system cannot find the file specified) 
 
which leads me to believe that Xalan is actually using the system id as
a 
URI to load a resource.  It seems kind of broken to require that any 
stylesheet that references itself be reloadable and that it actually would 
reload it and reparse it. 
 
I even thought, well, a StreamSource is not re-usable, so what if I use
a 
DOMSource.  Same story, Xalan tries to reload the original stylesheet
using 
the system id.  This is really bumming me out :) 
 
 
 
Mike Brown-3 wrote: 
> 
> dnfoote wrote: 
>> I have done some testing with a style sheet that uses the document 
>> function 
>> with an empty string as its only argument.  The document('')
call errors 
>> out 
>> complaining 'SystemId Unknown' if I invoke newTransformer as follows:
 
>> 
>> Transformer transformer = tFactory.newTransformer(new StreamSource(new
 
>> FileInputStream("media.xsl"))); 
>> 
>> instead of: 
>> 
>> Transformer transformer = tFactory.newTransformer(new 
>> StreamSource("media.xsl")); 
> 
> Because when you constructed the StreamSource from a FileInputStream,
you 
> didn't set the StreamSource's system ID, which is a URI to use as
the 
> document's ID and against which your processor's URIResolver will
resolve 
> relative references like the '' (empty string) in that document()
call. 
> 
> See the StreamSource API docs and set the system ID to a full URI
like 
> "file:///C:/path/to/media.xsl". 
> 
>> Is it true that Xalan cannot reference the stylesheet document
tree 
>> unless 
>> it got the document from a URI in the first place? 
> 
> No, it's not true. 
> 
> However, every document has a URI / system ID, regardless of how the 
> document 
> was obtained, transmitted, or referred to in APIs. Maybe it represents 
> where 
> you got the doc from, maybe not. If you didn't set one, then one was 
> assigned 
> to it -- probably not very intelligently.  If you did set one,
but it 
> wasn't a 
> full URI, then the results are unpredictable and implementation-dependent
 
> and 
> sometimes wrong, as you've observed with your test stylesheet. 
> 
>> Has anyone else seen this behavior?  Is it correct? 
> 
> First time I've seen it. 
> 
> Even though you weren't really setting the base URI / system ID correctly,
 
> your stylesheet shouldn't have failed.  I'd consider it a bug
in Xalan, 
> but 
> others may disagree. 
> 
 
-- 
View this message in context: http://www.nabble.com/document%28%27%27%29
-tf2884411.html#a8060924 
Sent from the Xalan - J - Users mailing list archive at Nabble.com. 
 
</tt>