Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <3F28D3B2.3000401@apache.org>
Date: Thu, 31 Jul 2003 10:30:42 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: Jasper & Cocoon's Eclipse Compiler Plugin
References: <Pine.LNX.4.33.0307302117590.9495-100000@bebop.coremedia.com>
In-Reply-To: <Pine.LNX.4.33.0307302117590.9495-100000@bebop.coremedia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

matthias.ernst@coremedia.com wrote:
> Hi,
> 
> I'm experimenting with embedding Jasper/JSP 2.0 into production servlet
> 2.3 containers / JSP 1.2. That works surprisingly well, using an
> alternative lib directory and an additional classloader. (I want to run
> tagfiles in Websphere,Dynamo,... before 2005.)
> 
> Anwyay, one of the obstacles is Jasper's requirement for the container's
> URLClassLoader for assembling a classpath for the compiler. The cocoon
> project has solved this by using an Eclipse Java compiler plugin that
> reads classes on demand from the thread context classloader. I.e. no jar
> location is needed.
> 
> I've patched Jasper to use that compiler plugin instead of ant and it
> works very well so far. It's even much faster than javac.
> 
> Is there interest to incorporate that compiler and remove the
> URLClassLoader requirement ?

Jasper uses Ant and that was a rather painful switch which needed lots 
of testing to start working fine. You should be able to use EDT through Ant.
I'm against what you propose (lots of pain, no gain).

Remy


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org