Unquestionably you can gain from using Avalon, I'm using the framework
quite a bit too. Mostly the framework is fairly stable. There are two
areas you need to be careful about though.
1) The Context interface is the subect of heavy discussion on avalon-dev,
it isn't too much of a hardship to avoid using Context and for the next
few months that's what I'd do, as almost any use of Context will tie the
project to a particular container. Use Service instead. Context often
makes more sense intuitively, but the framework contract is as yet
unclear.
2) Using the Avalon framework also means using an Avalon container.
At the moment I'd recommend either Fortress (soon to be officialy
'released', but currently being used in production) or Phoenix, the
workhorse of Avalon containers. Fortress is much more 'wave of the
future' than Phoenix, and doesn't make the assumptions of very coarse
granularity that Phoenix does.
As another poster said, Avalon helps you give more attention to the
components by saving energy otherwise spent writing glue. Watching a
container assemble your application is pretty satisfying!
Regards,
Gary
[2002-12-11 05:43 -0800] Vladimir R. Bossicard ([EMAIL PROTECTED]) wrote:
>
> > I feel Avalon is overkill for what we need: configuration of components is
> > only a minor issue in Xindice, and the current framework works fine IMHO...
>
> I forgot 'e.g.' when talking about configuration. From what I've seen,
> the configuration doesn't currently handle more complicated
> configurations (multiple children with the same name).
>
> Of course you can always spend some time enhancing the Xindice class but
> I prefer to use what's already out there.
>
> And the configuration is only an example. I have no experience with
> Avalon but I think that it can bring more than just the configuration.
>
> -Vladimir
>
> --
> Vladimir R. Bossicard
> Apache Xindice - http://xml.apache.org/xindice
>
>
>
