Hi All,

We did have the fix  "endExecuteChildren() in ElemVariable.cpp, ElemWithParam.cpp"  in the source code built for Xalan 1.9 libraries(with Xerces 2.7).'
I understand with this fix,  InvalidStackContextException should not be encountered.

I analysed someof the problems with Xalan 1.9

When there is a <xsl:for-each> call on the empty element and when we are processing the data further  we are getting the exception.
<xsl:for-each> should not process empty elements and I am not sure how the Xalan 1.9 allows this.
Xalan 1.3 did not allow for loop for empty elements.


One more issue with Xalan 1.9:
       I have a call         <xsl:if test="contains($assAttRefId,$assatt/@id)">  . When $assatt/@id is null, <xsl: if> test is processed which I understand is a bug.


Please let me know whether anyone experienced the same problem

Thanks and Regards,
Hari Krishna Nitturi
Tata Consultancy Services Limited
Plot No 1, Survey No. 64/2, Software Units Layout
Serilingampally Mandal, Madhapur
Hyderabad - 500034,Andhra Pradesh
India
Mailto: [EMAIL PROTECTED]
Website: http://www.tcs.com



David Bertoni <[EMAIL PROTECTED]>

03/01/06 12:40 PM

Please respond to
[email protected]

To
[email protected]
cc
Subject
Re: InvalidStackContextException





[EMAIL PROTECTED] wrote:
>
> Hi,
>
> I am getting an exception during the Parsing an XML by an XSL with Xalan
> C++ 1.9 and Xerces 2.6 C++ libraries.
>
> The exception is "InvalidStackContextException: Invalid stack context  (,
> line -1, column -1) "
>
> I am calling a template recursively.Is that the cause of the problem?
>

You are probably hitting this bug, which is already fixed in the latest
source code:

http://issues.apache.org/jira/browse/XALANC-453

Dave

ForwardSourceID:NT00005B22    
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

Reply via email to