> from my understanding, WAR files are self extracting. once
> you put the war file in
> the appropriate directory and it is called by the client it
> will extract the files
> and create the appropriate directory.
I'm no guru, but I think you are wrong (probably wrong more in you choice of
word than your understanding, but I'll clarify anyway...)
A self-extracting archive is one that requires no other program to extract
it. In WindowsLand, you often get WinZip self-extractors. They are
executable programs that extract files from themselves... They differ from
plain vanilla WinZip archives in that the standard WinZip archive needs an
unzipping program (eg WinZip) to extract files from it.
WAR files are more like zip archives than WinZip self-extractors. They
contain no code in themselves that will extract anything. They are just in a
format known to the Java platform, and when it comes across a WAR (or JAR)
file in it's classpath, it will extract the files from it. Note that the JVM
itself does the extracting (ie a program external to the WAR/JAR file
itself)...
As for the other questions, I'm not real familiar with JSP technology, but
I'll offer some answers anyway...
>
> Sujoy Kumar Bose wrote:
>
> > Hi,
> >
> > Can somebody simplify the terms used in the followimg
> mail.I quote
> >
> > >From :Nestel, Frank [[EMAIL PROTECTED]]
> >
> > To: [EMAIL PROTECTED]
> >
> > "Thank you again. I've only read the servlet 2.2 specs yet to know
> > that a war file is a special kind of jar file. So I guess I know
> > how to contruct a war file.
> >
> > But new questions arise:
> > * How do I configure the servlet container to fetch files from an
> > war archive instead of an directory (a sample web.xml
> would be nice)
I imagine (no experience here...) that you would specify it in the classpath
or something similar... It may depend on the individual container...
> > * Are there limitations in existing 2.2 engines (Resin is
> one of our
> > current favorites) concerning war-Archives?
no idea
> > * How is it possible to remove all JAVA/JSP source code from an
> > application before shipment.
JAVA source: When you make the WAR (JAR) file, simply don't include the
.java files. All you need put in there is the .class files....
JSP source: My (poor) understanding is that JSP doesn't really get compiled
into .class files. You distribute your JSP files as they are, and they are
parsed and compiled dynamically, as needed. Remember that the end result of
processing a .jsp file is a .html file, but this .html file changes
depending on the data given to the .jsp file... So... You do put your .jsp
sources into the WAR file. However, most of your important code (your
business logic) will be in the Java classes anyway, so someone seeing your
JSP code is not much different from someone veiwing your html source...
someone correct me if I am wrong...
HTH
rr
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
