revised message: ---------------------------------
All, lately the avalon-dev list has been through a storm of ideas for improving Avalon Framework. During this brainstorming session we have come up with some fairly good ideas (*we* think so anyway) - some of them quite radical, some more conservative. Will you like them? Well, that's the problem. We have no idea if you - the users of Avalon - like the ideas, because we lack your input. What parts of Avalon do you really like? Which parts need improvement? Of special interest to us is the view of the "total newbie". What was/is the greatest problem you faced when you first tried to use Avalon? Lack of documentation? The size of the project? The lack of examples? If you are not using Avalon, but have made your way over here to evaluate the project: What will it take for you to start using it? Also, general comments on using Avalon are more than welcome. What were your greatest challenges in migrating your current archictecure to Avalon? How did you overcome them? Below is a short list of things we are either doing or considering. Feel more than free to comment on any of these. * we are revising the docs to be easier to digest for the average java developer * we are moving the parts of Avalon Excalibur that are of use outside avalon to the commons project * We are defining container contracts better so that any component written to Avalon specification will run in any container (the container is the thing that hosts components, one example is Avalon Phoenix) * we are clarifying (for ourselves and in documentation) the relationships between the different containers * we are working on making simpler containers, like one that is optimised for just handling a single component * We are implementing a standard meta-data system to help ensure a secure environment, and allow complex component mappings. thank you very much for taking the time to provide us with the vital feedback to make Avalon even better! best regards, - The Avalon Developers --------------------------------- someone could edit, post to -users, and then we can reference it in the newsletter? cheers, - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
