on 1/31/01 8:53 PM, "David Weinrich" <[EMAIL PROTECTED]> wrote:
> With the recent discussions about tinderbox/CJAN and related stuff, I have
> started wondering about the cases where multiple jakarta projects have areas
> of overlap/duplication. From digging into struts for a very short time I
> notice that it also has a Database Connection Pooling component and some
> string utilities ( I don't know if the string utilities are related in any
> way to Avalon or Turbine ). That makes for three projects that implement the
> same or very similar things.
Shame on Struts for not using Turbine's Connection pool. That makes me very
upset because this was something that Craig promised would not happen (that
there wouldn't be much major duplication in Struts as in Turbine).
Even Cocoon uses Turbine's Connection pool and we put a lot of effort into
making a build target for Turbine that allows you to only build the
turbine-pool.jar.
As for StringUtil's duplication, that isn't that big of a deal to me because
this code is duplicated all the time. It is simple to create and simple to
duplicate and most of it is Java 101 type of code. Not as much of a big
deal.
> The ( possibly naive ) question that comes to my mind is: would it be
> beneficial to take certain aspects of these projects that share the same
> goals or produce libraries with the same or similar functionality and create
> a repository of tools that each do one thing ( or maybe two ) and do them
> very very well. One project that comes to mind is log4j, which recently
> joined jakarta. It focuses on one specific task, logging, and it does it
> extremely well.
That is hard to do because you have communities around the software as well
and there just isn't enough time in the day to track all the changes that
are going on across all communities.
> In my mind this issue is very close to how I see something that will
> hopefully someday become CJAN: a place where people can find the specific
> java libraries/tools that they need. I know that a few times in the recent
> past I have looked for things similar to JDBC pooling and something similar
> to cron for java and found what is available is scattered about on
> individual websites. The ability to present developers with a trusted source
> of high quality and very focused components could only enhance the java
> community as a whole and bring new voices/minds/ideas into the
> jakarta/apache community.
Yep.
-jon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
