Behaviour differences between war file and exploded directory
I'm baffled by differences in how my web app behaves when deploy in a war f=
ile and when deployed in exploded directory.
Firstly when I deploy in exploded directory format (using wldeploy in ant) =
- the jsps do not precompile. However, when I deploy the war file - again =
using ant and wldeploy - precompile works just fine - and general performan=
ce seems better.
Secondly - the webapp has a pdf file - which is used as a template to dynam=
ically produce a document. When deployed
in exploded format - the webapp works fine and is able to read the pdf. Ho=
wever, when I deploy in war file, the pdf cannot be read.
Surely the behaviour should be the same whether we deploy as a war or explo=
Someone please help
Re: Behaviour differences between war file and exploded directory
Some behaviors will be different between a WAR file deployment and an explo=
ded WAR deployment.
With respect to JSP precompile, you just say "they do not precompile", so I=
can't tell anything about that.
When you read files from an exploded WAR, you can reference them in two way=
s: as a resource, or as an absolute file path. When you read files from a =
WAR file, you can only read files as a resource, and not as an absolute fil=
e path. You're not giving any information about how you're reading the fil=
e, so I can't tell about that either.
You'd have to provide more detail to get better answers.