Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <00dd01c17744$788db980$216518c8@ricardo>
From: "Ricardo Rocha" <ricardo@apache.org>
To: <cocoon-dev@xml.apache.org>
References: <3C036A09.4050208@yahoo.com>
Subject: Re: org.apache.cocoon.components.language.programming.java package
Date: Tue, 27 Nov 2001 08:07:21 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org