>
> Turbine is a servlet based framework that
> allows experienced Java developers to quickly
> build secure web applications.
That text deserve Turbine. I was looking some time
ago for a generic cache system and a connection pool
to be use outside a webapp, but the title make
me search elsewhere :
Better see :
Turbine is a java based framework that
allows experienced Java developers to quickly
build secure applications.
>If I'm building a project that is not a web
>application, why would I even investigate the features
>of Turbine? Let's review the best connection pooling
>mechanism (maybe Turbine, maybe Struts or some
>spinoff) and create a generic utilities project to
>house it. It's lame to have to include all the
>Turbine classes just to get at something as low-level
>as database pooling.
A solution could be to split Turbine in sub-projects, each
which its own jar. As for Tomcat, where you have the servlet
engine and jasper. You could consider the two packages as
independants projects. Tomcat 3.x use jasper and Tomcat 4.0
also use jasper. When somebody fixe a bug in japser, he didn't
have to copy the correction, to the TC 3.2.2, 3.3, 4.0 Tomcat
trees.
Turbine contains ParameterParsing, Database Connection Pools,
Job Scheduling, GlobalCaches, which could be also usefull to
Tomcat, Jasper, log4j ....
A split in sub projects will help having reusable components.
I'm +1 with Arieh Markel about
. Jakarta Base Network Utilities
. Jakarta Base JSP Utilities
. Jakarta XML Utilities
. Jakarta SMTP Utilities
. Jakarta Tools
The Apache Jakarta hosts now many projects (ie log4j arrival)
and must be re-oriented on categories instead of list of
projects at is sourceforge.net :]
Jakarta is much more now just Apache
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
