I'm currently in the early stages of designing a small web application for
managing task allocation and time recording for our IT consultants (a y2k
remediation project, would you believe ;-). This will be a collection of
servlets and JSP pages, talking to an SQL database. I plan to deploy it as
"web application" in tomcat. No plan for tag libaries at this stage.
I am wondering if any of the more experienced developers out there would
like to share some thoughts on how they have managed the system design
specification of their JSP/Servlet web apps? How have you guys & girls
documented your design thoughts, to communicate them to other developers and
the future maintainer's of your systems? In particular I would be
interested to see any document layout templates that people may have
developed for this.
In the meantime, I have started documenting the design in HTML, divided into
areas for the JSP pages, servlet actions (using the single controlling
servlet command pattern), HTML pages, application & session attributes etc.
and lots of links between them to indicate what calls/relies on what. If
this format turns out to be useful I will post a link to some sample back to
group.
Regards
Drew Cox
Barrack Consulting
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
