Stefano Mazzocchi wrote: >This said, I want to throw a stone in the lake and see where the waves >go: > >if Cocoon performance bottleneck is XSLT processing, what about using >Xalan C as the XSLT processor instead of Xalan J? > As long as it is an option, why not ? Personally, I am not yet convinced that the potential issues (architecture/design, scalability, debugging) earned by mixing native code and Java bytecode are worth it in the long run, but prove me wrong ;)
Best regards, Michael Hartle, Hartle & Klug GbR --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
