Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Message-ID: <4CA7138F.7040208@apache.org>
Date: Sat, 02 Oct 2010 12:12:15 +0100
From: Mark Thomas <markt@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-GB;
 rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Tomcat Developers List <dev@tomcat.apache.org>
Subject: Re: Jasper & Servlet 3.0
References: <4CA6EF6E.8050701@pidster.com>
In-Reply-To: <4CA6EF6E.8050701@pidster.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 02/10/2010 09:38, Pid wrote:
> Hi,
> 
> Idea: instead of outputting XML as well, for Servlet 3.0 webapps, Jasper
> could just annotate the generated classes.
> 
> Thoughts?

Are you talking about pre-compilation?

Generally, -0 since I loath using annotations for configuration. When
fault finding, if the web.xml doesn't show the complete picture you have
to search though the entire source code (if you have access to it) to
figure out what is going on.

I have only been bitten by this once so far - and in a simple case - but
it was a PITA and took me a little while to figure out what on earth was
going on. Yes Tomcat can providing logging to help, but I still prefer
just to use web.xml.

Mark

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