Poll: How you configure your web module
Hi,
We are interested how you configure your web modules, in particular:
- how many web resource roots you have.
- does the web resource roots differ from exploded directory.
- how often you have synchronization problems between exploded directory
and web resource / source directories.
Thank you in advance for the answers.
请先登录再写评论。
1> I usually only have a single web resource root and build everything off that as sub directories.
2> The web roots for my projects are usually the same as the exploded directory in most circumstances.
3> I've not had any problems so far.
Please be aware that to date I have not really used IDEA 4.0 for what I would consider extensive J2EE development, it's just co-incidental that since 4.0 was released most of my projects have been more trivial.
1) One resource root
2) My web resource root is usually the "project source" directory
3) I have synchronize set to on and usually don't have problem.
Maxim Mossienko wrote:
>
>
On Thu, 01 Jul 2004 19:25:53 +0400, Maxim Mossienko wrote:
1, with the same caveat as Rob - I've only really used IDEA with a couple
of fairly simple webapps. I think the ability to define multiple web
resource roots looks very useful - I just haven't had the need to do so to
date.
Yes - I personally don't like having my sandbox cluttered with non-source
stuff.
Not noticed any problems so far.
--
Mark Scott
I have one resource root, and unless the webapp is trivial, I do not set up an exploded dir OR a war. Instead I have my webapp deploy 'in-place', since my file structure is exactly how an appserver would expect it to be:
blah-web/WEB-INF/classes, blah-web/WEB-INF/web.xml, etc.
1 - I normally have one resource root, but I do have a project with 10 of them.
2- The web resource root for me ALWAYS is different from exploded dir. I don't have an instance where my web resource root is the actually webapp's strutcture.
3- In the latest version of Pallada, if I have one module per content root (resource root) I don't have a problem anymore, it seems to be OK now.
R
Maxim Mossienko wrote:
One to three source roots.
Exploded directory not the same.
No problems so far.
Michael
oops I misunderstood your third question... I think you meant synch between content root and exploded dir, not local refresh of files synchronize. To that end, I don't use the auto synch because of how it's implemented, where frame deactivation causes a synch. I don't like it, never did. I simply right click on a file and just deploy it if I changed it.
R
1. I often have 3 or 4 roots because it is more convienient for me to store jsp, etc, xml deployment descriptors, and java sources rooted differently in Starteam or CVS. Multiple modules contributes even more to needing multiple roots in the source control.
2. I usually go directly to WAR or EAR as most of my apps are run on full app server not web container.
3. Hardly ever; but see 2.
1) 1-3 web root (a framework and 2 apps)
2) simple app will deploy in place. With the fw+app, have another exploded directory to deploy to
3) Not synchronization per say. The only problem I had is a library that keep forgetting its the deployment option "Copy to lib".
Also like I said in another email, I cannot stop tomcat from within IDEA
We have two modules:
- one Java module containing our application code and rich client GUI.
- one web module, dependent on the first, with one resource root. The
app is deployed in situ (like Hani), so I don't actually need a war or
an exploded directory. (Of course, Idea doesn't allow this, so I point
the exploded directory to the content root, which is also the resource
directory.) In addition, the WEB-INF/classes directory is a symbolic
link to the compilation output of the first module.
The only problem I have is that when compiling the project there is a
delay of about 10 seconds at the end when Idea tries (I think) to
synchronize directories, even though I keep the "synchronize" checkbox off.
Maxim Mossienko wrote:
I have 4 Web Resource directories and 6 content roots that do not overlap.
Each of my web resource directories map to / so the content of each
directory follows the same structure as the exploded directory but does
not contain the entire content.
The exploded directory is on a different logical drive and is used
directly by my app server.
I haven't seen any problems here.
- Tim
Tim Haley wrote:
>> - how many web resource roots you have.
Correction, the 4 web resource directories map directly to 4 of the
content roots. The other content roots map to java src directories.
>> - does the web resource roots differ from exploded directory.
>> - how often you have synchronization problems between exploded
>> directory and web resource / source directories.