You haven't gotten a response in a few days, I'd guess because this is a pretty agile crowd that doesn't do a lot of formal project plans like the ones you're looking for, and because the technology is not really what makes one different from another.
I'd be sure to include a "spike" very early in the project where two or three people write a thin slice of the application from top to bottom and get a good idea of how all those technologies play together. You probably have a lot of uncertainty there ... will you have to build new framework parts, which ones should you use, how should you hook them up. The spike will resolve a lot of questions and establish conventions for how all these things are done ... for now.
The rest of the plan is probably iterate, iterate, iterate, iterate, done!
But the project plan really isn't very much dependent on the technology you use (struts etc.) but on the features you'll have to implement.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Apr 08, 2004
Thanks Ilja Preuss for your valuable inputs and links.
Joined: Jan 29, 2003
I made a leap and guessed the original post was looking for something like the 80 page MS Project plans that circulate at work. You won't find one of those at Don Wells' site.