Well, nothing expected with deocument(.)
I may pass a DOM document as a parameter to this XSL, but when I have no document, then I had a lot of exceptions. So, initializing my repository with document(.) was a way to have something non-null. I expected document(.) was the XSL itself, and as it was non-null, I could use $repository/data/param[@id='foo']/@value even if repository do not contains data node....

Christophe

Le 26/09/2011 21:38, Michael Kay a écrit :
document(.) is a strange thing to put in a global variable. Presumably "." (the context item) is a document node, so document(.) will extract the string value of the document node, which is rather unlikely to be a valid URI. It's more likely to be a string containing a lot of whitespace, as the error message suggests. What did you expect document(.) to evaluate to?

Michael Kay
Saxonica

On 26/09/2011 13:32, Christophe Marchand wrote:
Hi,

I have this warning message, but I have no idea of what to look for to solve it.

Recoverable error on line 9
  FODC0002: Exception thrown by URIResolver: Invalid relative URI
  {\n%20%20%20\n%20%20%20%20%20%2...}: Illegal character in path at index 0:
%20%20%20
%20%20%20%20%20%20
%20%20%20%20%20%20
%20%20%20

May this could be that :
<?xml version="1.1" encoding="iso-8859-1"?>
<!DOCTYPE xsl:stylesheet [
<!ENTITY nbsp "&#160;">
<!ENTITY deg "&#176;">
<!ENTITY eacute "&#233;">
]>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:n="http://xemelios.org/schemas/bourses" version="2.0" exclude-result-prefixes="xsl n">
    <xsl:output method="xhtml" encoding="ISO-8859-1" indent="yes"/>
    <xsl:param name="repository" select="document(.)"/>

    <xsl:template match="*"> </xsl:template>


I use a custom URI Resolver.


Any idea ?
Christophe




------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1


_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/saxon-help 

------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________ saxon-help mailing list archived at http://saxon.markmail.org/ saxon-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/saxon-help