[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] SAXON 8 - Error at element constructor


Subject: RE: [xsl] SAXON 8 - Error at element constructor
From: "Michael Kay" <mike@xxxxxxxxxxxx>
Date: Mon, 24 Jan 2005 23:24:36 -0000

The error XT1170 comes from a call on the unparsed-text() function. The text

"2005-01-24 16:40:30,437 52219 WARN  no.docstream.formstream.GetForm"

is the message associated with an exception from the java.net.URL class -
it's possible this is actually the URL you supplied as the argument to the
function.

I can't see you you could get this error from a stylesheet that you haven't
changed from XSLT 1.0.

I hope this helps you identify where the error originated.

Michael Kay
http://www.saxonica.com/
 

> -----Original Message-----
> From: Tommy Skarateppen [mailto:ts@xxxxxxxxxxxx] 
> Sent: 24 January 2005 16:17
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: [xsl] SAXON 8 - Error at element constructor
> 
> I'm getting this error when I transform using SAXON 8:
> 
> Error at element constructor <td> on line 572 of :
>   XT1170: Cannot resolve relative URI: no protocol: 
> 2005-01-24 16:40:30,437 52219 WARN  
> no.docstream.formstream.GetForm  Unable
> to perform XSL transformationnet.sf.saxon.xpath.DynamicError: 
> Cannot resolve
> relative URI
> 
> I've used the same xsl in my application for two years now, 
> and never had
> problems with the transformation and I haven't changed 
> anything. I'm going
> to add some xsl 2.0 features in my stylesheet, so I had to 
> use the SAXON 8.
> And now I get this error from the Tomcat log.
> 
> This is what I have on line 572 in my xsl:
> 
> <td valign="top">
> 
> Just a common html-tag with a common attribute.
> 
> Does anyone have an idea what causing this error?
> 
> -Tommy


Current Thread
Keywords