Re: [Xsltforms-support] xalan infinite loop

[Christian M. <chr...@mu...>]

Hi
The good message: The resulting javascript is very responsive and great to
use. I also was thinking that this recursion could maybe be replaced by a
regular expression, if I am not dependent on transforming it in the browser.
Only I would like to know what it _should_ do before I try to make up some
code.

Maybe it would even be a valuable strategy to fork the xsltforms to a more
performance optimized version which allows to use exsl. I think that the use
of xslt forms with something like existdb, as in my case, is a very nice use
of xsltforms. Maybe even more useful than the application in the browser.
Also I could store the generated code in some cache  be cause the only thing
that needs to change often is the instance  data.



> Do you have very very long names in instances??
>
> no, not really, but a lot of instance data because I have an instance with
all attribute default values and one with all elements and their minimal
data model.

How I found out was to compare the template hit counts in the debugger. With
xalan getname has a count of over 10 000
before it crashes.   With saxon 6.5.5 no template has a count larger than
9000 and getname has much less.
saxon takes also more than a minute to do my form. I don't think that this
must be so slow it could probably get orders of magnitudes faster.

Thanks!
>
> -Alain
>

Thanks!