Re: Moving the configuration beans to core-api

2010-11-01 Thread Emmanuel Lécharny
On 11/1/10 11:36 AM, Alex Karasulu wrote: On Mon, Nov 1, 2010 at 12:29 PM, Emmanuel Lecharnywrote: On 11/1/10 11:04 AM, Alex Karasulu wrote: On Mon, Nov 1, 2010 at 9:51 AM, Kiran Ayyagari wrote: On 11/1/10, Emmanuel Lecharny wrote: One thing I forgot to say : the current configReader

Re: Moving the configuration beans to core-api

2010-11-01 Thread Alex Karasulu
On Mon, Nov 1, 2010 at 12:29 PM, Emmanuel Lecharny wrote: > On 11/1/10 11:04 AM, Alex Karasulu wrote: > >> On Mon, Nov 1, 2010 at 9:51 AM, Kiran Ayyagari >> wrote: >> >> On 11/1/10, Emmanuel Lecharny wrote: >>> One thing I forgot to say : the current configReader is not able to proces

Re: Moving the configuration beans to core-api

2010-11-01 Thread Emmanuel Lecharny
On 11/1/10 11:04 AM, Alex Karasulu wrote: On Mon, Nov 1, 2010 at 9:51 AM, Kiran Ayyagari wrote: On 11/1/10, Emmanuel Lecharny wrote: One thing I forgot to say : the current configReader is not able to process anything but JdbmIndex atm. It has to evolve to be able to do so (probably using re

Re: Moving the configuration beans to core-api

2010-11-01 Thread Alex Karasulu
On Mon, Nov 1, 2010 at 9:51 AM, Kiran Ayyagari wrote: > On 11/1/10, Emmanuel Lecharny wrote: > > One thing I forgot to say : the current configReader is not able to > > process anything but JdbmIndex atm. It has to evolve to be able to do so > > (probably using reflection to do so) > in order to

Re: Moving the configuration beans to core-api

2010-11-01 Thread Emmanuel Lecharny
On 11/1/10 8:51 AM, Kiran Ayyagari wrote: On 11/1/10, Emmanuel Lecharny wrote: One thing I forgot to say : the current configReader is not able to process anything but JdbmIndex atm. It has to evolve to be able to do so (probably using reflection to do so) in order to support all those 'dynami

Re: Moving the configuration beans to core-api

2010-11-01 Thread Kiran Ayyagari
On 11/1/10, Emmanuel Lecharny wrote: > One thing I forgot to say : the current configReader is not able to > process anything but JdbmIndex atm. It has to evolve to be able to do so > (probably using reflection to do so) in order to support all those 'dynamic extension' things talked about in this

Re: Moving the configuration beans to core-api

2010-10-31 Thread Emmanuel Lecharny
One thing I forgot to say : the current configReader is not able to process anything but JdbmIndex atm. It has to evolve to be able to do so (probably using reflection to do so) -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com

Re: Moving the configuration beans to core-api

2010-10-31 Thread Emmanuel Lécharny
On 10/31/10 10:38 PM, Alex Karasulu wrote: On Sun, Oct 31, 2010 at 11:11 PM, Emmanuel Lécharnywrote: On 10/31/10 9:54 PM, Alex Karasulu wrote: On Sun, Oct 31, 2010 at 6:42 PM, Emmanuel Lecharny wrote: Hi guys, There is a base Index class, with two main children : AvlIndex and JdbmIndex. T

Re: Moving the configuration beans to core-api

2010-10-31 Thread Alex Karasulu
On Sun, Oct 31, 2010 at 11:11 PM, Emmanuel Lécharny wrote: > On 10/31/10 9:54 PM, Alex Karasulu wrote: > >> On Sun, Oct 31, 2010 at 6:42 PM, Emmanuel Lecharny> >wrote: >> >> Hi guys, >>> >>> There is a base Index class, with two main children : AvlIndex and >>> JdbmIndex. There is a third child,

Re: Moving the configuration beans to core-api

2010-10-31 Thread Emmanuel Lécharny
On 10/31/10 9:54 PM, Alex Karasulu wrote: On Sun, Oct 31, 2010 at 6:42 PM, Emmanuel Lecharnywrote: Hi guys, There is a base Index class, with two main children : AvlIndex and JdbmIndex. There is a third child, named genericIndex, which is only used to deal with junit annotations used to create

Re: Moving the configuration beans to core-api

2010-10-31 Thread Alex Karasulu
On Sun, Oct 31, 2010 at 6:42 PM, Emmanuel Lecharny wrote: > Hi guys, > > There is a base Index class, with two main children : AvlIndex and > JdbmIndex. There is a third child, named genericIndex, which is only used to > deal with junit annotations used to create a new server instance (it's a > ho

Re: Moving the configuration beans to core-api

2010-10-31 Thread Emmanuel Lecharny
On 10/31/10 6:51 PM, Kiran Ayyagari wrote: hi Emmanuel, On 10/31/10, Emmanuel Lecharny wrote: Hi guys, now that the configuration branch has been merged back to trunk (with some bump in the road, I must admit : I just fixed some badly merged IMO np, what you have done was huge in the branc

Re: Moving the configuration beans to core-api

2010-10-31 Thread Kiran Ayyagari
hi Emmanuel, On 10/31/10, Emmanuel Lecharny wrote: > Hi guys, > > now that the configuration branch has been merged back to trunk (with > some bump in the road, I must admit : I just fixed some badly merged IMO np, what you have done was huge in the branch > file, which caused some errors), I'm

Moving the configuration beans to core-api

2010-10-31 Thread Emmanuel Lecharny
Hi guys, now that the configuration branch has been merged back to trunk (with some bump in the road, I must admit : I just fixed some badly merged file, which caused some errors), I'm now checking some classes that may need a bit of refactoring : the Index hierarchy. There is a base Index c