Re: problem

[Gary L Peskin <ga...@firstech.com>]

Shamil wrote:
> 
> > Please send me your complete XSLT stylesheets and XML input file and
> > I'll try to recreate the problem on my system.
> 
> Everyting is in the attached file. Some tags replaced others deleted for the
> simplifying purpose. There are java source code and a compiled class I'm
> using for transformation.
> This example returns infinite output from <xsl:message> statement indicating
> an infinite loop with <xsl:apply-import>. I can't get what I'm doing wrong
> in a such simple example.
> 
> Thank you for help,
> Shamil
> Mar 30, 14:43

Hi, Shamil --

I think this is a bug in XalanJ2 with xsl:apply-imports.  It appears to
that the template containing the xsl:apply-imports element is itself
being reapplied, causing an infinite loop.  Could you please enter this
into the Bugzilla database and attach your .zip file as the attachment
needed to reproduce this problem?

Thanks,
Gary

Re: problem

[Gary L Peskin <ga...@firstech.com>]

Gary L Peskin wrote:
> 
> Shamil wrote:
> >
> > > Please send me your complete XSLT stylesheets and XML input file and
> > > I'll try to recreate the problem on my system.
> >
> > Everyting is in the attached file. Some tags replaced others deleted for the
> > simplifying purpose. There are java source code and a compiled class I'm
> > using for transformation.
> > This example returns infinite output from <xsl:message> statement indicating
> > an infinite loop with <xsl:apply-import>. I can't get what I'm doing wrong
> > in a such simple example.

Shamil --

I've located the problem with your stylesheets which should allow you to
get working.  The problem is that the xmlns:xsl namespace declaration in
your included stylesheets has a URI that is missing an "s".  You have
Tranform instead of Transform.  Thus, the xsl:import elements didn't
import anything.  If you properly declare the namespace URI, everything
should work as you expect.  I missed this misspelling myself.

I didn't see where you entered the bug into bugzilla so I've added it in
as Bug 1170.  I'll work on it as soon as possible.  Keep watching the
list to see when this bug is fixed.

Thanks for reporting this problem.

Gary