You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by Simone Tripodi <si...@apache.org> on 2012/07/21 23:27:30 UTC

[chain2] configuration façade APIs

Hi all guys,

Elijah and and I had a chat and we thought that, since chain2 hasn't
released yet, we are still in time to define a façade API for textual
configurations and rename the current XML configuration module to
xml-configuration (and adapt it to new API) - new formats such as YAML
and JSON will be included in future releases.
Any objection?

@Elijah: if you have cycles to dedicate to it, I think the façade can
be defined in a o.a.c.chain.config package in the core module, in that
way it should be quick enough going to the first release - WDYT?

TIA!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

Am 27.07.2012 15:56, schrieb Elijah Zupancic:
> I didn't know that Jackson supported YAML. Wow, that sounds like a
> great solution.
>
> -Elijah
+1, looks indeed promising. Maybe also interesting for [configuration].

Oliver

>
> On Fri, Jul 27, 2012 at 2:08 AM, Simone Tripodi
> <si...@apache.org> wrote:
>> Hi all [chain2] people,
>>
>> looks like what we have in /trunk is good already to cut a first RC -
>> anyway I would like to spur all involved people to be more "visionary"
>> and do more work now :P
>>
>> Just to put more food for thoughts, for the configuration side: I
>> would like to invite you on evaluating the Jackson[1] library wich is
>> natively JSON and now supports data binding for more formats[2], XML,
>> YAML and Smile included!
>> Hopefully, with Jackson we could get rif of the Digester and have a
>> universal underlying parser wich supports more formats... how does it
>> sound? Maybe we won't need multiple config submodules anymore!
>>
>> About licensing, Jackson is available under ALv2.
>>
>> This is something that worths investigate - WDYT?
>>
>> all the best, have a nice day!
>> -Simo
>>
>> [1] http://wiki.fasterxml.com/JacksonHome
>> [2] http://www.cowtowncoder.com/blog/archives/2012/04/entry_472.html
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Fri, Jul 27, 2012 at 3:55 AM, Elijah Zupancic <el...@apache.org> wrote:
>>> For this particular project I would rather take the approach of writing a
>>> [configuration] based configuration and then extending [configuration]  to
>>> support other formats.
>>>
>>> -Elijah
>>>
>>> On Thursday, July 26, 2012, Simone Tripodi wrote:
>>>
>>>> Hi Oliver,
>>>>
>>>> we are on the same path!!! I had the idea of realizing an "universal"
>>>> parser (XML/JSON/YAML/INI) just writing XML readers adapters :)
>>>>
>>>> good thought!
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Thu, Jul 26, 2012 at 9:37 PM, Oliver Heger
>>>> <ol...@oliver-heger.de> wrote:
>>>>> 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
>>>>>> <br...@yahoo.com.br> 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 <si...@apache.org>
>>>>>>>> To: Commons Developers List <de...@commons.apache.org>
>>>>>>>> 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: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

I didn't know that Jackson supported YAML. Wow, that sounds like a
great solution.

-Elijah

On Fri, Jul 27, 2012 at 2:08 AM, Simone Tripodi
<si...@apache.org> wrote:
> Hi all [chain2] people,
>
> looks like what we have in /trunk is good already to cut a first RC -
> anyway I would like to spur all involved people to be more "visionary"
> and do more work now :P
>
> Just to put more food for thoughts, for the configuration side: I
> would like to invite you on evaluating the Jackson[1] library wich is
> natively JSON and now supports data binding for more formats[2], XML,
> YAML and Smile included!
> Hopefully, with Jackson we could get rif of the Digester and have a
> universal underlying parser wich supports more formats... how does it
> sound? Maybe we won't need multiple config submodules anymore!
>
> About licensing, Jackson is available under ALv2.
>
> This is something that worths investigate - WDYT?
>
> all the best, have a nice day!
> -Simo
>
> [1] http://wiki.fasterxml.com/JacksonHome
> [2] http://www.cowtowncoder.com/blog/archives/2012/04/entry_472.html
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Fri, Jul 27, 2012 at 3:55 AM, Elijah Zupancic <el...@apache.org> wrote:
>> For this particular project I would rather take the approach of writing a
>> [configuration] based configuration and then extending [configuration]  to
>> support other formats.
>>
>> -Elijah
>>
>> On Thursday, July 26, 2012, Simone Tripodi wrote:
>>
>>> Hi Oliver,
>>>
>>> we are on the same path!!! I had the idea of realizing an "universal"
>>> parser (XML/JSON/YAML/INI) just writing XML readers adapters :)
>>>
>>> good thought!
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Thu, Jul 26, 2012 at 9:37 PM, Oliver Heger
>>> <ol...@oliver-heger.de> wrote:
>>> > 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
>>> >> <br...@yahoo.com.br> 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 <si...@apache.org>
>>> >>>> To: Commons Developers List <de...@commons.apache.org>
>>> >>>> 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: dev-unsubscribe@commons.apache.org
>>> >>>> For additional commands, e-mail: dev-help@commons.apache.org
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>
>>> >>> ---------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Hi all [chain2] people,

looks like what we have in /trunk is good already to cut a first RC -
anyway I would like to spur all involved people to be more "visionary"
and do more work now :P

Just to put more food for thoughts, for the configuration side: I
would like to invite you on evaluating the Jackson[1] library wich is
natively JSON and now supports data binding for more formats[2], XML,
YAML and Smile included!
Hopefully, with Jackson we could get rif of the Digester and have a
universal underlying parser wich supports more formats... how does it
sound? Maybe we won't need multiple config submodules anymore!

About licensing, Jackson is available under ALv2.

This is something that worths investigate - WDYT?

all the best, have a nice day!
-Simo

[1] http://wiki.fasterxml.com/JacksonHome
[2] http://www.cowtowncoder.com/blog/archives/2012/04/entry_472.html

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Fri, Jul 27, 2012 at 3:55 AM, Elijah Zupancic <el...@apache.org> wrote:
> For this particular project I would rather take the approach of writing a
> [configuration] based configuration and then extending [configuration]  to
> support other formats.
>
> -Elijah
>
> On Thursday, July 26, 2012, Simone Tripodi wrote:
>
>> Hi Oliver,
>>
>> we are on the same path!!! I had the idea of realizing an "universal"
>> parser (XML/JSON/YAML/INI) just writing XML readers adapters :)
>>
>> good thought!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Thu, Jul 26, 2012 at 9:37 PM, Oliver Heger
>> <ol...@oliver-heger.de> wrote:
>> > 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
>> >> <br...@yahoo.com.br> 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 <si...@apache.org>
>> >>>> To: Commons Developers List <de...@commons.apache.org>
>> >>>> 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: dev-unsubscribe@commons.apache.org
>> >>>> For additional commands, e-mail: dev-help@commons.apache.org
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>> ---------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

For this particular project I would rather take the approach of writing a
[configuration] based configuration and then extending [configuration]  to
support other formats.

-Elijah

On Thursday, July 26, 2012, Simone Tripodi wrote:

> Hi Oliver,
>
> we are on the same path!!! I had the idea of realizing an "universal"
> parser (XML/JSON/YAML/INI) just writing XML readers adapters :)
>
> good thought!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Thu, Jul 26, 2012 at 9:37 PM, Oliver Heger
> <ol...@oliver-heger.de> wrote:
> > 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
> >> <br...@yahoo.com.br> 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 <si...@apache.org>
> >>>> To: Commons Developers List <de...@commons.apache.org>
> >>>> 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: dev-unsubscribe@commons.apache.org
> >>>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>> ---------------------

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Hi Oliver,

we are on the same path!!! I had the idea of realizing an "universal"
parser (XML/JSON/YAML/INI) just writing XML readers adapters :)

good thought!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Thu, Jul 26, 2012 at 9:37 PM, Oliver Heger
<ol...@oliver-heger.de> wrote:
> 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
>> <br...@yahoo.com.br> 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 <si...@apache.org>
>>>> To: Commons Developers List <de...@commons.apache.org>
>>>> 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: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

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
> <br...@yahoo.com.br> 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 <si...@apache.org>
>>> To: Commons Developers List <de...@commons.apache.org>
>>> 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: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

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
<br...@yahoo.com.br> 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 <si...@apache.org>
>>To: Commons Developers List <de...@commons.apache.org>
>>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: dev-unsubscribe@commons.apache.org
>>For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by "Bruno P. Kinoshita" <br...@yahoo.com.br>.

+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 <si...@apache.org>
>To: Commons Developers List <de...@commons.apache.org> 
>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: dev-unsubscribe@commons.apache.org
>For additional commands, e-mail: dev-help@commons.apache.org
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

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.

Thanks,
-Elijah

On Wed, Jul 25, 2012 at 3:36 PM, Elijah Zupancic <el...@apache.org> wrote:
> Hi everyone,
>
> I've created a first draft of refactoring chain so that it uses a
> facade for configuration.
>
> Please see the diff attached to this ticket to get my proposed
> changes: https://issues.apache.org/jira/browse/CHAIN-72
>
> Here is a summary of what I have done:
>
> * Removed the module configuration
> * Created a new module called noop-configuration
> * Created a new module called xml-configuration
> * We now compile the web module against the noop-configuration with
> noop-configuration being scoped as provided in the pom.xml.
> * We check on class instantiation inside ChainServlet and ChainListner
> to validation that we have a valid configuration module present.
> * The ConfigParser class has a new constructor added called:
> ConfigParser(String ruleSet, ClassLoader loader) - this allows a
> ruleset class to be loaded by the classloader without tightly coupling
> the code against digester. Because we detect if the ruleset classname
> is specified in the servlet config and if it is we pass it to our
> constructor, otherwise we use the default constructor. Now we can
> remove the digester dependency from the web module.
>
> Comments:
>
> I still don't like how we store data in map with a classloader as a
> key. I understand that we can an implementation that has a factory per
> classloader, but this seems like a poor man's dependency injection.
>
> See:
>
> CatalogFactory.java:181 - public static <K, V, C extends Map<K, V>>
> CatalogFactory<K, V, C> getInstance() {
>
>
> Anyways, I would love to hear all of your thoughts regarding these changes.
>
> Thanks,
> -Elijah
>
> On Tue, Jul 24, 2012 at 12:43 PM, Oliver Heger
> <ol...@oliver-heger.de> wrote:
>> Hi Simo and Elijah,
>>
>> Am 23.07.2012 21:55, schrieb Simone Tripodi:
>>
>>> Thanks a lot Oliver, much more than appreciated!
>>>
>>> If you could have a look at current configuration stuff at [chain2]
>>> and share what you think would be already *great*!
>>
>>
>> I had a look at the current config module. I understand Elijah's concerns
>> about a redesign of this package because the API indeed seems to be tightly
>> coupled to Digester.
>>
>> IMHO - and IIUC this is also the direction in which you are going - the
>> underlying library used for parsing XML configurations should not be visible
>> in the public API of the parser component. So you would have methods like
>>
>> Chain parseChain(URL url);
>> Catalog parseCatalog(URL url);
>>
>> Then the parsing library is an implementation detail and can be replaced if
>> necessary.
>>
>> One word about using [configuration]: Note that the philosophy of
>> [configuration] is pretty much different from [digester]. [digester] is able
>> - based on its rules - to parse a source file and transform it into a target
>> in-memory representation in a single step. [configuration] in contrast first
>> parses the file and creates an internal in-memory representation. Then you
>> have to evaluate this model (e.g. using XPath or a simplified syntax for
>> accessing hierarchal structures) and do the conversion yourself. So for the
>> use case of creating Chain objects from XML documents [digester] may be
>> better suited because the manual transformation step is not necessary.
>>
>> But in any case, the first step is to define the API of the configuration
>> parser. Then we can think about implementation strategies.
>>
>> Oliver
>>
>>
>>>
>>> then, feel free to put your hands and help us on defining the façade :)
>>>
>>> alles gute,
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Mon, Jul 23, 2012 at 9:43 PM, Oliver Heger
>>> <ol...@oliver-heger.de> wrote:
>>>>
>>>> Am 23.07.2012 09:00, schrieb Simone Tripodi:
>>>>
>>>>> Good morning all,
>>>>>
>>>>> so I continue proposing the already proposed roadmap: let's add the
>>>>> façade APIs for the [chain] configuration stuff, adapt the existing
>>>>> XML configuration reader, use the [configuration] in future releases
>>>>> for new [chain] configurations.
>>>>> How does it sound?
>>>>
>>>>
>>>> +1
>>>>
>>>> If I can support you, let me know.
>>>>
>>>> @Elijah: There is a feature request for adding support for YAML [1].
>>>> IIRC,
>>>> it was planned as a Google Summer of Code project, but it did not
>>>> succeed.
>>>>
>>>> Oliver
>>>>
>>>> [1] https://issues.apache.org/jira/browse/CONFIGURATION-201
>>>>
>>>>
>>>>>
>>>>> best,
>>>>> -Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Oliver,
>>>>>>
>>>>>> Configuration seems like it might be useful if I end up redoing the
>>>>>> XML configuration portion. Are there any plans to support YAML?
>>>>>>
>>>>>> Thanks,
>>>>>> -Elijah
>>>>>>
>>>>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi Simo,
>>>>>>>
>>>>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>>>>
>>>>>>>> Good point Oliver,
>>>>>>>>
>>>>>>>> I honestly didn't think about [configuration], please apologize!
>>>>>>>> since
>>>>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>>>>> the Digester, we thought it would have been good having a façade and
>>>>>>>> plug other textual format...
>>>>>>>>
>>>>>>>> Anyway, we are open to suggestions - what would fit better for you?
>>>>>>>> Do
>>>>>>>> you already have some hints to share?
>>>>>>>>
>>>>>>>> Many thanks in advance, all the best!
>>>>>>>> -Simo
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> nothing concrete. I saw that you mentioned an XML configuration
>>>>>>> module,
>>>>>>> and
>>>>>>> [configuration] contains a XMLConfiguration class. It also supports
>>>>>>> other
>>>>>>> configuration file formats, e.g. properties or ini files which can be
>>>>>>> accessed through the same Configuration interface.
>>>>>>>
>>>>>>> I don't know your concrete use cases. If you already have a working
>>>>>>> implementation based on Digester, there is probably not much benefit
>>>>>>> in
>>>>>>> switching to another API. But if you plan support for other
>>>>>>> configuration
>>>>>>> file formats, [configuration] may be worth a look.
>>>>>>>
>>>>>>> Oliver
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>> http://www.99soft.org/
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>>>>
>>>>>>>>> Depending on your concrete requirements, this is probably
>>>>>>>>> over-sized.
>>>>>>>>> But
>>>>>>>>> maybe a source of inspiration?
>>>>>>>>>
>>>>>>>>> Oliver
>>>>>>>>>
>>>>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>>>>
>>>>>>>>>> Thanks!
>>>>>>>>>>
>>>>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>>>>
>>>>>>>>>>> best,
>>>>>>>>>>> -Simo
>>>>>>>>>>>
>>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi all guys,
>>>>>>>>>>>>
>>>>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2
>>>>>>>>>>>> hasn't
>>>>>>>>>>>> released yet, we are still in time to define a façade API for
>>>>>>>>>>>> textual
>>>>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as
>>>>>>>>>>>> YAML
>>>>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>>>>> Any objection?
>>>>>>>>>>>>
>>>>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade
>>>>>>>>>>>> can
>>>>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in
>>>>>>>>>>>> that
>>>>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>>>>
>>>>>>>>>>>> TIA!
>>>>>>>>>>>> -Simo
>>>>>>>>>>>>
>>>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

Hi everyone,

I've created a first draft of refactoring chain so that it uses a
facade for configuration.

Please see the diff attached to this ticket to get my proposed
changes: https://issues.apache.org/jira/browse/CHAIN-72

Here is a summary of what I have done:

* Removed the module configuration
* Created a new module called noop-configuration
* Created a new module called xml-configuration
* We now compile the web module against the noop-configuration with
noop-configuration being scoped as provided in the pom.xml.
* We check on class instantiation inside ChainServlet and ChainListner
to validation that we have a valid configuration module present.
* The ConfigParser class has a new constructor added called:
ConfigParser(String ruleSet, ClassLoader loader) - this allows a
ruleset class to be loaded by the classloader without tightly coupling
the code against digester. Because we detect if the ruleset classname
is specified in the servlet config and if it is we pass it to our
constructor, otherwise we use the default constructor. Now we can
remove the digester dependency from the web module.

Comments:

I still don't like how we store data in map with a classloader as a
key. I understand that we can an implementation that has a factory per
classloader, but this seems like a poor man's dependency injection.

See:

CatalogFactory.java:181 - public static <K, V, C extends Map<K, V>>
CatalogFactory<K, V, C> getInstance() {


Anyways, I would love to hear all of your thoughts regarding these changes.

Thanks,
-Elijah

On Tue, Jul 24, 2012 at 12:43 PM, Oliver Heger
<ol...@oliver-heger.de> wrote:
> Hi Simo and Elijah,
>
> Am 23.07.2012 21:55, schrieb Simone Tripodi:
>
>> Thanks a lot Oliver, much more than appreciated!
>>
>> If you could have a look at current configuration stuff at [chain2]
>> and share what you think would be already *great*!
>
>
> I had a look at the current config module. I understand Elijah's concerns
> about a redesign of this package because the API indeed seems to be tightly
> coupled to Digester.
>
> IMHO - and IIUC this is also the direction in which you are going - the
> underlying library used for parsing XML configurations should not be visible
> in the public API of the parser component. So you would have methods like
>
> Chain parseChain(URL url);
> Catalog parseCatalog(URL url);
>
> Then the parsing library is an implementation detail and can be replaced if
> necessary.
>
> One word about using [configuration]: Note that the philosophy of
> [configuration] is pretty much different from [digester]. [digester] is able
> - based on its rules - to parse a source file and transform it into a target
> in-memory representation in a single step. [configuration] in contrast first
> parses the file and creates an internal in-memory representation. Then you
> have to evaluate this model (e.g. using XPath or a simplified syntax for
> accessing hierarchal structures) and do the conversion yourself. So for the
> use case of creating Chain objects from XML documents [digester] may be
> better suited because the manual transformation step is not necessary.
>
> But in any case, the first step is to define the API of the configuration
> parser. Then we can think about implementation strategies.
>
> Oliver
>
>
>>
>> then, feel free to put your hands and help us on defining the façade :)
>>
>> alles gute,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Mon, Jul 23, 2012 at 9:43 PM, Oliver Heger
>> <ol...@oliver-heger.de> wrote:
>>>
>>> Am 23.07.2012 09:00, schrieb Simone Tripodi:
>>>
>>>> Good morning all,
>>>>
>>>> so I continue proposing the already proposed roadmap: let's add the
>>>> façade APIs for the [chain] configuration stuff, adapt the existing
>>>> XML configuration reader, use the [configuration] in future releases
>>>> for new [chain] configurations.
>>>> How does it sound?
>>>
>>>
>>> +1
>>>
>>> If I can support you, let me know.
>>>
>>> @Elijah: There is a feature request for adding support for YAML [1].
>>> IIRC,
>>> it was planned as a Google Summer of Code project, but it did not
>>> succeed.
>>>
>>> Oliver
>>>
>>> [1] https://issues.apache.org/jira/browse/CONFIGURATION-201
>>>
>>>
>>>>
>>>> best,
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org>
>>>> wrote:
>>>>>
>>>>>
>>>>> Hi Oliver,
>>>>>
>>>>> Configuration seems like it might be useful if I end up redoing the
>>>>> XML configuration portion. Are there any plans to support YAML?
>>>>>
>>>>> Thanks,
>>>>> -Elijah
>>>>>
>>>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Simo,
>>>>>>
>>>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>>>
>>>>>>> Good point Oliver,
>>>>>>>
>>>>>>> I honestly didn't think about [configuration], please apologize!
>>>>>>> since
>>>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>>>> the Digester, we thought it would have been good having a façade and
>>>>>>> plug other textual format...
>>>>>>>
>>>>>>> Anyway, we are open to suggestions - what would fit better for you?
>>>>>>> Do
>>>>>>> you already have some hints to share?
>>>>>>>
>>>>>>> Many thanks in advance, all the best!
>>>>>>> -Simo
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> nothing concrete. I saw that you mentioned an XML configuration
>>>>>> module,
>>>>>> and
>>>>>> [configuration] contains a XMLConfiguration class. It also supports
>>>>>> other
>>>>>> configuration file formats, e.g. properties or ini files which can be
>>>>>> accessed through the same Configuration interface.
>>>>>>
>>>>>> I don't know your concrete use cases. If you already have a working
>>>>>> implementation based on Digester, there is probably not much benefit
>>>>>> in
>>>>>> switching to another API. But if you plan support for other
>>>>>> configuration
>>>>>> file formats, [configuration] may be worth a look.
>>>>>>
>>>>>> Oliver
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>> http://twitter.com/simonetripodi
>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>>>
>>>>>>>> Depending on your concrete requirements, this is probably
>>>>>>>> over-sized.
>>>>>>>> But
>>>>>>>> maybe a source of inspiration?
>>>>>>>>
>>>>>>>> Oliver
>>>>>>>>
>>>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>>>
>>>>>>>>>> best,
>>>>>>>>>> -Simo
>>>>>>>>>>
>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi all guys,
>>>>>>>>>>>
>>>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2
>>>>>>>>>>> hasn't
>>>>>>>>>>> released yet, we are still in time to define a façade API for
>>>>>>>>>>> textual
>>>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as
>>>>>>>>>>> YAML
>>>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>>>> Any objection?
>>>>>>>>>>>
>>>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade
>>>>>>>>>>> can
>>>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in
>>>>>>>>>>> that
>>>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>>>
>>>>>>>>>>> TIA!
>>>>>>>>>>> -Simo
>>>>>>>>>>>
>>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

Hi Simo and Elijah,

Am 23.07.2012 21:55, schrieb Simone Tripodi:
> Thanks a lot Oliver, much more than appreciated!
>
> If you could have a look at current configuration stuff at [chain2]
> and share what you think would be already *great*!

I had a look at the current config module. I understand Elijah's 
concerns about a redesign of this package because the API indeed seems 
to be tightly coupled to Digester.

IMHO - and IIUC this is also the direction in which you are going - the 
underlying library used for parsing XML configurations should not be 
visible in the public API of the parser component. So you would have 
methods like

Chain parseChain(URL url);
Catalog parseCatalog(URL url);

Then the parsing library is an implementation detail and can be replaced 
if necessary.

One word about using [configuration]: Note that the philosophy of 
[configuration] is pretty much different from [digester]. [digester] is 
able - based on its rules - to parse a source file and transform it into 
a target in-memory representation in a single step. [configuration] in 
contrast first parses the file and creates an internal in-memory 
representation. Then you have to evaluate this model (e.g. using XPath 
or a simplified syntax for accessing hierarchal structures) and do the 
conversion yourself. So for the use case of creating Chain objects from 
XML documents [digester] may be better suited because the manual 
transformation step is not necessary.

But in any case, the first step is to define the API of the 
configuration parser. Then we can think about implementation strategies.

Oliver

>
> then, feel free to put your hands and help us on defining the façade :)
>
> alles gute,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Mon, Jul 23, 2012 at 9:43 PM, Oliver Heger
> <ol...@oliver-heger.de> wrote:
>> Am 23.07.2012 09:00, schrieb Simone Tripodi:
>>
>>> Good morning all,
>>>
>>> so I continue proposing the already proposed roadmap: let's add the
>>> façade APIs for the [chain] configuration stuff, adapt the existing
>>> XML configuration reader, use the [configuration] in future releases
>>> for new [chain] configurations.
>>> How does it sound?
>>
>> +1
>>
>> If I can support you, let me know.
>>
>> @Elijah: There is a feature request for adding support for YAML [1]. IIRC,
>> it was planned as a Google Summer of Code project, but it did not succeed.
>>
>> Oliver
>>
>> [1] https://issues.apache.org/jira/browse/CONFIGURATION-201
>>
>>
>>>
>>> best,
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org>
>>> wrote:
>>>>
>>>> Hi Oliver,
>>>>
>>>> Configuration seems like it might be useful if I end up redoing the
>>>> XML configuration portion. Are there any plans to support YAML?
>>>>
>>>> Thanks,
>>>> -Elijah
>>>>
>>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>>> <ol...@oliver-heger.de> wrote:
>>>>>
>>>>> Hi Simo,
>>>>>
>>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>>
>>>>>> Good point Oliver,
>>>>>>
>>>>>> I honestly didn't think about [configuration], please apologize! since
>>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>>> the Digester, we thought it would have been good having a façade and
>>>>>> plug other textual format...
>>>>>>
>>>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>>>> you already have some hints to share?
>>>>>>
>>>>>> Many thanks in advance, all the best!
>>>>>> -Simo
>>>>>
>>>>>
>>>>>
>>>>> nothing concrete. I saw that you mentioned an XML configuration module,
>>>>> and
>>>>> [configuration] contains a XMLConfiguration class. It also supports
>>>>> other
>>>>> configuration file formats, e.g. properties or ini files which can be
>>>>> accessed through the same Configuration interface.
>>>>>
>>>>> I don't know your concrete use cases. If you already have a working
>>>>> implementation based on Digester, there is probably not much benefit in
>>>>> switching to another API. But if you plan support for other
>>>>> configuration
>>>>> file formats, [configuration] may be worth a look.
>>>>>
>>>>> Oliver
>>>>>
>>>>>
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://simonetripodi.livejournal.com/
>>>>>> http://twitter.com/simonetripodi
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>>
>>>>>>> Depending on your concrete requirements, this is probably over-sized.
>>>>>>> But
>>>>>>> maybe a source of inspiration?
>>>>>>>
>>>>>>> Oliver
>>>>>>>
>>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>>
>>>>>>>>> best,
>>>>>>>>> -Simo
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>> http://www.99soft.org/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all guys,
>>>>>>>>>>
>>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2
>>>>>>>>>> hasn't
>>>>>>>>>> released yet, we are still in time to define a façade API for
>>>>>>>>>> textual
>>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as
>>>>>>>>>> YAML
>>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>>> Any objection?
>>>>>>>>>>
>>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade
>>>>>>>>>> can
>>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in
>>>>>>>>>> that
>>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>>
>>>>>>>>>> TIA!
>>>>>>>>>> -Simo
>>>>>>>>>>
>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Thanks a lot Oliver, much more than appreciated!

If you could have a look at current configuration stuff at [chain2]
and share what you think would be already *great*!

then, feel free to put your hands and help us on defining the façade :)

alles gute,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Mon, Jul 23, 2012 at 9:43 PM, Oliver Heger
<ol...@oliver-heger.de> wrote:
> Am 23.07.2012 09:00, schrieb Simone Tripodi:
>
>> Good morning all,
>>
>> so I continue proposing the already proposed roadmap: let's add the
>> façade APIs for the [chain] configuration stuff, adapt the existing
>> XML configuration reader, use the [configuration] in future releases
>> for new [chain] configurations.
>> How does it sound?
>
> +1
>
> If I can support you, let me know.
>
> @Elijah: There is a feature request for adding support for YAML [1]. IIRC,
> it was planned as a Google Summer of Code project, but it did not succeed.
>
> Oliver
>
> [1] https://issues.apache.org/jira/browse/CONFIGURATION-201
>
>
>>
>> best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org>
>> wrote:
>>>
>>> Hi Oliver,
>>>
>>> Configuration seems like it might be useful if I end up redoing the
>>> XML configuration portion. Are there any plans to support YAML?
>>>
>>> Thanks,
>>> -Elijah
>>>
>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>> <ol...@oliver-heger.de> wrote:
>>>>
>>>> Hi Simo,
>>>>
>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>
>>>>> Good point Oliver,
>>>>>
>>>>> I honestly didn't think about [configuration], please apologize! since
>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>> the Digester, we thought it would have been good having a façade and
>>>>> plug other textual format...
>>>>>
>>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>>> you already have some hints to share?
>>>>>
>>>>> Many thanks in advance, all the best!
>>>>> -Simo
>>>>
>>>>
>>>>
>>>> nothing concrete. I saw that you mentioned an XML configuration module,
>>>> and
>>>> [configuration] contains a XMLConfiguration class. It also supports
>>>> other
>>>> configuration file formats, e.g. properties or ini files which can be
>>>> accessed through the same Configuration interface.
>>>>
>>>> I don't know your concrete use cases. If you already have a working
>>>> implementation based on Digester, there is probably not much benefit in
>>>> switching to another API. But if you plan support for other
>>>> configuration
>>>> file formats, [configuration] may be worth a look.
>>>>
>>>> Oliver
>>>>
>>>>
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>
>>>>>>
>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>
>>>>>> Depending on your concrete requirements, this is probably over-sized.
>>>>>> But
>>>>>> maybe a source of inspiration?
>>>>>>
>>>>>> Oliver
>>>>>>
>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>> <si...@apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>
>>>>>>>> best,
>>>>>>>> -Simo
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>> http://www.99soft.org/
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi all guys,
>>>>>>>>>
>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2
>>>>>>>>> hasn't
>>>>>>>>> released yet, we are still in time to define a façade API for
>>>>>>>>> textual
>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as
>>>>>>>>> YAML
>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>> Any objection?
>>>>>>>>>
>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade
>>>>>>>>> can
>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in
>>>>>>>>> that
>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>
>>>>>>>>> TIA!
>>>>>>>>> -Simo
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>> http://www.99soft.org/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

Am 23.07.2012 09:00, schrieb Simone Tripodi:
> Good morning all,
>
> so I continue proposing the already proposed roadmap: let's add the
> façade APIs for the [chain] configuration stuff, adapt the existing
> XML configuration reader, use the [configuration] in future releases
> for new [chain] configurations.
> How does it sound?
+1

If I can support you, let me know.

@Elijah: There is a feature request for adding support for YAML [1]. 
IIRC, it was planned as a Google Summer of Code project, but it did not 
succeed.

Oliver

[1] https://issues.apache.org/jira/browse/CONFIGURATION-201

>
> best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org> wrote:
>> Hi Oliver,
>>
>> Configuration seems like it might be useful if I end up redoing the
>> XML configuration portion. Are there any plans to support YAML?
>>
>> Thanks,
>> -Elijah
>>
>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>> <ol...@oliver-heger.de> wrote:
>>> Hi Simo,
>>>
>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>
>>>> Good point Oliver,
>>>>
>>>> I honestly didn't think about [configuration], please apologize! since
>>>> [chain] already had a way to be configured via an XML wrapper around
>>>> the Digester, we thought it would have been good having a façade and
>>>> plug other textual format...
>>>>
>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>> you already have some hints to share?
>>>>
>>>> Many thanks in advance, all the best!
>>>> -Simo
>>>
>>>
>>> nothing concrete. I saw that you mentioned an XML configuration module, and
>>> [configuration] contains a XMLConfiguration class. It also supports other
>>> configuration file formats, e.g. properties or ini files which can be
>>> accessed through the same Configuration interface.
>>>
>>> I don't know your concrete use cases. If you already have a working
>>> implementation based on Digester, there is probably not much benefit in
>>> switching to another API. But if you plan support for other configuration
>>> file formats, [configuration] may be worth a look.
>>>
>>> Oliver
>>>
>>>
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>> <ol...@oliver-heger.de> wrote:
>>>>>
>>>>> Is there any relation or overlap to [configuration]?
>>>>>
>>>>> Depending on your concrete requirements, this is probably over-sized. But
>>>>> maybe a source of inspiration?
>>>>>
>>>>> Oliver
>>>>>
>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>> <si...@apache.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>
>>>>>>> best,
>>>>>>> -Simo
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>> http://twitter.com/simonetripodi
>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>> <si...@apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi all guys,
>>>>>>>>
>>>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>>>> and JSON will be included in future releases.
>>>>>>>> Any objection?
>>>>>>>>
>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>
>>>>>>>> TIA!
>>>>>>>> -Simo
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Hi Elijah,

not sure we understand each other there, please confirm IIUC - in my
mind I would have extracted "configurations APIs" (mainly interfaces
and few abstract classes maybe) from the configuration module and put
in the core, then renamed the actual configuration module to
`xml-configuration` and let the [digester] dependency - and make the
switch to [configuration] in a second step, taking care on ingesting
same type of input format.

did I understand correctly?
TIA!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Mon, Jul 23, 2012 at 9:34 PM, Elijah Zupancic <el...@apache.org> wrote:
> I've been going through the chain source for about a day looking for a
> way to decouple the digester configuration. Sadly, I don't think that
> I will be able to do it without removing digester. I may just jump
> ahead and remove [digester] completely and then move us to
> [configuration] for creating dynamic chains. That said, my final
> implementation may change because I haven't been able to prototype a
> good solution yet.
>
> Thanks,
> -Elijah
>
> On Mon, Jul 23, 2012 at 11:11 AM, Elijah Zupancic <el...@apache.org> wrote:
>> Hi Simo,
>>
>> That sounds good to me. However, I'm having trouble separating the
>> existing Catalog implementation from the rest of chain. Digester is
>> tightly coupled across components, so it is a non-trivial refactor to
>> make a configuration facade. I'm working on it, but it will take some
>> time.
>>
>> Thanks,
>> -Elijah
>>
>> On Mon, Jul 23, 2012 at 12:00 AM, Simone Tripodi
>> <si...@apache.org> wrote:
>>> Good morning all,
>>>
>>> so I continue proposing the already proposed roadmap: let's add the
>>> façade APIs for the [chain] configuration stuff, adapt the existing
>>> XML configuration reader, use the [configuration] in future releases
>>> for new [chain] configurations.
>>> How does it sound?
>>>
>>> best,
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org> wrote:
>>>> Hi Oliver,
>>>>
>>>> Configuration seems like it might be useful if I end up redoing the
>>>> XML configuration portion. Are there any plans to support YAML?
>>>>
>>>> Thanks,
>>>> -Elijah
>>>>
>>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>>> <ol...@oliver-heger.de> wrote:
>>>>> Hi Simo,
>>>>>
>>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>>
>>>>>> Good point Oliver,
>>>>>>
>>>>>> I honestly didn't think about [configuration], please apologize! since
>>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>>> the Digester, we thought it would have been good having a façade and
>>>>>> plug other textual format...
>>>>>>
>>>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>>>> you already have some hints to share?
>>>>>>
>>>>>> Many thanks in advance, all the best!
>>>>>> -Simo
>>>>>
>>>>>
>>>>> nothing concrete. I saw that you mentioned an XML configuration module, and
>>>>> [configuration] contains a XMLConfiguration class. It also supports other
>>>>> configuration file formats, e.g. properties or ini files which can be
>>>>> accessed through the same Configuration interface.
>>>>>
>>>>> I don't know your concrete use cases. If you already have a working
>>>>> implementation based on Digester, there is probably not much benefit in
>>>>> switching to another API. But if you plan support for other configuration
>>>>> file formats, [configuration] may be worth a look.
>>>>>
>>>>> Oliver
>>>>>
>>>>>
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://simonetripodi.livejournal.com/
>>>>>> http://twitter.com/simonetripodi
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>>
>>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>>
>>>>>>> Depending on your concrete requirements, this is probably over-sized. But
>>>>>>> maybe a source of inspiration?
>>>>>>>
>>>>>>> Oliver
>>>>>>>
>>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>>
>>>>>>>>> best,
>>>>>>>>> -Simo
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>> http://www.99soft.org/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi all guys,
>>>>>>>>>>
>>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>>> Any objection?
>>>>>>>>>>
>>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>>
>>>>>>>>>> TIA!
>>>>>>>>>> -Simo
>>>>>>>>>>
>>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>>> http://www.99soft.org/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

I've been going through the chain source for about a day looking for a
way to decouple the digester configuration. Sadly, I don't think that
I will be able to do it without removing digester. I may just jump
ahead and remove [digester] completely and then move us to
[configuration] for creating dynamic chains. That said, my final
implementation may change because I haven't been able to prototype a
good solution yet.

Thanks,
-Elijah

On Mon, Jul 23, 2012 at 11:11 AM, Elijah Zupancic <el...@apache.org> wrote:
> Hi Simo,
>
> That sounds good to me. However, I'm having trouble separating the
> existing Catalog implementation from the rest of chain. Digester is
> tightly coupled across components, so it is a non-trivial refactor to
> make a configuration facade. I'm working on it, but it will take some
> time.
>
> Thanks,
> -Elijah
>
> On Mon, Jul 23, 2012 at 12:00 AM, Simone Tripodi
> <si...@apache.org> wrote:
>> Good morning all,
>>
>> so I continue proposing the already proposed roadmap: let's add the
>> façade APIs for the [chain] configuration stuff, adapt the existing
>> XML configuration reader, use the [configuration] in future releases
>> for new [chain] configurations.
>> How does it sound?
>>
>> best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org> wrote:
>>> Hi Oliver,
>>>
>>> Configuration seems like it might be useful if I end up redoing the
>>> XML configuration portion. Are there any plans to support YAML?
>>>
>>> Thanks,
>>> -Elijah
>>>
>>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>>> <ol...@oliver-heger.de> wrote:
>>>> Hi Simo,
>>>>
>>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>>
>>>>> Good point Oliver,
>>>>>
>>>>> I honestly didn't think about [configuration], please apologize! since
>>>>> [chain] already had a way to be configured via an XML wrapper around
>>>>> the Digester, we thought it would have been good having a façade and
>>>>> plug other textual format...
>>>>>
>>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>>> you already have some hints to share?
>>>>>
>>>>> Many thanks in advance, all the best!
>>>>> -Simo
>>>>
>>>>
>>>> nothing concrete. I saw that you mentioned an XML configuration module, and
>>>> [configuration] contains a XMLConfiguration class. It also supports other
>>>> configuration file formats, e.g. properties or ini files which can be
>>>> accessed through the same Configuration interface.
>>>>
>>>> I don't know your concrete use cases. If you already have a working
>>>> implementation based on Digester, there is probably not much benefit in
>>>> switching to another API. But if you plan support for other configuration
>>>> file formats, [configuration] may be worth a look.
>>>>
>>>> Oliver
>>>>
>>>>
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>>> <ol...@oliver-heger.de> wrote:
>>>>>>
>>>>>> Is there any relation or overlap to [configuration]?
>>>>>>
>>>>>> Depending on your concrete requirements, this is probably over-sized. But
>>>>>> maybe a source of inspiration?
>>>>>>
>>>>>> Oliver
>>>>>>
>>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>>> <si...@apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>>
>>>>>>>> best,
>>>>>>>> -Simo
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>> http://www.99soft.org/
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>>> <si...@apache.org> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi all guys,
>>>>>>>>>
>>>>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>>>>> and JSON will be included in future releases.
>>>>>>>>> Any objection?
>>>>>>>>>
>>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>>
>>>>>>>>> TIA!
>>>>>>>>> -Simo
>>>>>>>>>
>>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>>> http://www.99soft.org/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

Hi Simo,

That sounds good to me. However, I'm having trouble separating the
existing Catalog implementation from the rest of chain. Digester is
tightly coupled across components, so it is a non-trivial refactor to
make a configuration facade. I'm working on it, but it will take some
time.

Thanks,
-Elijah

On Mon, Jul 23, 2012 at 12:00 AM, Simone Tripodi
<si...@apache.org> wrote:
> Good morning all,
>
> so I continue proposing the already proposed roadmap: let's add the
> façade APIs for the [chain] configuration stuff, adapt the existing
> XML configuration reader, use the [configuration] in future releases
> for new [chain] configurations.
> How does it sound?
>
> best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org> wrote:
>> Hi Oliver,
>>
>> Configuration seems like it might be useful if I end up redoing the
>> XML configuration portion. Are there any plans to support YAML?
>>
>> Thanks,
>> -Elijah
>>
>> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
>> <ol...@oliver-heger.de> wrote:
>>> Hi Simo,
>>>
>>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>>
>>>> Good point Oliver,
>>>>
>>>> I honestly didn't think about [configuration], please apologize! since
>>>> [chain] already had a way to be configured via an XML wrapper around
>>>> the Digester, we thought it would have been good having a façade and
>>>> plug other textual format...
>>>>
>>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>>> you already have some hints to share?
>>>>
>>>> Many thanks in advance, all the best!
>>>> -Simo
>>>
>>>
>>> nothing concrete. I saw that you mentioned an XML configuration module, and
>>> [configuration] contains a XMLConfiguration class. It also supports other
>>> configuration file formats, e.g. properties or ini files which can be
>>> accessed through the same Configuration interface.
>>>
>>> I don't know your concrete use cases. If you already have a working
>>> implementation based on Digester, there is probably not much benefit in
>>> switching to another API. But if you plan support for other configuration
>>> file formats, [configuration] may be worth a look.
>>>
>>> Oliver
>>>
>>>
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>>> <ol...@oliver-heger.de> wrote:
>>>>>
>>>>> Is there any relation or overlap to [configuration]?
>>>>>
>>>>> Depending on your concrete requirements, this is probably over-sized. But
>>>>> maybe a source of inspiration?
>>>>>
>>>>> Oliver
>>>>>
>>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>>> <si...@apache.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>>
>>>>>>> best,
>>>>>>> -Simo
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>> http://twitter.com/simonetripodi
>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>>> <si...@apache.org> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi all guys,
>>>>>>>>
>>>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>>>> configurations and rename the current XML configuration module to
>>>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>>>> and JSON will be included in future releases.
>>>>>>>> Any objection?
>>>>>>>>
>>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>>
>>>>>>>> TIA!
>>>>>>>> -Simo
>>>>>>>>
>>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>>> http://twitter.com/simonetripodi
>>>>>>>> http://www.99soft.org/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Good morning all,

so I continue proposing the already proposed roadmap: let's add the
façade APIs for the [chain] configuration stuff, adapt the existing
XML configuration reader, use the [configuration] in future releases
for new [chain] configurations.
How does it sound?

best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Mon, Jul 23, 2012 at 7:01 AM, Elijah Zupancic <el...@apache.org> wrote:
> Hi Oliver,
>
> Configuration seems like it might be useful if I end up redoing the
> XML configuration portion. Are there any plans to support YAML?
>
> Thanks,
> -Elijah
>
> On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
> <ol...@oliver-heger.de> wrote:
>> Hi Simo,
>>
>> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>>
>>> Good point Oliver,
>>>
>>> I honestly didn't think about [configuration], please apologize! since
>>> [chain] already had a way to be configured via an XML wrapper around
>>> the Digester, we thought it would have been good having a façade and
>>> plug other textual format...
>>>
>>> Anyway, we are open to suggestions - what would fit better for you? Do
>>> you already have some hints to share?
>>>
>>> Many thanks in advance, all the best!
>>> -Simo
>>
>>
>> nothing concrete. I saw that you mentioned an XML configuration module, and
>> [configuration] contains a XMLConfiguration class. It also supports other
>> configuration file formats, e.g. properties or ini files which can be
>> accessed through the same Configuration interface.
>>
>> I don't know your concrete use cases. If you already have a working
>> implementation based on Digester, there is probably not much benefit in
>> switching to another API. But if you plan support for other configuration
>> file formats, [configuration] may be worth a look.
>>
>> Oliver
>>
>>
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>>> <ol...@oliver-heger.de> wrote:
>>>>
>>>> Is there any relation or overlap to [configuration]?
>>>>
>>>> Depending on your concrete requirements, this is probably over-sized. But
>>>> maybe a source of inspiration?
>>>>
>>>> Oliver
>>>>
>>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>>
>>>>> Thanks!
>>>>>
>>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>>> <si...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>>
>>>>>> best,
>>>>>> -Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://simonetripodi.livejournal.com/
>>>>>> http://twitter.com/simonetripodi
>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>>> <si...@apache.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>> Hi all guys,
>>>>>>>
>>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>>> configurations and rename the current XML configuration module to
>>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>>> and JSON will be included in future releases.
>>>>>>> Any objection?
>>>>>>>
>>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>>
>>>>>>> TIA!
>>>>>>> -Simo
>>>>>>>
>>>>>>> http://people.apache.org/~simonetripodi/
>>>>>>> http://simonetripodi.livejournal.com/
>>>>>>> http://twitter.com/simonetripodi
>>>>>>> http://www.99soft.org/
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

Hi Oliver,

Configuration seems like it might be useful if I end up redoing the
XML configuration portion. Are there any plans to support YAML?

Thanks,
-Elijah

On Sun, Jul 22, 2012 at 1:16 PM, Oliver Heger
<ol...@oliver-heger.de> wrote:
> Hi Simo,
>
> Am 22.07.2012 17:54, schrieb Simone Tripodi:
>
>> Good point Oliver,
>>
>> I honestly didn't think about [configuration], please apologize! since
>> [chain] already had a way to be configured via an XML wrapper around
>> the Digester, we thought it would have been good having a façade and
>> plug other textual format...
>>
>> Anyway, we are open to suggestions - what would fit better for you? Do
>> you already have some hints to share?
>>
>> Many thanks in advance, all the best!
>> -Simo
>
>
> nothing concrete. I saw that you mentioned an XML configuration module, and
> [configuration] contains a XMLConfiguration class. It also supports other
> configuration file formats, e.g. properties or ini files which can be
> accessed through the same Configuration interface.
>
> I don't know your concrete use cases. If you already have a working
> implementation based on Digester, there is probably not much benefit in
> switching to another API. But if you plan support for other configuration
> file formats, [configuration] may be worth a look.
>
> Oliver
>
>
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
>> <ol...@oliver-heger.de> wrote:
>>>
>>> Is there any relation or overlap to [configuration]?
>>>
>>> Depending on your concrete requirements, this is probably over-sized. But
>>> maybe a source of inspiration?
>>>
>>> Oliver
>>>
>>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>>
>>>> Thanks!
>>>>
>>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>>> <si...@apache.org> wrote:
>>>>>
>>>>>
>>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>>
>>>>> best,
>>>>> -Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>>> <si...@apache.org> wrote:
>>>>>>
>>>>>>
>>>>>> Hi all guys,
>>>>>>
>>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>>> released yet, we are still in time to define a façade API for textual
>>>>>> configurations and rename the current XML configuration module to
>>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>>> and JSON will be included in future releases.
>>>>>> Any objection?
>>>>>>
>>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>>
>>>>>> TIA!
>>>>>> -Simo
>>>>>>
>>>>>> http://people.apache.org/~simonetripodi/
>>>>>> http://simonetripodi.livejournal.com/
>>>>>> http://twitter.com/simonetripodi
>>>>>> http://www.99soft.org/
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

Hi Simo,

Am 22.07.2012 17:54, schrieb Simone Tripodi:
> Good point Oliver,
>
> I honestly didn't think about [configuration], please apologize! since
> [chain] already had a way to be configured via an XML wrapper around
> the Digester, we thought it would have been good having a façade and
> plug other textual format...
>
> Anyway, we are open to suggestions - what would fit better for you? Do
> you already have some hints to share?
>
> Many thanks in advance, all the best!
> -Simo

nothing concrete. I saw that you mentioned an XML configuration module, 
and [configuration] contains a XMLConfiguration class. It also supports 
other configuration file formats, e.g. properties or ini files which can 
be accessed through the same Configuration interface.

I don't know your concrete use cases. If you already have a working 
implementation based on Digester, there is probably not much benefit in 
switching to another API. But if you plan support for other 
configuration file formats, [configuration] may be worth a look.

Oliver

>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
> <ol...@oliver-heger.de> wrote:
>> Is there any relation or overlap to [configuration]?
>>
>> Depending on your concrete requirements, this is probably over-sized. But
>> maybe a source of inspiration?
>>
>> Oliver
>>
>> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>>
>>> Thanks!
>>>
>>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>>> <si...@apache.org> wrote:
>>>>
>>>> Just tracked CHAIN-72 and assigned to Elijah
>>>>
>>>> best,
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>>
>>>>
>>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>>> <si...@apache.org> wrote:
>>>>>
>>>>> Hi all guys,
>>>>>
>>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>>> released yet, we are still in time to define a façade API for textual
>>>>> configurations and rename the current XML configuration module to
>>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>>> and JSON will be included in future releases.
>>>>> Any objection?
>>>>>
>>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>>> way it should be quick enough going to the first release - WDYT?
>>>>>
>>>>> TIA!
>>>>> -Simo
>>>>>
>>>>> http://people.apache.org/~simonetripodi/
>>>>> http://simonetripodi.livejournal.com/
>>>>> http://twitter.com/simonetripodi
>>>>> http://www.99soft.org/
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Good point Oliver,

I honestly didn't think about [configuration], please apologize! since
[chain] already had a way to be configured via an XML wrapper around
the Digester, we thought it would have been good having a façade and
plug other textual format...

Anyway, we are open to suggestions - what would fit better for you? Do
you already have some hints to share?

Many thanks in advance, all the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Sun, Jul 22, 2012 at 4:49 PM, Oliver Heger
<ol...@oliver-heger.de> wrote:
> Is there any relation or overlap to [configuration]?
>
> Depending on your concrete requirements, this is probably over-sized. But
> maybe a source of inspiration?
>
> Oliver
>
> Am 22.07.2012 10:00, schrieb Elijah Zupancic:
>
>> Thanks!
>>
>> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
>> <si...@apache.org> wrote:
>>>
>>> Just tracked CHAIN-72 and assigned to Elijah
>>>
>>> best,
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>
>>>
>>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>>> <si...@apache.org> wrote:
>>>>
>>>> Hi all guys,
>>>>
>>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>>> released yet, we are still in time to define a façade API for textual
>>>> configurations and rename the current XML configuration module to
>>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>>> and JSON will be included in future releases.
>>>> Any objection?
>>>>
>>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>>> be defined in a o.a.c.chain.config package in the core module, in that
>>>> way it should be quick enough going to the first release - WDYT?
>>>>
>>>> TIA!
>>>> -Simo
>>>>
>>>> http://people.apache.org/~simonetripodi/
>>>> http://simonetripodi.livejournal.com/
>>>> http://twitter.com/simonetripodi
>>>> http://www.99soft.org/
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Oliver Heger <ol...@oliver-heger.de>.

Is there any relation or overlap to [configuration]?

Depending on your concrete requirements, this is probably over-sized. 
But maybe a source of inspiration?

Oliver

Am 22.07.2012 10:00, schrieb Elijah Zupancic:
> Thanks!
>
> On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
> <si...@apache.org> wrote:
>> Just tracked CHAIN-72 and assigned to Elijah
>>
>> best,
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>
>>
>> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
>> <si...@apache.org> wrote:
>>> Hi all guys,
>>>
>>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>>> released yet, we are still in time to define a façade API for textual
>>> configurations and rename the current XML configuration module to
>>> xml-configuration (and adapt it to new API) - new formats such as YAML
>>> and JSON will be included in future releases.
>>> Any objection?
>>>
>>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>>> be defined in a o.a.c.chain.config package in the core module, in that
>>> way it should be quick enough going to the first release - WDYT?
>>>
>>> TIA!
>>> -Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Elijah Zupancic <el...@apache.org>.

Thanks!

On Sat, Jul 21, 2012 at 11:54 PM, Simone Tripodi
<si...@apache.org> wrote:
> Just tracked CHAIN-72 and assigned to Elijah
>
> best,
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>
>
> On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
> <si...@apache.org> wrote:
>> Hi all guys,
>>
>> Elijah and and I had a chat and we thought that, since chain2 hasn't
>> released yet, we are still in time to define a façade API for textual
>> configurations and rename the current XML configuration module to
>> xml-configuration (and adapt it to new API) - new formats such as YAML
>> and JSON will be included in future releases.
>> Any objection?
>>
>> @Elijah: if you have cycles to dedicate to it, I think the façade can
>> be defined in a o.a.c.chain.config package in the core module, in that
>> way it should be quick enough going to the first release - WDYT?
>>
>> TIA!
>> -Simo
>>
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [chain2] configuration façade APIs

Posted by Simone Tripodi <si...@apache.org>.

Just tracked CHAIN-72 and assigned to Elijah

best,
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/


On Sat, Jul 21, 2012 at 11:27 PM, Simone Tripodi
<si...@apache.org> wrote:
> Hi all guys,
>
> Elijah and and I had a chat and we thought that, since chain2 hasn't
> released yet, we are still in time to define a façade API for textual
> configurations and rename the current XML configuration module to
> xml-configuration (and adapt it to new API) - new formats such as YAML
> and JSON will be included in future releases.
> Any objection?
>
> @Elijah: if you have cycles to dedicate to it, I think the façade can
> be defined in a o.a.c.chain.config package in the core module, in that
> way it should be quick enough going to the first release - WDYT?
>
> TIA!
> -Simo
>
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org