And to add one more comment: with the current approach in Avalon configuration handling, it is still possible to implement the Ant approach on top of this (write an AbstractReflectionConfigurable, override .configure(..) method to call the relevant methods using reflection and let other people just extend your class), while you cannot really use the Avalon approach if you would have based the whole system on reflection from the very beginning.
So, I would say that Avalon approach is also more flexible :-) Neeme (also biased) PS this discussion is getting way too avalon specific for cocoon-dev... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
