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-17       - By Mike Brown
Reply:     1     2     3     4  

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.

XSLT 1.0 says that key() has to return nodes from "the same document as" the
context node, and XSLT 1.0 operates on "document" which is modeled as a
slightly modified XPath node tree, always having a root node under which all
the other nodes fall and thus comprise part of the same document as the root
node.

A converted result tree fragment is a node-set that contains a single root
node. Unless otherwise stated, document identity is going to be based on the
root node. So, regardless of whether your context node is from a converted
result tree fragment, it stands to reason that the context node itself, as
well as any other nodes under the same root, would be potential members of the
node-set returned by key().