Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of funkman@joedog.org designates
 204.74.20.252 as permitted sender)
Message-ID: <4326FDE1.9080507@joedog.org>
Date: Tue, 13 Sep 2005 12:27:13 -0400
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.8) Gecko/20050511
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: Why are tag files always compiled to class files?
References: <10b00a2105091308071ecc9bac@mail.gmail.com>
In-Reply-To: <10b00a2105091308071ecc9bac@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Yeah, I ran into this too. It would require a refactoring of jasper to allow 
this. The last time I looked into this - at first glance, it appeared the tag 
file need compiled so that all of its properties can be looked up for pages 
which used that tag file.

-Tim

ping xu wrote:

> Hi,
> I hope someone could shed some light on this: I'm trying to pre-compile JSPs 
> using Jasper (Jasper2 Ant task from the document). My Tomcat version is 
> 5.0.28. In my webapp, there are a few custom tags in tag file format. When I 
> set the jasper2 "comiple" attribute to false, I expect only java files being 
> generated by Jasper Ant task -- they shouldn't be compiled to class files. 
> This is generally true for all the JSP files. However the tag files don't 
> follow this rule, they always get compiled to class files. Is it possible to 
> let jasper only generate the java files for tag files?
> 
> Thanks,
> 

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