Hi Steve! 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, rather than having this god class...
I'll point you to discussions anyway as soon as I find it! Have a nice weekend, all the best! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sat, Mar 16, 2013 at 11:39 PM, Steve Westwood <steve.westw...@hexsaw.org.uk> wrote: > Hi Simone, > > Thanks for this - happy to take a closer look a.s.a.p. However, what were/are > yours and Elijahs issues with the CatalogFactory? > > Regards, > > Steve > > -----Original Message----- > From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of > Simone Tripodi > Sent: 16 March 2013 21:04 > To: Commons Developers List > Subject: Re: [Chain] Any future plans for commons-chain? > > Hi again Steve, > > another thing that came in my mind, is about a discussion between Elijah and > I about dropping completely the CatalogFactory and moving the > ChainConfigurationException to the configuration API module. > IIRC this is still related to CHAIN-76... > > TIA! > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Fri, Mar 15, 2013 at 3:46 PM, Simone Tripodi <simonetrip...@apache.org> > wrote: >> Hi Steve, >> >> thanks a lot for your interest on chains! :) >> >> 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 :) >> >> Thanks a lot in advance for your involvement, hope to read from you soon! >> Have a nice day, all the best, >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> On Fri, Mar 15, 2013 at 1:53 PM, Steve Westwood >> <steve.westw...@hexsaw.org.uk> wrote: >>> Hi Simone, >>> >>> Thanks for the response; >>> >>> 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. >>> >>> 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. >>> >>> Thanks again, >>> >>> Steve >>> >>> -----Original Message----- >>> >>> From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On >>> Behalf Of Simone Tripodi >>> >>> Sent: 13 March 2013 20:01 >>> >>> To: Commons Developers List; Steve Westwood >>> >>> Subject: Re: [Chain] Any future plans for commons-chain? >>> >>> >>> >>> Hi Steve, >>> >>> >>> >>> very nice to hear there is someone willing to put new energies on >>> Chain! :) >>> >>> >>> >>> 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 completed. >>> >>> If you want to give a help here, there's enough space to get involved >>> >>> - I would be more than pleased to revamp my interest in Chains :) >>> >>> >>> >>> I hope to read from you soon! >>> >>> All the best! >>> >>> -Simo >>> >>> >>> >>> [1] https://issues.apache.org/jira/browse/CHAIN-76 >>> >>> >>> >>> http://people.apache.org/~simonetripodi/ >>> >>> http://simonetripodi.livejournal.com/ >>> >>> http://twitter.com/simonetripodi >>> >>> http://www.99soft.org/ >>> >>> >>> >>> >>> >>> On Wed, Mar 13, 2013 at 5:50 PM, Steve Westwood >>> <steve.westw...@hexsaw.org.uk> wrote: >>> >>>> I wanted to get a sense of what (if anything) is planned for >>> >>>> commons-chain. I used this in some years ago, and for various >>>> reasons >>> >>>> I now find myself returning to it. In examining the SVN trunk things >>>> have not stood still: >>> >>>> - Discussions (and subsequent work) in 2011 to accommodate work as a >>> >>>> precursor to a chains2 from of CHAIN-53 >>> >>>> - A fair bit of rework to accommodate Generics/Java 5 support >>> >>>> - DSL like capability introduced >>> >>>> - Refactoring >>> >>>> >>> >>>> Of course, the last release was 2008 (1.2), hence is 2.0 imminent, >>>> or >>> >>>> are there other issues that require addressing prior to its roll-out? >>> >>>> I have looked at JIRA, and I am aware of some debates via this list >>> >>>> back in 2009 regarding the incorporation of aspects of Robust-Task >>> >>>> from Min Cha (this has morphed into Whitetask - see >>> >>>> https://code.google.com/p/whitetask/). In addition I note >>>> guice/spring integration has been raised in some form. >>> >>>> >>> >>>> Hence what are the next steps for commons-chain? I am more than >>>> happy >>> >>>> to get involved with this. >>> >>>> >>> >>>> Regards, >>> >>>> >>> >>>> Steve Westwood >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
