[ http://issues.apache.org/jira/browse/XALANJ-2335?page=comments#action_12448257 ] Henry Zongaro commented on XALANJ-2335: ---------------------------------------
This is a known problem with Xalan-J's representation of namespace nodes. It's previously been reported in issues XALANJ-334 and XALANJ-1325. XALANJ-2080 and XALANJ-1962. This has never been given a high priority, because nobody's been able to describe a scenario in which it's really important for each element to have its own unique set of namespace nodes for its in-scope namespaces. I'd be interested in hearing whether you have identified such a scenario? > Xalan-J incorrectly identifies the parents of namespace nodes > ------------------------------------------------------------- > > Key: XALANJ-2335 > URL: http://issues.apache.org/jira/browse/XALANJ-2335 > Project: XalanJ2 > Issue Type: Bug > Components: XPath > Affects Versions: 2.7 > Reporter: Mike Brown > Priority: Minor > > Xalan-J 2.7.0 incorrectly identifies the parents of namespace nodes. > A namespace node's parent is supposed to be the element the namespace node is > associated with. > In Xalan, for a namespace node with an empty local-name, parent::* > incorrectly identifies the grandparent element. And for a namespace node with > local-name 'xml', parent::* incorrectly identifies the document element in > every case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
