On 2/9/2001 at 8:12 AM Sam Ruby wrote:
>I would suggest that you start with a proposed code base.
Going back over the posts, there seem to be at least five clear areas of
overlap:
* DataSource/Database Pool
* XML Configuration
* Message Resources / i18n
* JNDI / Naming
* Testing Suites
If you are * actually * interested in working on a Jakarta library
product, and a library implementation of one of these subproducts is an
itch you are ready to scratch, please indicate your commitment with a
+1.
Again, a +1 response indicates that you are actually committing to
working on the given library subproduct in the immediate future. In
order to make a proposal, we need to indicate both the codebases and the
initial Committers, which is the purpose of this vote.
If there is sufficient response to this, we could tally the vote, and
proceed toward a formal proposal. The persons committing to one or more
library products would then work out the other details. (To the
committers go the spoils!) Of course, if no one tenders a (+1) for a
suggested library subproduct, then it would not be part of the initial
proposal.
---
Suggested subproducts and existing Jakarta codebases
DATASOURCE/DATABASE POOL
[Avalon/Cocoon2] DataSource Connection pool
[Struts] DataSource Connection pool
[Turbine] - Database Connection Pool
XML CONFIGURATION
[Avalon/Cocoon2] Configuration (XML based config classes - like a read
only JDOM tree)
[Struts] Digester package - fires events during SAX processing of an XML
document, similar to Tomcat's XmlMapper used to configure itself.
MESSAGE RESOURCES / INTERNATIONALIZATION
[Ant] i18n tools
[Avalon/Cocoon2] XMLResourceBundle/ResourceGroup (ie equivelent)
[Struts] Message Resources - utility classes for packaging resources
(similar to ResourceBundles but Serializable) that include messages for
the same keys in multiple locales.
JNDI
[Avalon] ComponentManager - a component based directory (A
simplification of JNDI and more advanced/generic form of Turbines
Service API).
[Tomcat 4] Naming - Robust implementation of JNDI Context and DirContext
APIs for in-memory resource collections to be accessed via JNDI (with
extensions for things like WAR files that are Tomcat-specific, and
therefore would probably remain in Tomcat).
TESTING SUITES
[Ant] testlet framework (basically similar to early versions of JUnit)
[Tomcat/Watchdog/Slide/Ant] HTTP test clients for unit tests.
[Xalan] Testing infrastructure proposal
< http://marc.theaimsgroup.com/?l=xerces-j-dev&m=98183907325686&w=2 >
SUBPROJECT INFRASTRUCTURE
[*] - Subproject infrastructure: website, documentation, sample
applications, test suites, quality assurance.
[Tinderbox] ?
[GUMP] ?
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
