tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Kirk" <>
Subject RE: Re[2]: JNDI DataSource GlobalResources problem
Date Thu, 28 Oct 2004 14:51:06 GMT

Benson wrote:
> Yoav, in one posting, explained that the servlet spec is 
> written from a
> point of view that only requires support for applications in 
> unexploded WAR files.

Does the spec explicitly state that point of view?  I can't find that
anywhere in the spec doc.  Therefore this makes me ask (out of polite
curiosity) what is that statement based on?

Yoav has already patiently explained the rationale for why mandating "open"
filesystem support would exclude certain platforms - that aspect is now
clear, even if not written up explicitly in the spec.  Thanks for that
insight, Yoav.

He also said that he believes that the spec implicitly only requires support
for warfiles because it only discusses packed war files.  However, I can't
see that from my readings of it.  I've been through it a few times (at least
once wearing "warfile only goggles"), but find sections that mention both
"packed" and "open" webapp deployments, which seems to imply that
either/both are OK.  Further, SRV.9.6 says that web apps "can" be packaged
into a war.  It doesn't say "must", so to me this implies that warfiles are
optional from a webapp developer point of view (but mandatory from the
container author point of view).  Further still, I can't see anywhere in the
spec that says that webapps "must" be deployed in warfiles, or that support
for "open" filesystem deployment is optional.

I happily stand to be corrected on any of these points if someone can point
out the relevant section :)

I don't mean to be a PITA ;) .  As it happens, I adopted warfiles yesterday
as my deployment method during development, after Yoav's comments on this
thread (and I learned to use Ant and upgraded to 5.0.28 in the process).  So
I hope you can see that I'm not just being stubborn - I just want to learn

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

View raw message