First let me say that it _does_ properly deploy and unpack the
'struts-example.war' file, so I know there must be something wrong with
mine.
I'm using this to build the .war file:
target name=war depends=compile
war destfile=${dist}/${context}.war
webxml=config/web.xml
lib
Hello, Wendy.
What happens if you don't use zipfileset?
Also, confirm that you have unpackWARs set on your Context in
$CATALINA_HOME/conf/server.xml. Like this:
Context path=/bendev docBase=bendev unpackWARs=true ... /
...
/Context
What does zipfileset do? If it compresses the targets, you
Doh! Forget what I said about Context.unpackWARs--unpackWARs is a Host
thing. If struts-example.war unpacked successfully under the same Host,
this isn't the problem.
Sean Dockery [EMAIL PROTECTED] wrote in message
b2ts7v$arm$[EMAIL PROTECTED]">news:b2ts7v$arm$[EMAIL PROTECTED]...
Hello,
What happens if you don't use zipfileset?
I can't specify a 'prefix' for the files, so they don't go into the correct
location in the archive. Or else I have to rearrange my development
environment. AFAIK, zipfileset is just a way to specify a collection of
files to be put in the archive.
Any other ideas on why Tomcat doesn't like *this* particular .war file?
It gets weirder. If while Tomcat is running, I rename 'bendev.war' to
'abc.war', Tomcat immediately sees it, expands it and deploys the new
webapp.
(It was a nice experiment to prove that I have not hard coded the context
From what you have described, it is not the WAR file itself that is the
problem. It is a configuration problem with naming the WAR or deploying the
web application.
What does your build.properties (or build.xml) file define ${context} to be?
(Remember that case matter here.)
Wendy Smoak [EMAIL
From what you have described, it is not the WAR file itself that is the
problem. It is a configuration problem with naming the WAR or deploying
the
web application.
What does your build.properties (or build.xml) file define ${context} to
be?
(Remember that case matter here.)
It used to say:
