Oxygen XML Forum

vaisberga wrote:First autocomplition for XLT Template.

vaisberga wrote:Second the Error view. If I have error in included Template, than show in Problem that it has any Error in root xsl (index.xsl). sample:
/administration index.xsl line 114.
It say, that it error on the index.xsl, but error in other xsl. It's must:
/administration child.xsl line 114.

vaisberga wrote:The first sample:

...

Validations Error is:
Severity and Description Path Resource Location Creation Time Id
java.util.EmptyStackException proficio/proficio-stores index.xsl line 1 1159350739910 1072880

vaisberga wrote:I have a template-util.xls writet, but must xsl.The Error say nothing.

vaisberga wrote:The second sample:
I have two file:

...

I have Error in second file, but error message been:

Severity and Description Path Resource Location Creation Time Id
Falsche Anführungszeichen für Literal... Einfache Anführungszeichen wurden erwartet! proficio/proficio-stores index.xsl (but must template-util) line 7 1159350957168 1072885

vaisberga wrote:

vaisberga wrote:I have a Eclipse 3.2 and OxygenXML Plugin. This message I copy from Problems-View . If you selected the error in Problems -View of the Eclipse, then copy this error in other editor you must this see with id and other eleements. And I uses oXygen plugin (7.2). I can the screen for this send. Say youer e-mail and send this.

Alex.

sorin wrote:Yes, if the XSLT files are in the current workspace the errors are reported in the Problems view and they have the format which you posted. The problem is that for the XSL files which you posted I do not get java.util.EmptyStackException and org.apache.xml.utils.WrappedRuntimeException. Did you post all the included stylesheets ? Did you open the file with the errors with the Oxygen XSL Editor ? Do you see the icon in the editor title ?


Regards,
Sorin

sorin wrote:Run the following stylesheet with the oXygen plugin and tell us the output:

Code: Select all

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

    xmlns:xalan="http://xml.apache.org/xalan" xmlns:exslt="http://exslt.org/common" 

    exclude-result-prefixes="xalan exslt">

    <xsl:template match="/">

        <out>

            Version: <xsl:value-of select="system-property('xsl:version')" />

            Engine: <xsl:value-of select="exslt:node-set(xalan:checkEnvironment())//item[@key='version.xalan2x']"/>

            Java version: <xsl:value-of select="exslt:node-set(xalan:checkEnvironment())//item[@key='java.version']"/>

        </out>

    </xsl:template>

</xsl:stylesheet>

Regards,
Sorin

vaisberga wrote:

sorin wrote:Run the following stylesheet with the oXygen plugin and tell us the output:

Code: Select all

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

    xmlns:xalan="http://xml.apache.org/xalan" xmlns:exslt="http://exslt.org/common" 

    exclude-result-prefixes="xalan exslt">

    <xsl:template match="/">

        <out>

            Version: <xsl:value-of select="system-property('xsl:version')" />

            Engine: <xsl:value-of select="exslt:node-set(xalan:checkEnvironment())//item[@key='version.xalan2x']"/>

            Java version: <xsl:value-of select="exslt:node-set(xalan:checkEnvironment())//item[@key='java.version']"/>

        </out>

    </xsl:template>

</xsl:stylesheet>

Regards,
Sorin

I have it run an have a follow output:
<?xml version="1.0" encoding="UTF-8"?>
<out>
Version: 1.0
Engine: Xalan Java 2.7.0
Java version: 1.5.0_07
</out>

Regards,
Alexander Vaysberg
Adaptions GmbH

sorin wrote:What validation errors do you get with Saxon instead of Xalan for your stylesheets ? Did you post all the included files for the stylesheet which you validate ? Can you send us the files ?


Regards,
Sorin

sorin wrote:Hello,

The error messages are:

- Variable bla has not been declared

- Unmatched quote in expression 'Test

You can fix the errors by declaring the variable bla before using it in template-util.xsl and by closing the quote in the element

Code: Select all

<xsl:value-of select="'Test"/>

which should be:

Code: Select all

<xsl:value-of select="'Test'"/>

Regards,
Sorin

sorin wrote:Hello,

I cannot reproduce the errors with your version of Xalan (2.7.0) and your version of Java (1.5.0_07). Go to Help -> About Eclipse -> Configuration Details, copy all and post here all the content.


Regards,
Sorin

sorin wrote:Thank you for the configuration details. I think the Xalan error messages are localized in German because your user.language is 'de'. What is the English version of the error messages ? Are they the same stylesheet errors as the ones reported by Saxon ? If you switch to user.language 'en' do you get English error messages ?


Regards,
Sorin

vaisberga wrote:

sorin wrote:Thank you for the configuration details. I think the Xalan error messages are localized in German because your user.language is 'de'. What is the English version of the error messages ? Are they the same stylesheet errors as the ones reported by Saxon ? If you switch to user.language 'en' do you get English error messages ?


Regards,
Sorin

I have a locale from de_DE to en_GB changed, but view it's same with description for english language.

Alexander Vaysberg
ADaptions GmbH

vaisberga wrote:I have a locale from de_D to en_GB changed, but view it's same with description for english language.

sorin wrote:What is the English version of the error messages ? Are they the same stylesheet errors as the ones reported by Saxon ?

sorin wrote:Hello,

vaisberga wrote:I have a locale from de_D to en_GB changed, but view it's same with description for english language.

I am not sure I understand. Do you mean that the Xalan error messages of the transformation are now in English and they are the same as the Saxon error messages for the same transformation ? Or the Xalan error description is the same as the Saxon errors reported always in English but the Xalan errors are still in German language after changing from de_DE locale to en_GB locale ?

sorin wrote:What is the English version of the error messages ? Are they the same stylesheet errors as the ones reported by Saxon ?

Also please tell us the English translation of the German error messages. Using automatic translation with Google I am not sure what is the English version of the error messages. Are they the same stylesheet errors as the errors reported by Saxon in English language ?


Regards,
Sorin

sorin wrote:In your case you should use Saxon instead of Xalan for transformations of index.xsl because the reported errors have the correct location so that you click on a line in the Errors view of <oXygen/> and the line with the error is highlighted in the right stylesheet, that is template-util.xsl.


Regards,
Sorin