Web Module Deployment and Exploded Directory

Hi,

What is the relation between Web Module deployment and Web Module Exploded directory? Usually I point the docBase of my context to the Exploded directory but with this new Web Module Deployment I was wondering what is the use of Web Module Exploded Directory.

thanks,
--Venkat.

5 comments
Comment actions Permalink

Just like in 4.0.4, so you can have idea explode the directory somewhere other than your app server directory, this way you can keep your project completely separate from how your app server works.

R

0
Comment actions Permalink

*Content Root *- Your module files are located below here.
Web Resource Directory - this is the root of your web application.
Below here should be a WEB-INF, etc., according to the servlet
specification. This is where your "source" files are. This where your
.jsp files are located.
_Web Module Exploded Directory _- This is the directory under your
application which will contain your deployed web application.

The confusion probably arises from the way things worked in 3.x. In 3.x
you always worked within your exploded directory. If you are working
within your web application context directory, then you *DO NOT *want an
exploded directory.

Norris Shelton
Sun Certified Java Programmer




Venkat Sonnathi wrote:

>Hi,
>
>What is the relation between Web Module deployment and Web Module Exploded directory? Usually I point the docBase of my context to the Exploded directory but with this new Web Module Deployment I was wondering what is the use of Web Module Exploded Directory.
>
>thanks,
>--Venkat.

>

0
Comment actions Permalink

If you are working
within your web application context directory, then
you *DO NOT *want an
exploded directory.


Norris, you picked my curiousity now. I use an exploded war outside my work content but exactly why should I not use exploded directory if I work (edit files?) in my webapp context directory?

Jacques

0
Comment actions Permalink

Jacque,

It's because your context directory IS your exploded directory in your case. Meaning IDEA knows you have a flat structure meaning that your project directory is setup like it would be if it were an exploded dir.

The exploded dir is only really needed if you project structure is organized for example like so:

jsps
media
resources
web.xml
someotherxml.xml
tlds
src

that structure is not a valid exploded directory, it wouldn't work in an app server of course. To turn it into a directory that would work, you would map each of those directories to a virtual root, which would result in an exploded directory which would look more like this:

index.jsp
someother.jsp
WEB-INF
web.xml
someotherxml.xml
tlds
classes
com
...

hope this answers your question.
R

0
Comment actions Permalink

You do not want to work in your exploded directory, for the same reason
you would not want to have your source files within your classes
directory (output directory). One synchronize output by accident will
have you praying to the gods of CVS.

This can be done, but why?

:-P

Jacques Morel wrote:

>>If you are working
>>within your web application context directory, then
>>you *DO NOT *want an
>>exploded directory.
>>
>>
>>
>
>Norris, you picked my curiousity now. I use an exploded war outside my work content but exactly why should I not use exploded directory if I work (edit files?) in my webapp context directory?
>
>Jacques

>

0

Please sign in to leave a comment.