Dan,
When I look at your outline, it suggests (to me) that every item on it is
REQUIRED when creating a webapp. That is not necessarily true. Revision
control (CVS, SVN, ...), sharing files with SAMBA, creating an information
Wiki, tracking problems in a Bugzilla, and so forth are excellent
suggestions and good practices for large teams but it should be made clear
they are just that: not good ideas and not mandatory for initial setup. (As
a solo developer, I'm SOO going to get looks or emails from that comment)
Perhaps your document would be better served if broken down to a few more
sections where the reader could pick and choose what is important to them
and see the relationships right away. And an searchable index of this
information never hurts.
An example tree follows:
1. A Basic Struts webapp
a) sample webapp
b) form objects
c) using Business Objects instead of overloading an
Action's methods with a large amount of custom code
d) Add server-side validation
e) implement client-side validation
f) alternate presentation layers: JSP, Velocity, FreeMaker, ...
g) using databases
h) using a DAO such as Hibernate or iBatis
j) connection pooling
i) paging tables of information (DataGrid, DisplayTag, etc)
k) add caching mechanisms to reduce Database or disk access
l) securing pages under /WEB-INF to ensure access only
through (authorized) actions
m) Adding authentication (JAAS, SecurityFilter, roles ...)
2. Rapid development (optional)
a) use an IDE (Eclipse, NetBeans, etc.)
b) Install optional web-server controlling IDE plugins
(Eclipse + Sysdeo
c) Using ANT
3. How to add quality control to your project: (optional)
a) Create JUnit tests for Business Objects
b) Create Web tests using Struts Test Case (?)
4. Group development (optional)
a) Track issues with a Bugzilla
b) Configure module builds with Maven
c) Share files with SAMBA at your discretion
d) Create a Wiki to share key information with the group
e) Add revision control such as CVS, RCS, Subversion, etc.
I'm sure there are many other topics but this is just a suggestion for
enhancing the readability and clarifying what is good to have, but
ultimately optional software.
Regards,
David
-----Original Message-----
From: Peng Tuck [mailto:[EMAIL PROTECTED]
Sent: Friday, November 12, 2004 10:42 PM
To: Struts Users Mailing List
Subject: Re: Application Development Procedure Doc (Again)
Dan,
I don't really understand the document you posted. Maybe it would
be better served
in wiki format or you could post in pdf or something like that. As it
is, I was pretty confused
when I first saw it.
Dan Cancro wrote:
>Hi Group,
>
>This is plea #2 for help with a soup-to-nuts How-To
>doc I'm making for building apps, so that I can
>finally build one. The last doc I did was pretty
>boring. It fetched one joke, one criticism and zero
>offers for assistance.
>
>This new one is much more fun. It has expanding
>trees, iframes, a little color, and even takes
>parameters. Whoa, Nelly!! How fun is that????
>
>I've put a lot of thought/information into it so far.
>I'm just looking for help from people with real
>experience to look it over and clear up the fuzzy
>parts and let me know what I missed or got wrong.
>
>Once it's all polished, I'm sure it will make a
>valuable addition to some collection of docs
>somewhere.
>
>So, here it is:
>http://www.geocities.com/topdowndan/docs/webapp/
>
>Thanks,
>Dan
>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Check out the new Yahoo! Front Page.
>www.yahoo.com
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
