[ 
https://issues.apache.org/jira/browse/XALANJ-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096903#comment-14096903
 ] 

Uwe Schindler commented on XALANJ-2590:
---------------------------------------

This seems to be caused by XALANJ-2590: The DOM NodeList gets copied to a DTM. 
During this process, it looks like empty text nodes are removed. This causes a 
problem at the end of the iteration. The new Exception was added in this commit.

I will try to produce a testcase with a extension function that creates a 
DocumentFragment with some empty text nodes, which returns 
DocFrag.getChildNodes(), so a nodelist with some empty text nodes.

> "InternalRuntimeError: Expected element missing at 6" after upgrade to XALAN 
> 2.7.2
> ----------------------------------------------------------------------------------
>
>                 Key: XALANJ-2590
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2590
>             Project: XalanJ2
>          Issue Type: Bug
>      Security Level: No security risk; visible to anyone(Ordinary problems in 
> Xalan projects.  Anybody can view the issue.) 
>          Components: DTM, Xalan
>    Affects Versions: 2.7.2
>            Reporter: Uwe Schindler
>            Assignee: Steven J. Hathaway
>
> Hi,
> after upgrading to XALAN 2.7.2, I got very strange errors in one of my XSL 
> transformations, but just for some documents. It took a while to find the 
> problem:
> I have an extension function that returns a NodeList with some elements and 
> text nodes (some HTML). Unfortunately this NodeList contained an *empty* text 
> node as very last element. This is perfectly fine for DOM, because there is 
> nothing that forbids empty text nodes. This empty node caused the following 
> error when invoking <xsl:copy-of select=java:Class:myExtensionFunction()"/>:
> {{InternalRuntimeError: Expected element missing at 6}}
> (6 is the last node in the Node-Set, the empty text node)
> I fixed the issue by calling normalize() before returning the NodeList as 
> quick hack. Later I did a better fix to not create the empty nodes at all.
> In XALAN 2.7.1 this worked without any problem.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to