Re: Design pattern needed: breaking webapp into modules
- From: Lew <lew@xxxxxxxxxxxxx>
- Date: Tue, 13 Nov 2007 20:54:24 -0500
Chris wrote:
We've got a webapp that has different modules. Let's say, just as an example, the modules are Editing, Querying, and Reporting. Each module has its own set of JSP pages. The modules also have some sub-pages in common like headers and footers.
We'd really like to distribute the modules independently. A customer might buy only Editing and Querying, but not Reporting, for example.
One of the modules is open source, which means that we'd like to distribute it as a complete, standalone project. But we'd also like to be able to integrate it with the rest of the webapp easily.
Does anyone have a good design pattern for this? I'm struggling with how to organize the webapp, where to put the pages, how to have independent projects that share common pages and code, etc. Any ideas appreciated.
EAR - Enterprise ARchive.
Give each web app component its own context. I've done this and it works all right.
--
Lew
.
- Follow-Ups:
- Re: Design pattern needed: breaking webapp into modules
- From: Are Nybakk
- Re: Design pattern needed: breaking webapp into modules
- From: Chris
- Re: Design pattern needed: breaking webapp into modules
- References:
- Prev by Date: Re: class loader getResourceAsStream
- Next by Date: Re: HashMap toString, what about the other way?
- Previous by thread: Design pattern needed: breaking webapp into modules
- Next by thread: Re: Design pattern needed: breaking webapp into modules
- Index(es):
Relevant Pages
|