+1
Can everybody just vote? Or is this only for committers?
Regards,
Matthijs
robert burrell donkin wrote:
On Thu, 2005-06-23 at 00:04 +1200, Simon Kitching wrote:
[AARGH - I hate top-posting!!]
It certainly seems like email is generally ready for release.
I think one more RC and a
Let user decides what form choose to use right? Good, I think is a very good
idea!!! If he wants a programmatic or declarative form he only need to
decide!!
Hi,
I've been reading this thread and I think Woody's suggestion to let the
user decide is a really good one. It would not even be hard
Brian Oxley wrote:
[A quick meta-question: is this list the right place for technical
questions of this sort? I don't want to spam the uninterested.]
Mario Ivankovits wrote:
Before I decide to make it public (and non final) could you please
explain in short what you try to do?
I'm working to
simon wrote:
On Mon, 2004-12-06 at 07:30, Mihai C. wrote:
Hi all, being new to digester, I have no clue how to get around my problem.
Here's the story:
I'm trying to parse a config xml that looks like this:
root
a
...
b
.
/b
b
.
Hi Matthijs,
I think your rules-related extension to Digester is very similar to the
digester plugins module. Would you mind reading the javadoc for the
plugins package, and then explaining a little more about the
differences between that and your code? I have placed a copy of the
package-summary
.
Best regards,
Matthijs Wensveen
Func. Internet Integration.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hmm, I think this may be comparable to the digester.plugins packages? I
haven't been paying attention to Digester development for quite a while
so I had never seen these packages.
Of course, I am still willing to provide source code to anyone that is
interested...
Matthijs.
Matthijs Wensveen
and javadocs, or just some extra info.
Regards,
Matthijs Wensveen.
PS. It is possible to use the org.apache.commons.configuration classes
*in* 'our' configuration system. And it's probably also possible to
write a commons configuration class that uses 'our' configurator.
PPS. Currently we have both SAX
I am currently working on a separate site on sourceforge to place all
files, documentation and examples, but hopefully we can place it on
Apache some day soon.
This is how it works:
There is a singleton Context instance that is provided by a Context
subclass. Currently there are 2
