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).
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]>
