James (and others),
File extensions doesn't seem to be part of the "Java Ideology" (couldn't
think of better word). Reasons why:
1) File extensions are very windows 'centric. (already mentioned) In
addition, if I was Microsoft, I would make sure that W2K used .war and .ear
for core system extensions just to tick us off. That would make most of
your arguments invalid. The fact that it "could" happen should be reason
enough not use it as part of a cross platform spec.
2) It should be trivial to write a program that inspects the manifest of a
.jar file then launches the correct tool. A Java Launcher that ships with
the JRE. It knows how to start a jar app, or send it off to the correct
program based on manifest. This would satisfy us GUI freaks (me included).
3) .jar is the Java Archive Extension regardless of what it contains
(already mentioned). I just hope the hubbub about insisting on these
extensions isn't because some marketing person thought it would be "cool" to
have "jars" and "ears" and "wars".
A benefit would be being able to tell what file a does "on sight" but this
fails with jar apps already so it wouldn't be anything new. A naming
convention is a better solution to this problem (already mentioned).
Lance
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's
> Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On
> Behalf Of James
> Duncan Davidson
> Sent: Tuesday, July 06, 1999 5:27 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Comments on 2.2 Public Review Draft
>
>
> > The /WEB-INF subdirectory contains the stuff that is not part of the
> > public document tree. But, does this necessitate a new file type?
> > Anyway, the META-INF directory is supposed to contain
> meta-stuff about
> > the contents. Why not add another entry in the manifest.mf file to
> > indicate that the contents make a "web" application?
> >
> > The same is the case with J2EE, which requires an .ear file for
> > packaging!
> >
> > Am I missing something here?
>
> Yes. A new file type is necessary. The usage of the contents
> of the file
> is different. A jar is an element of the classpath, contains classes,
> and can be possibly double clicked on to launch an application.
>
> A war is a element of the webserver's document hiearchy, is not a
> classpath root (at least not at the root of the war), and can not be
> double clicked on to launch an app. Furthermore, if double
> clicked, and
> os level mapping can be made to launch your packaging tool of
> choice to
> edit or otherwise manipulate the war.
>
> --
> James Davidson
> <[EMAIL PROTECTED]> http://java.sun.com/products/servlet
> <[EMAIL PROTECTED]> http://www.x180.com
> !try; do() PGP:0x7D776205
>
> ______________________________________________________________
> _____________
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources:
http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
