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.
Xalan-J JIRA defect review - Monday October 16, 2006 from 2:00 to 3:30 pm ED

Xalan-J JIRA defect review - Monday October 16, 2006 from 2:00 to 3:30 pm ED

2006-10-18       - By Henry Zongaro
Reply:     1     2     3     4  

Hi, Mike.

Mike Brown <mike@(protected)> wrote on 2006-10-17 06:59:39 PM:
> Brian Minchau wrote:
> >  2308 - Nodes in a node set created  
> >  using the node-set extension  
> >         function are not accessible  
> >  through key  
> >         Though Henry Z. opened this  
> >  issue he is not the real originator.  
> >         This functionality seems to  
> >  be available in XSLT 2.0 so this is  
> >         the motivation for this  
> >  issue. However Henry Z. doesn't  
> >  think this  
> >         is a high priority issue.  
>
> Well, I have real XSLT 1.0 code that is impacted by this today. I have
to
> completely avoid using Muenchian grouping when operating on generated
> node-sets because of it.
>
> Also, it's not just XSLT 2.0 functionality.

I just wanted to clarify the remarks that I made during the defect review
meeting.  Another user ran into this problem trying to do the same sort of
things with the node-set function key, and that's why I opened the Jira
issue.  What I said about XSLT 2.0 was that the fact that it allows the
key function to return nodes from temporary trees would be an argument in
favour of doing the same thing in XSLT 1.0 if the key function is
evaluated with a context node that is in a tree returned by the node-set
extension function.

The particular user opted to write their stylesheet in a different way, so
I indicated this wasn't a high priority.  If you feel this is a critically
important feature, maybe we should look at fixing this in Xalan-J 2.7.1.

Thanks,

Henry
------------------------------------------------------------------
Henry Zongaro      XSLT Processors Development
IBM SWS Toronto Lab   T/L 969-6044;  Phone +1 905 413-6044
mailto:zongaro@(protected)