Do you think avalon should provide declarative-style stuff? Why? How?
I think yes. The "why-question" is easily answered: because it's easier to use and maintain. There is a reason that XSLT has become a success. The "how-question" is not so easily answered.
I think the first step is to ask what in Avalon do we want to specify in a declarative way? In my eyes the assembly process, where different components are taken and assembled to a larger application, is a candidate.
The next thing is that there should be some kind of generic and implicit mapping from Avalon components to an XML representation. The XML then should be used as a replacement for scripting and it should be processed in a declarative way so that the Java component is called and does the work.
I know this is pretty vague at this point :)
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
