XSLTC fails to access auxilliary (non-main) xml file.

• Key: XALANJ-1928
• Type: Bug
• Status: Reopened
• Priority: Major
• Assignee: Unassigned
• Reporter: Barys Dubauski
• Component/s: XSLTC
• Affects Version/s: 2.7.1

Environment

Operating System: Other
Platform: Other

Description

In our project we need to access non-main XML file in order to retrieve
localized strings that will later appear in resulting HTMLs. If we use XSLTC
as our processor it is impossible.

Example. The same example works fine in interpretive Xalan. But fails on Xalan-
XSLTC.

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

    <xsl:output method="html"/>
    
    <xsl:variable name="stringTable" select="document('foo.xml')"/>

    <!-- Look up the parameter key in the localized string table (loaded in
the variable stringTable
       based on the passed in parameter stringTableFileName). If the key
cannot be found then the
       returned string will be !<key>!.
       
       Parameters:
       key - the look up key matched to the key attribute of string elements
in the lookup table
   -->


    <!-- Perhaps not the fastest approach but it is compatible with both XSLTC
and interpretive Xalan -->
    <xsl:template name="getLocalizedString">
        <xsl:param name="key"/>
        <xsl:value-of select="$key"/>
        <xsl:variable name="lookupString" select="$stringTable/strings/string
[@key=$key]"/>
        <xsl:choose>
            <xsl:when test="$lookupString != ''">
                <xsl:value-of select="$lookupString"/>
            </xsl:when>
            <xsl:otherwise>
                <xsl:element name="a">
                    <xsl:attribute name="name">MISSING_L10N_KEY</xsl:attribute>
                    <xsl:text>!!</xsl:text>
                    <xsl:value-of select="$key"/>
                    <xsl:text>!!</xsl:text>
                </xsl:element>
            </xsl:otherwise>
        </xsl:choose>
    </xsl:template>
</xsl:stylesheet>


Example of XML file

<?xml version="1.0" encoding="UTF-8" ?>
<strings>
<string key="Description.Foo">Here goes description of foo</string>
</strings>

Comments

[Barys Dubauski]

Please disregard the comments in the examples I put in the description. They
are old and not true.

[Henry Zongaro]

I added the following template to your example stylesheet to make it complete.
When I did so, the example worked with both Xalan-J Interpretive and XSLTC.

    <xsl:template match="/">
      <xsl:call-template name="getLocalizedString">
        <xsl:with-param name="key" select="'Description.Foo'"/>
      </xsl:call-template>
    </xsl:template>

May I ask you to provide a complete example that demonstrates the problem you
are encountering, along with specific details about the failure that you see
with XSLTC?

[Henry Zongaro]

I was unable to reproduce this problem given the information provided. If you are still able to reproduce it, please reopen the bug report, attaching a complete sample stylesheet and complete sample input.

[Henry Zongaro]

Based on the test case David Green attached to the original Bugzilla bug report, this might be a duplicate of XALANJ-1348.

[David Green]

 A test case with two XML documents, an XSL stylesheet and an Ant build script to run the test case.

[David Green]

This case reproduces the problem: ( I accidentally posted this against XALANJ-1348 as well)

!DOCUMENT1 (foo.xml)
<?xml version="1.0" encoding="UTF-8"?>
<foo>
  <a>foo</a>
</foo>

!DOCUMENT2 (bar.xml)
<?xml version="1.0" encoding="UTF-8"?>
<bar>
  <b>bar</b>
</bar>

!XSLT Stylesheet
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

   <xsl:variable name="BAR" select="document('bar.xml',/)"/>

   <xsl:template match="/">
     <xsl:message>
        Foo root element name: <xsl:value-of select="local-name(/*)"/>
     </xsl:message>
     <xsl:for-each select="$BAR/bar/b">
     <xsl:message>
        Bar root element name: <xsl:value-of select="local-name(/*)"/>
     </xsl:message>
     </xsl:for-each>
   </xsl:template>
</xsl:stylesheet>

The output of running the test (from Ant) is as follows:

foobar-test:
     [echo]
     [echo] USING XSLTC PROCESSOR
     [echo]

     [java] Foo root element name: foo

     [java] Bar root element name: foo

     [java] <?xml version="1.0" encoding="UTF-8"?>
     [echo]
     [echo] USING INTERPRETIVE PROCESSOR
     [echo]
     [java] file:///C:/dev/BCCampus/connector/server-system/codegen/foobar.xslt;
Line #8; Column #19;
     [java] Foo root element name: foo
     [java] file:///C:/dev/BCCampus/connector/server-system/codegen/foobar.xslt;
Line #12; Column #19;
     [java] Bar root element name: bar

     [java] <?xml version="1.0" encoding="UTF-8"?>

I have verified that the problem still exists with the current CVS. Henry: Do you want to take this one?

[Henry Zongaro]

Priority was lost in move from Bugzilla.