ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad P. Crochet" <>
Subject Re: [PATCH] enhancements
Date Tue, 30 Apr 2002 20:18:45 GMT
On Tue, 30 Apr 2002, Stefan Bodewig wrote:

> Hello Brad,
> thank you for helping us with Ant.
> On Wed, 24 Apr 2002, Brad P. Crochet <> wrote:
> > 1) If you specify a prefix to a <webinf>, if would prepend WEB-INF
> > to the prefix, allowing arbitrary prefixes in the webinf.
> Why wouldn't you simply use a plain <zipfileset> for that?

I'll answer your question with another. Why have a lib or classes attribute?
It seems that you would want to be able to put arbitrary directories into
WEB-INF, not just classes and lib. I assume that the purpose of <webinf> is
so as not to hard-code "WEB-INF/" as part of your prefix. Why have a <WAR>
task at all? It can be accomplished with a <JAR> task. 

I guess what I'm trying to say is for convenience. Besides, it would seem
clear that the following files are in the WEB-INF directory if you use
<webinf> instead of zipfileset. 

> > 2) Having a <jsp> tag. This would put files in "WEB-INF/jsp". This
> > seems to be the de facto standard for placing protected JSPs in a
> > war.
> Hmm, what are "protected JSPs"?  Precompiled JSPs?
> I've seen JRun place generated .java and .class files there, but I've
> never seen Tomcat/Jasper doing something like that.

This one was not as important. But what I mean by protected JSPs is JSPs
that are not publicly accessible resources. If you deploy a WAR into Tomcat
with a URI of /myapp, then you can call http://localhost/myapp/foo.jsp if
foo.jsp is in the root of the .WAR. However, you may want to have a set of
JSPs that should not be accessible from the outside, but will only be
included by other code within your application. You would put these into
WEB-INF. Anything in WEB-INF is considered to be "protected", and not
accessible to the outside world. <jsp> can be accomplished with the above
<webinf> enhancement. Again, these are mostly for convenience and clarity.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message