Gary z wrote:
>
> However some of the users got a problem because they
> can't modify the WAR easily
>
In theory, servlet-containers are supposed to provide
tools to help users manipulate WAR files, something along
the lines of the J2EE reference implementation's
deploytool.
> the simple modification became a pain.
>
Yes. If you look in the archives there should be a
thread about where to put config files. Do you put
them in the WAR? But then the users have to modify
the WAR. Somewhere else? But where? Use the J2EE-like
ejb-ref/env-entry/resource-ref? But those are only
required for servlet containers running inside a full
J2EE container. Etc, etc.
> Also on all other engines they can use a FileInputStream
> to open the content of .war file, while if it is not
> extracted, that simply won't work.
>
Hmmm, they should be able to use ServletContext
getResource() and friends to read files inside the
WAR, even on un-expanded WAR. If they can't, then
the engine is broken.
> So is the extract of .war file a standard set by sun or
> something that servlet developers should not assume?
>
Developers should not assume that WARs are expanded.
Did I read right? Are you implementing a servlet
container? Or did you mean that you're implementing
a web-application that will be deployed in someone
else's container?
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
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
