Re: [xsl] Referring to stylesheet itself, possible in XSLT 1.0, but how in XSLT 2.0?

Subject: Re: [xsl] Referring to stylesheet itself, possible in XSLT 1.0, but how in XSLT 2.0?
From: George Cristian Bina <george@xxxxxxxxxxxxx>
Date: Tue, 17 Oct 2006 17:47:53 +0300
Hmm, with the same example I get 2 errors reported in the Errors tab from the Results View, both with the message "Content is not allowed in prolog.".
If oXygen detects errors and cannot find a resource to place the error markers on then it reports them in an Errors tab in the Results view. That should appear automatically if you are in the oXygen XML perspective (Window -> Open Perspective -- Other... -- oXygen XML).


Best Regards,
George
---------------------------------------------------------------------
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com


Abel Braaksma wrote:
George Cristian Bina wrote:
Hi Abel,

Error reporting in Eclipse is done using error markers and these markers are set on the resource (file) that represents the system id reported on the error. In your case the error had a directory as system id and an error marker in Eclipse cannot be set for them, so oXygen reports them in the oXygen Results view. To have that visible either open the oXygen XML perspective and the Results view will appear automatically when you perform the transformation or go to Window -> Show View -- Other... and select oXygen -- Results.

Thanks George, for looking into this. Unfortunately, in the results view nothing happens either. The statusbar just states "Transformation failed". The results view is totally empty. The complete XSLT that I used is as follows:


<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; version="2.0" xml:base="../..">
<xsl:template match="/">
1) <xsl:value-of select="document-uri(document(''))"></xsl:value-of>
2) <xsl:value-of select="static-base-uri()"></xsl:value-of>
3) <xsl:value-of select="base-uri(.)"></xsl:value-of>
</xsl:template>
</xsl:stylesheet>



By the way, I have several other scenarios where I just receive a "Transformation failed" error. May this be because of this xml:base that I use very often throughout our xslt library?


Cheers,
-- Abel Braaksma

Current Thread