Ted Husted wrote:
>
> Jon :
>
> >No, the right direction would be to use the project which implemented
> this
> >code first and has the most complete solution and ask that project to
> >externalize their code in such a way that it could be used in other
> >projects. Oh wait. The Turbine Project already did all of that work.
>
> No one's interested in a holy war. We all want to use the best
> technology. If the Turbine pool is both best and first, then it
> shouldn't have a problem being approved as a subproject.
>
> >But, I'm not going to start working on that other project until I can
> get
> >agreement and proof that Struts community will contribute to the
> project
> >because so far, they have refused to contribute to Turbine which is
> the
> >project they are duplicating...
>
> If you are serious about this, I would recommend that this be proposed
> as its own subproject. If it's worth doing, it's worth doing right.
> This should not be about Turbine, or Struts, or Jetspeed, it should be
> about a Jakarta connection pool.
And I think it's more than just the connection pool. I think if one
looked around there would be many places where 'basic parts', of
interest to people developing in the Java server space are being
duplicated across multiple projects. These parts seem to always be
things that aren't the main deliverable for the projects, so were
developed to satisfy a local project need, or are absorbed into a
project because there is no good place to put them.
My interest in this subject comes mainly from two places :
- from wanting to have a connection pool to use that I don't have to dig
out of a project I am not using, and futher so I don't have to worry
that the pool will morph in a way subordinate to the needs of the
project it comes from (and therefore change underneath me...)
- from my involvement in Velocity, where there are things that people
who use Velocity want to contribute of a tool and utility nature, but
really are of an application/general use. So from the Velocity point of
view, we want to push them out into a tool/utility package for others to
share, and I am sure that there are plenty of tools and utilities that a
project like Turbine would be able to push out as well for general use.
I have no conclusion other than a misc utility project would be a good
thing to have, especially if we can get the major players to work out
their differences and actually use the thing. I volunteer to help in
any way needed.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
http://jakarta.apache.org/velocity
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
