Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of beneritter@gmail.com
 designates 209.85.214.41 as permitted sender)
Subject: Re: [Chain] Any future plans for commons-chain?
References: <1224673202.449667.1363352028626.open-xchange@email.1and1.co.uk>
 <CAAqLGLOGG14oJDqwQveG6Q9ViRhBRP+3viEF6-TgB5fC+7wxdA@mail.gmail.com>
 <CAAqLGLOvN5KdkxVLHkguJajKJqzcHgoe2MSh21GiG=BBA8Ut-w@mail.gmail.com>
 <005a01ce2297$318a8210$949f8630$@hexsaw.org.uk>
 <CAAqLGLP+sxzj9RfuS55XcwrsavrC19TQaiYXjVByNa56bd_xMw@mail.gmail.com>
From: Benedikt Ritter <beneritter@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: 
 <CAAqLGLP+sxzj9RfuS55XcwrsavrC19TQaiYXjVByNa56bd_xMw@mail.gmail.com>
Message-Id: <CDFC6011-C918-4E15-883F-FFBCC129C75C@gmail.com>
Date: Sun, 17 Mar 2013 12:36:55 +0100
To: Commons Developers List <dev@commons.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

Hi Simo,

Send from my mobile device

Am 17.03.2013 um 11:05 schrieb Simone Tripodi <simonetripodi@apache.org>:

> Hi Steve!
>=20
> I have to dig in the ML to find the discussion, anyway IIRC the
> CatalogFactory has been designed to be integrated in the XML/textual
> configuration, mixing a lot of pattern - not in the best way.
> With new Configuration design, we thought delegating the config
> implementation to resolve commands class name to instance,

Resolving classes by name will cause problems with OSGi. Are there other pos=
sibilities to configure [chain]? Sorry I haven't looked at the sources yet, b=
ut will do asap. I'm interested in getting involved in the development of th=
is component.

Regards,
Benedikt

> rather than
> having this god class...
>=20
> I'll point you to discussions anyway as soon as I find it!
>=20
> Have a nice weekend, all the best!
> -Simo
>=20
> http://people.apache.org/~simonetripodi/
> http://simonetripodi.livejournal.com/
> http://twitter.com/simonetripodi
> http://www.99soft.org/
>=20
>=20
> On Sat, Mar 16, 2013 at 11:39 PM, Steve Westwood
> <steve.westwood@hexsaw.org.uk> wrote:
>> Hi Simone,
>>=20
>> Thanks for this - happy to take a closer look a.s.a.p. However, what were=
/are yours and Elijahs issues with the CatalogFactory?
>>=20
>> Regards,
>>=20
>> Steve
>>=20
>> -----Original Message-----
>> From: simone.tripodi@gmail.com [mailto:simone.tripodi@gmail.com] On Behal=
f Of Simone Tripodi
>> Sent: 16 March 2013 21:04
>> To: Commons Developers List
>> Subject: Re: [Chain] Any future plans for commons-chain?
>>=20
>> Hi again Steve,
>>=20
>> another thing that came in my mind, is about a discussion between Elijah a=
nd I about dropping completely the CatalogFactory and moving the ChainConfig=
urationException to the configuration API module.
>> IIRC this is still related to CHAIN-76...
>>=20
>> TIA!
>> -Simo
>>=20
>> http://people.apache.org/~simonetripodi/
>> http://simonetripodi.livejournal.com/
>> http://twitter.com/simonetripodi
>> http://www.99soft.org/
>>=20
>>=20
>> On Fri, Mar 15, 2013 at 3:46 PM, Simone Tripodi <simonetripodi@apache.org=
> wrote:
>>> Hi Steve,
>>>=20
>>> thanks a lot for your interest on chains! :)
>>>=20
>>> Documentation is never enough, so if you do have some more
>>> samples/hints/.../whatever, feel free to push one or more patches on
>>> JIRA, I'd be more than glad to apply it!
>>> Same thing for unit tests, or improve the test coverage - patches are
>>> more than welcome, and playing with tests is usually a good way to get
>>> familiar with codebase :)
>>>=20
>>> Thanks a lot in advance for your involvement, hope to read from you soon=
!
>>> Have a nice day, all the best,
>>> -Simo
>>>=20
>>> http://people.apache.org/~simonetripodi/
>>> http://simonetripodi.livejournal.com/
>>> http://twitter.com/simonetripodi
>>> http://www.99soft.org/
>>>=20
>>>=20
>>> On Fri, Mar 15, 2013 at 1:53 PM, Steve Westwood
>>> <steve.westwood@hexsaw.org.uk> wrote:
>>>> Hi Simone,
>>>>=20
>>>> Thanks for the response;
>>>>=20
>>>> My first thought on commons-chain relate to the other 2.0 issues
>>>> apart from
>>>> CHAIN-76 that have been delivered (which is a lot I notice -
>>>> congratulations on getting to this point!). Are the changes in your
>>>> view stable and do they need further tests/samples to ensure all is
>>>> good (I haven't looked at test coverage yet). I notice cookbook
>>>> sample changes (CHAIN-66)  but do we need to provide more (plus amend
>>>> documentation) to provide certainty going forward?  I guess my
>>>> thinking relates to whether work such as CHAIN-76 is a
>>>> 2.0 or 2.1 issue.  I have no strong view on this although a move away
>>>> from XML-centric configuration is certainly desirable.
>>>>=20
>>>> For CHAIN-76, I will apply the prototype patch to a copy of the 2.0
>>>> over the weekend and take a closer look at what you submitted. I need
>>>> to refresh my memory on commons-chain (its been a while...) but I
>>>> like to think I can get up to speed fairly quickly here.
>>>>=20
>>>> Thanks again,
>>>>=20
>>>> Steve
>>>>=20
>>>> -----Original Message-----
>>>>=20
>>>> From: simone.tripodi@gmail.com [mailto:simone.tripodi@gmail.com] On
>>>> Behalf Of Simone Tripodi
>>>>=20
>>>> Sent: 13 March 2013 20:01
>>>>=20
>>>> To: Commons Developers List; Steve Westwood
>>>>=20
>>>> Subject: Re: [Chain] Any future plans for commons-chain?
>>>>=20
>>>>=20
>>>>=20
>>>> Hi Steve,
>>>>=20
>>>>=20
>>>>=20
>>>> very nice to hear there is someone willing to put new energies on
>>>> Chain! :)
>>>>=20
>>>>=20
>>>>=20
>>>> So, the latest step IMHO before to cut the first chain RC, is
>>>> CHAIN-76[1] where some work has already been done but far to be complet=
ed.
>>>>=20
>>>> If you want to give a help here, there's enough space to get involved
>>>>=20
>>>> - I would be more than pleased to revamp my interest in Chains :)
>>>>=20
>>>>=20
>>>>=20
>>>> I hope to read from you soon!
>>>>=20
>>>> All the best!
>>>>=20
>>>> -Simo
>>>>=20
>>>>=20
>>>>=20
>>>> [1] https://issues.apache.org/jira/browse/CHAIN-76
>>>>=20
>>>>=20
>>>>=20
>>>> http://people.apache.org/~simonetripodi/
>>>>=20
>>>> http://simonetripodi.livejournal.com/
>>>>=20
>>>> http://twitter.com/simonetripodi
>>>>=20
>>>> http://www.99soft.org/
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On Wed, Mar 13, 2013 at 5:50 PM, Steve Westwood
>>>> <steve.westwood@hexsaw.org.uk> wrote:
>>>>=20
>>>>> I wanted to get a sense of what (if anything) is planned for
>>>>=20
>>>>> commons-chain. I used this in some years ago, and for various
>>>>> reasons
>>>>=20
>>>>> I now find myself returning to it. In examining the SVN trunk things
>>>>> have not stood still:
>>>>=20
>>>>> - Discussions (and subsequent work) in 2011 to accommodate work as a
>>>>=20
>>>>> precursor to a chains2 from of CHAIN-53
>>>>=20
>>>>> - A fair bit of rework to accommodate Generics/Java 5 support
>>>>=20
>>>>> - DSL like capability introduced
>>>>=20
>>>>> - Refactoring
>>>>=20
>>>>=20
>>>>> Of course, the last release was 2008 (1.2), hence is 2.0  imminent,
>>>>> or
>>>>=20
>>>>> are there other issues that require addressing prior to its roll-out?
>>>>=20
>>>>> I have looked at JIRA, and I am aware of some debates via this list
>>>>=20
>>>>> back in 2009 regarding the incorporation of aspects of  Robust-Task
>>>>=20
>>>>> from  Min Cha (this has morphed into Whitetask - see
>>>>=20
>>>>> https://code.google.com/p/whitetask/). In addition I note
>>>>> guice/spring integration has been raised in some form.
>>>>=20
>>>>=20
>>>>> Hence what are the next steps for commons-chain? I am more than
>>>>> happy
>>>>=20
>>>>> to get involved with this.
>>>>=20
>>>>=20
>>>>> Regards,
>>>>=20
>>>>=20
>>>>> Steve Westwood
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> ---------------------------------------------------------------------
>>>>=20
>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>>>=20
>>>> For additional commands, e-mail: dev-help@commons.apache.org
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>=20
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>=20

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