Slightly off-topic:
Do you think the following approach could work: Consider there is a
central component - e.g. [flatfile] in sandbox - which implements
parsers for various text-base formats like YAML, JSON, CSV, ... and a
generic mechanism for transforming the parsed data into XML SAX events.
Then in theory it would be possible that all XML-based Commons
components like [digester], [configuration], or [jelly] could directly
read such formats.
WDYT?
Oliver
Am 26.07.2012 16:10, schrieb Simone Tripodi:
Good!
hopefully Bruno can provide some help/advice to Elijah!
Thanks,
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Thu, Jul 26, 2012 at 3:43 PM, Bruno P. Kinoshita
<[email protected]> wrote:
+1
I used SnakeYaml in a project [1] that parses TAP test streams and in some
Jenkins plug-ins, and had a look at the source code too. It works very well
with the latest YAML spec and the source code is very neat and with many tests.
TestNG uses SnakeYaml for parsing YAML configuration of test suites too [2].
[1] http://www.tap4j.org
[2] https://github.com/cbeust/testng/blob/master/pom.xml#L124
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
________________________________
From: Simone Tripodi <[email protected]>
To: Commons Developers List <[email protected]>
Sent: Thursday, 26 July 2012 4:58 AM
Subject: Re: [chain2] configuration façade APIs
I may draft up a prototype using YAML as a configuration source, just
to make sure that it in fact is a good abstraction. I noticed that the
SnakeYaml parser is under the Apache 2.0 license
(http://code.google.com/p/snakeyaml/). I'm assuming that it wouldn't
be a problem to take it as a dependency.
+1!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
