Scaffold is a reusable package, like the Validator or Tiles. The only
part that needs to be developed for Artimus is what is under the Artimus
package. The rest is reusable, like the Struts framework itself. After
this development phase, the two will be split back out again.
The nice things about Struts is that simple things can be simple. If you
don't want to go whole-hog on the Model/MVC thing, you can still use
Model 1 strategies (like those used by PHP, ASP, and ColdFusion) where
you like, and Model 2 where you need it.
Later, if the application outgrows Model 1 (and most of us have been
there), you'd still be in a good position to refactor your application
to use a Model 2/MVC artitechture. The real justification of Model 2/MVC
is not time-to-market, it's the time-after-market, where 80% of most
budgets are spent. The prime consumer of Struts seem to be intranet
installations where they not only have to ship the code, but maintain
and improve it over the longterm.
Incidentally, the Struts generic connection pool does play well with
tag-based systems. The datasource is stored in the servlet context
under, where many tags can get at it. The default token is
"org.apache.struts.action.DATA_SOURCE", but you can also configure it
for a shorter name if you like. Besides the JSTL, there is also the
dbTags library
http://jakarta.apache.org/taglibs/doc/dbtags-doc/intro.html
For database centric applications, another interesting framework is
http://www.dbforms.org/
-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-- Web: http://husted.com/about/services
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
