Tom Amiro wrote:
>
> Hi,
>
> Thanks Scott. Good characterization. We have already fixed the XSLTMark
> bugs that Jacek did, but if there are other problems, we need to
> know. Stefano's offer to prepare a detailed description of the
> symptoms/bugs/suggestions/issues will help. As I mentioned in
> another response related to this thread, I think Cocoon is using
> nonstatic external Java functions, which XSLTC does not currently
> support. So getting Cocoon to work 100% with XSLTC may not
> be just a few minor bug fixes.
Ok, I understand that, but since Cocoon is moving away from the
XSLT-generated sitemap java code (we have a tree interpreter that runs
without compilation and it's equally fast), non-static extensions might
not be a serious concern for us (could we make them static?).
I'm more concerned in *regular* use of XSLT, that is for runtime
transformation or regular XML content.
Bruno reported to have that working and I'll try it myself this week and
report back.
Anyway, people, don't worry, we'll get XSLTC working with Cocoon sooner
or later, even if this requires changing both sides of the fence.
Thanks.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
