Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of lbrtchx@gmail.com designates
 64.233.162.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=qHL1lM3ucYZVRqTZ4BRGc02Le93UL0UJKgGMWli+EBk0FyT9Sk65vhgZtMzC09GSTapIRpe1kqz4Jrg3C5Vrb4QcLYcYhNIhvaH9KI1k13pYESK5Xz+/+dRu1z/21uyUWxe+OPqfpsPddZ3xCtkfbA38BvEgOXMP61djhHE/d8U=
Message-ID: <9ef66fac0712031205l49302354p62865e7bb06a846c@mail.gmail.com>
Date: Mon, 3 Dec 2007 15:05:54 -0500
From: "Albretch Mueller" <lbrtchx@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Still trying to log using org.apache.juli.FileHandler ...
In-Reply-To: 
 <2828B04F0113CD468E6D1D51DF4362A40408A9AB@USEA-EXCH2.na.uis.unisys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9ef66fac0711210916ldf200des1bb1f5b9147e8aa8@mail.gmail.com>
	 <2828B04F0113CD468E6D1D51DF4362A40408A9AB@USEA-EXCH2.na.uis.unisys.com>

~
 /META-INF directory you say? Isn't /META-INF a special descriptor
folder in WAR files?
~
 This is what I read from the latest final release of the Servlet Specification
~
// __ SRV.9.6 Web Application Archive File, page: 71
~
 SRV.9.6 Web Application Archive File
 Web applications can be packaged and signed into a Web ARchive format
(WAR) file using the standard Java archive tools. For example, an
application for issue tracking might be distributed in an archive file
called issuetrack.war.
 When packaged into such a form, a META-INF directory will be present
which contains information useful to Java archive tools. This
directory must not be directly served as content by the container in
response to a Web client's request, though its contents are visible to
servlet code via the getResource and getResourceAsStream calls on the
ServletContext. Also, any requests to access the resources in META-INF
directory must be returned with a SC_NOT_FOUND(404) response.
~
// __ SRV.9.7.1 Dependencies On Extensions, page: 72
~
 The application developer depending on such an extension or
extensions must provide a META-INF/MANIFEST.MF entry in the WAR file
listing all extensions needed by theWAR.
~
// __ SRV.S.19 PFD: Changes in this document since the Public Draft, page: 284
~
 Clarification of the status code when /META-INF/ resource is accessed
(9.6) Change xsd:string to j2ee:string in deployment descriptor (13.4)
~
 lbrtchx

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org