> I suppose I look at this differently. All these are "just" different
> operations on jar files. As an analogy, consider Java source files
> The default operation might be to open the file in an editor but I
> also typically have other, operations bound to it as well: Compile,
> Print etc. In Windows these appear on a right-click menu, on other
> systems there may be a similar approach.
Yes -- and a .jar could have an association of "run" as in JDK 1.2 you
can have a main class attribute to run an app from a Jar. Or how about
an "add to classpath" menu item. Sure, it's not there yet, but what's
stopping it? Both of these options are irrelevant for .wars -- there
you'd want "edit" or "deploy" actions. You *cant* make this distinction
unless you have the different extension.
> perhaps I use these systems in a different way, but when I develop
> Java, the jar file is usually an output (like a .class file), generated
> by my build process when I recompile the source code, rather than
> a manually edited input file (such as a .java file), When it comes
> to deployment, the jar file is identified by its context; jar files in
> the class path are extensions to the Java class library, jar files
> in a web server config file are web applications and so on.
By that logic, a .txt file in my ~duncan/public_html directory should be
treated as HTML 'cause its in my webroot.
--
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
