Martin Cooper wrote:
I believe Chain is now sufficiently complete and stable to warrant an
official 1.0 release. There are no outstanding bug reports, and the
component is already in use in a number of projects.
The plan is to release HEAD as Commons Chain 1.0 on completion of a
successful
--
Vote: Elect Simon Kitching As Jakarta Commons Committer
[X] +1 Yes let him commit!
[ ] +0
[ ] -0
[ ] -1 I am against this (please include a reason).
Simon Kitching wrote:
On Thu, 2003-10-30 at 02:43, Simon Kitching wrote:
Any logging changes (if something can be agreed on) might go in the mix
too.
And Remy Maucherat's variable substitution stuff, if it's ready?
And Jean-Francois Arcand's changes to schema validation?
J2EE 1.4 is
Simon Kitching wrote:
Looking at this from the user point of view:
Method setSchemaLocation(someURI) is valid, right? Users should be able
to associate a single schema (in some schema language) with the document
to be processed.
And setSchemaLocation(someURI) is valid, because
(a) the user
robert burrell donkin wrote:
On Saturday, October 4, 2003, at 07:26 PM, Jean-Francois Arcand wrote:
Hi Robert,
robert burrell donkin wrote:
hi Jean-Francois
snip
the current code could then be factored out allow schema support for
xerces 2.1. the new code you posted could form the basis
Simon Kitching wrote:
On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote:
Hi Robert,
robert burrell donkin wrote:
hi Jean-Francois
i'm very reluctant to apply a patch that breaks backwards
compatibility but i'd be happier to deprecate them.
That was my initial response
Simon Kitching wrote:
On Tue, 2003-10-07 at 03:09, Jean-Francois Arcand wrote:
Simon Kitching wrote:
On Sun, 2003-10-05 at 07:26, Jean-Francois Arcand wrote:
Doesn't it really suck that there is no parser-independent way of
enabling w3c-standard xml schema support? Is everybody
- robert
On Thursday, October 2, 2003, at 07:47 PM, Jean-Francois Arcand wrote:
Hi,
the current XML schema supports doesn't work with Xerces 2.3/2.4/2.5
(only 2.1 finaly) (at least that's the case with Tomcat 5). The
attached patch remove the current implementation. People interested
to use
or JAXP 1.2.1 to make
- * that class working with XML schema/p
+ * the support of XML schema. You need Xerces 2.1-2.3 and higher or
+ * JAXP 1.2.1 to make that class working with XML schema/p
*
* @author Craig McClanahan
* @author Scott Sanders
- * @author Jean-Francois Arcand
* @version
[EMAIL PROTECTED] wrote:
Maybe, but that's pretty old.
How about we agree to do this:
a) Between us, scan all source in the sandbox looking for license
violations (we can each pick projects to scan)
b) Collate them back here
c) Contact the committers responsible and ask for a resolution
d)
You need:
commons-beanutils
commons-collections
commons-logging
and a JAXP (SAX 2.0 ) compliant parser.
-- Jeanfrancois
V. Cekvenich wrote:
What other jar files does digester need to execute at run time?
(ex: Xerces, JaxP, SAX ?)
tia, V.
--
To unsubscribe, e-mail:
mailto:[EMAIL
11 matches
Mail list logo