I am currently looking at building a large application based on servlets and
JSP. The principles behind the Model 2 architecture are solid, and this
seems like the right approach. However, I have some concerns, and would like
to hear people's thoughts.
The application I am building will likely comprise somewhere between 100 and
150 forms. The use of a single controller servlet, a la Model 2, is
attractive because it provides a focal point for security and database
connectivity, amongst other things. However, it raises some concern
regarding the manageability of so many "entry points" (for lack of a better
term).
It seems that I would need some further structure to partition the
application. I have thought about creating "zones" of functionality, but
it's not clear (to me, at least) what the cleanest and most maintainable way
of doing this would involve.
I have been looking at the Jakarta Struts framework, and very much like the
way that forms and actions are hooked up. However, I'm concerned that it
won't fly for an application with so many forms as I will have.
By the way, this is an intranet app, not an Internet app, and, as such,
there will be a relatively small number of users. Scalability in number of
users is not important to me, but scalability in number of forms is.
Any thoughts would be very much appreciated.
--
Martin Cooper
Tumbleweed Communications
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
