Do you think one should apply the general pattern that interfacing to the Avalon framework is only done on top of a system that is able to run without Avalon, or to use Avalon as a framework that everything else is built on? I think we are at a point where we design a new system and make only code reuse where it is applicable.
--Clemens ----- Original Message ----- From: "Stephen McConnell" <[EMAIL PROTECTED]> To: "Avalon framework users" <[EMAIL PROTECTED]> Sent: Tuesday, November 12, 2002 8:05 PM Subject: Re: Jakarta Lucene goes Avalon > > > Clemens Marschner wrote: > > >The way the processing pipelines look like should be configurable by the > >user. My first thought was that each processing step will become a component > >that can be configured through Avalon's configuration mechanism. I just > >don't know if that's right because in Phoenix this is up to the "application > >assembler", while in the crawler this may well be a user's task. Components > >may be dependent on global services, like a scheduler or a global host > >manager. > > > > Something I should have mentioned in my prev. email - you noted above > the components may be depedent on global services like a scheduler or > global host manager. These relationships are handled in the Avalon work > though the implementation of the Avalon framework Servicable interface. > Serviceable is a replacement of the previouse Composable interface - > the difference being that you can service components with other objects > that may have nothing to do with Avalon. This addition makes life > dramatically easier if you are dealing with existing legacy > applications, or systems developed independently of the Avalon componet > model. > > Cheers, Steve. > > -- > > Stephen J. McConnell > > OSM SARL > digital products for a global economy > mailto:mcconnell@;osm.net > http://www.osm.net > > > > > -- > To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache. org> > For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
