Re: Architecture of an enterprise application, multiple projects + multiple customers
- From: Tomer <tomerbd1@xxxxxxxxx>
- Date: Thu, 21 Feb 2008 00:08:59 -0800 (PST)
Why do you believe that it is necessary to have separate applications
in order to have separate modules? It seems to me that you can have
many different modules sharing session data. Perhaps this is a
decision you should rethink.
I would like my large application to be broken up into multiple WARS,
so that new functionality can be pushed out in a more modularized
fashion. Also so that different teams can work on different web
applications, and another important feature that i would like is that
one team can release one web application without effecting anything in
other web applications, regression tests would be performed on exactly
one web application if released by one team.
Thanks
Tomer
.
- Follow-Ups:
- References:
- Prev by Date: Re: Translation
- Next by Date: Re: Inheritance of implementation: what is the reason of?
- Previous by thread: Re: Architecture of an enterprise application, multiple projects + multiple customers
- Next by thread: Re: Architecture of an enterprise application, multiple projects + multiple customers
- Index(es):