Subjects
• Home
• Xalan extension functions
• Fomatting question serializing DOM with pretty print
• xalan with pull parser
• Cannot find the declaration
• Apache Xalan drop support to run on JRE 1 1 x
• Why does Doctype change processing of a document
• Node set to XML string via Java extensions in Xalan J: possible?
• Templates/Transformers + thread safety???
• Problem evaluating xpath with muliple prefix with different namespace
• remove an arbitrary attribute from xsl output
• Xalan3 XSLT 2 0 XPath 2 0 support?
• Problem using compiled translets with Xalan !!
• Xalan and jstl 1 1 problem with transform tag
• NullPointer in DOM2DTM getLocalName
• URIResolvers base parameter with xsltc and cascaded imports
• Performance problem for Xalan J on intel dual core
• Standard libraries in JAXP?
• Serializing a DOM tree to XML file, customize entities replacement
• Library Conflict Involving BCEL Library
• A question on how users are using <xsl:message >
• Kevin Cormier as a new Apache Xalan J committer
• Struggling to iterate over tokenized string
• Xalan count() trouble
• Problem with recursive xpath
• Error when switching to java 1 5
• document( ' ')
• Problem with Xalan2 7 0 transformation
• cr/lf options
• entity encoded XML
• can xalan transform 2 xml using one xslt?
• Xalan J JIRA defect review Monday October 16, 2006 from 2:00 to 3:30 pm ED
• xsl transform with cdata section elements
• xslt parameters not expanded
• Weird behavior of XPath evaluate()
• How to avoid <xsl:message > instruction prints stylesheet file informations ?
• Cannot find SimpleTransform subdirectory after installing Xalan J
• recover from document not found exceptions
• jdk1 5 and Xalan jar differences?
• Performance Issue
• Error/Bug adding floating point numbers
• XPathAPI: eval exp using nodes with default namespace
• modifying xalan to output invalid XML
• NullPointerException
• mege two separate xml nodes into one
• Is this a XALAN document identification bug?
• is StylesheetRoot really java io Serializable ?
• transform() fails for DOMSource but succeeds for StreamSource
• Thoughts on Transformer parameter passing
• HELP, Xalan and jstl 1 1 problem with transformer
• Problem with XPath namespace axis?
• string utils:replace deleting search string if replacement string is an HTML
• help with enumeration values pls
• xalan 2 5 1 vs 2 7 performance question
• How to insert/update in XML document
• HTML Serialization and Handling of Ampersands in HREF Attributes
• XHTML link tag stripping
• SystemId Unknown; Line #24; Column #49; java lang NullPointerException
• xpath text() help
• Apostrophe problem with xalan 2 7 0
• How to set variables in XML document?
Links
Home
Oracle database error code ...
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
xsltc throws exception when xsl:choose condition is evaluated

xsltc throws exception when xsl:choose condition is evaluated

2006-03-14       - By Henry Zongaro
Reply:     1     2  

Hi, Amar.

"Reddy Anapalli Amarendra-E65017C" <E65017C@(protected)> wrote on
2006-02-17 03:19:35 PM:
> I have a template call as shown below to find out access_level.
> This variable should be assigned to 3 after the template call
> returns. but instead it throws runtime exception in translet
> while transformation. I am unable understand the reason for
> failure.This works just fine with interpretive processor.Please
> help. cut short version of xsl is included.
> Actual files which I am working are attached for
> transformations use.
> <xsl:variable name="access_level"><xsl:call-template namjava.lang.
> NullPointerException
>         at org.apache.xalan.xsltc.runtime.BasisLibrary.
> compare(BasisLibrary.java:790)
>         at translet.configRackNew.getAccessLevel()
>         at translet.configRackNew.topLevel()

    I don't think anybody ever responded to you.  This appears to be the
same problem, with a different symptom described by Jira issue
XALANJ-1742.[1]

    There is a reference to getAccessLevel inside the definition of the
"access_level" global variable (in configRackNew.xsl), and getAccessLevel
contains references to the global variables "TL1_ADMIN," "TL1_READ-WRITE,"
"TL1_READ-ONLY," and "TL1_NONE."  However, XSLTC is generating code that
defines the access_level variable before the code that defines the values
of those TL1_* variables.  The result is a NullPointerException for any of
those undefined variables.

    The work-around is to modify your stylesheet to take into account
dependencies between global variables.  If GV2 uses the value of GV1,
place the definition of GV1 closer to the start of the document than GV2
(or give it higher import precedence).

    I hope that helps.  If you feel that work-around is not acceptable,
please feel free to add a comment to the Jira issue.

Thanks,

Henry
[1] http://issues.apache.org/jira/browse/XALANJ-1742
------------------------------------------------------------------
Henry Zongaro      Xalan development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)