A a user of Cocoon, I think that (provided of course Xalan-J is still supported) this would be fantastic!
The ability to include native code in the pipeline as option, at any step, makes perfect sense. To not support it makes no sense, and XSLT is the ideal candidate! > ---------- > From: Stefano Mazzocchi[SMTP:[EMAIL PROTECTED]] > Reply To: [EMAIL PROTECTED] > Sent: Friday, February 15, 2002 4:01 PM > To: Apache Cocoon > Subject: [provocative] resurrecting native code > > I've (finally, some would say) come to the conclusion that WORA (write > once run everywhere) has to do with Java more or less like it has to do > with any other programming language in the world. > > Despite Sun's marketing. > > Thus, we (Pier and I) have decided break the unwritten rule "don't mix > java bytecode with native code" and decided to go resurrect native code > and use JNI. > > Early investigations are *impressive*. > > I even venture to say that the right mix of java code and native code > could well outperform completely native implementations. > > 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? > > -- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
