Ted Husted wrote:
>
> My feeling is that we need to do (3) to energize (1) and (2) (or (4) -
> The
> Gathering). I also feel we need to something both useful and manageable
> for (3) that can serve as a baseline example for future work.
>
> My actual suggestion would be to start with the XML Configuration
> component, along with the Testing Suite, supported by a site
> infrastructure designed to scale to multiple components.
And to test that scalabilty, lets do DBConnection Pool as well :)
> Testing seems to be a hot button right now all over Jakarta. But we
> would also need something to test. The XML Configuration component
> saw the largest number of votes. Merging the Avalon and Struts
> components seems manageable, and may provide a lot of
> utility to other products.
Does this mean that we have a project with an XMLConfig component that
will be used by Avalon and Struts, or will there now be three? :)
I think it's important :
* When we are done, we haven't increased the number of XML config tools
in Jakarta.
* The XML Config tool has standalone documentation and build
instructions.
* It is usable by and visible to an external developer that comes to
Jakarta 'shopping'
Ideally :
* The project includes committers from Avalon and Struts because
* Avalon uses it
* Struts uses it.
However, if it works out that we can't find a solution acceptable to
both Avalon and Struts, then we focus on making something suitable for
one of them, to keep the total # of like utilities in Jakarta constant
or smaller. But lets work hard to do something both are satisfied with.
This might be a good way to make all sides happy, as we can see how it
works out wrt committers from all interested parties.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
