Re: META-INF dir purpose

2008-05-13 Thread Piller Sébastien
In META-INF I have a context.xml. It is used to override some settings 
from server.xml per each webapp.


But I never put anything else on it. I ask myself if it's ever possible 
to do so.




Stefan Textor a écrit :

Hi,
I write webapps for a while now and I've been wondering all the time 
about the META-INF directory inside the webapp structure. What files 
are recognized by tomcat in this directory and what are they for. I 
have read  several tutorials/specs/books about webapps and I did not 
find anything about it. Can someone give me a clue or recommend a web 
resource?


Thanks in advance.

Stefan

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





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



Re: META-INF dir purpose

2008-05-13 Thread Johnny Kewl


---
HARBOR: http://coolharbor.100free.com/index.htm
The most powerful application server on earth.
The only real POJO Application Server.
Making the Java dream come true.
---
- Original Message - 
From: Stefan Textor [EMAIL PROTECTED]

To: Tomcat Users List users@tomcat.apache.org
Sent: Tuesday, May 13, 2008 7:09 PM
Subject: META-INF dir purpose



Hi,
I write webapps for a while now and I've been wondering all the time about 
the META-INF directory inside the webapp structure. What files are 
recognized by tomcat in this directory and what are they for. I have read 
several tutorials/specs/books about webapps and I did not find anything 
about it. Can someone give me a clue or recommend a web resource?


Thanks in advance.


Stefan

Its the sort of thing you can find out more about in J2EE specs, but in 
Tomcat is doesnt do too much.
Its got the context path in it but (I havent tried it) I think tomcat will 
go with the WebApp name anyway.

So not much... but its Java's way of finding out about a package.
For example in a JAR file its also there and can determine whether a JAR is 
an executable, and I think they also hide digital signatures in there.

On an application server its filled with all sorts of configuration stuff.

One cool thing about it is that Tomcat does not show that folder to a web 
browser... so you can hide stuff in there ;)

but this is normally not done.

Not much... in tomcat ;)  its a little like your appendix - not really 
needed ;)


Tomcat doesnt need too much help to get itself configured... something like 
Glassfish and EAR files... now that needs a lot more help ;)



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





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