Paul Hammant wrote:
Berin & Folks,
Given that we are on the subject of packaging and code migration. I
posed the question below on the Cocoon list on the 27th November.
Essentially it concerned the moving of the excellent java compiler
invoker from Cocoon to Excalibur so that other projects (I have in mind
DB) can use it.
There was one reply (also inlined below), in the affirmative from
Ricardo. Perhaps we could give it a go now, in advance of any obsoletion
from Cocoon (as there is a lock on the Excalibur version in Cocoon at
the moment).
I will personally go on record as saying that I am never in favor of a
system that compiles on the fly. Too many things can go wrong. That is
one of the reasons that I am in favor of the interpreted sitemap initiative
in the Cocoon CVS.
I will also strongly warn you that no JDBC driver should ever require
a compiler to be installed on the clients machine. If you require that,
then your driver is broken.
That said, if you want to perform this compilation step for prepared statements,
then you would benefit by Cocoon's compiler invoker.
Be warned that the compiler class is deprecated in JDK 1.4!
I am +.25 on the move of the compiler invoker to excalibur. Not totally
against it, not totally for it, but I can see how it would be useful.
Regards,
- Paul H
-------- Original Message --------
Subject: Re: org.apache.cocoon.components.language.programming.java package
Date: Tue, 27 Nov 2001 08:07:21 -0500
From: "Ricardo Rocha" <[EMAIL PROTECTED]>
Reply-To: cocoon-dev@xml.apache.org
To: <cocoon-dev@xml.apache.org>
References: <[EMAIL PROTECTED]>
Paul Hammant wrote:
> (interloping from the AvalonDB server project)
>
> We'd like to be able to use a technique where we compile SQL SELECT
> statements into Java class "actions". OK, so this is a non-rendering
> class, but it has similar aspects to JSP and XSP pages in that it is
> cached and used again later.
>
> My reason for popping into this list is to basically ask two
questions:
>
> 1) Is the org.apache.cocoon.components.language.programming.java
package
> suitable for reuse, or is it too tightly coupled with Cocoon?
> 2) Can we think about moving the package to Avalon's Excalibur? ( I
can
> do the addition work to Avalon's CVS tree, you folks switch your
impl...)
I'd say the packages under org.apache.cocoon.components.language, in
general, aren't really coupled to Cocoon. The programming.java package
in
particular could be reused with practically no change.
Ricardo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
