On 8/23/06, Graham Reeds <grah...@ntlworld.com> wrote:
Edson Carlos Ericksson Richter wrote:
Wondering if you could create an Enterprise Web App, and add as many
War Projects as you want... don't you?
Never thought of that - never looked at the enterprise tab. When I
tried it however the server combobox is empty and hasn't anything
available. Apparently TC 5 isn't considered enterprise?
"Considered" is a qualitative judgement :-). However, Tomcat doesn't know
how to handle EARs, because it is a servlet container, not a J2EE app
server, so it is not a reasonable deployment target for a J2EE "enterprise
application" stored in an EAR.
As to your original question, I would reconsider whether you really want to
deploy this entire thing as a single webapp or not. The only reason to do
so is if you would need to share HTTP session state across the entire
breadth of the overall application. (If all you need is single sign on
support, Tomcat has an optional feature that can do that for you). It feels
to me like you'd be much better off with each "chunk" of the overall
application being deployed independently, from its own web project.
Note that there's no problem with having the "root" webapp having a context
path of "/site" and a subordinate module having a context path of
"/site/accounts". That's merely a matter of setting up the hierarchy you
want for URLs, which should be totally independent of how many webapps there