{Wise
- We're a straight IT shop, not a web or product shop. We get body shop
- people for many tasks and its hard enough to get quality people let alone
- train them on Velocity / Turbine. Using a "standard" like JSP helps to
- minimize the training and learning curve problem. You can use JSP with
- Turbine but as every person who asks a JSP question on the list can tell
- you, its not well supported.
}
I think you'll find that development times can be significantly shorter when
using velocity or another template engine, rather than jsp. Just stick to
the a simple and clean approach. Use the least scripting as possible.
Don't think of them as jsp pages. If you build some basic, extensible
actions classes in a front controller servlet framework, then your
programmers can come in and write some basic stuff if that's what you need.
I can hack out almost any basic report, search, form processing, etc in less
than an hour (but I never let uncached, uncolumn sortable searches,
unchecked forms or any simple crap go live). Oh, Training on velocity takes
about 10 minutes.
(Better, reduce your staff and hire a few good people.)
Good luck,
Aaron Smuts
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
