> > 1. Why do I use Avalon? - I've been in huge EJB projects for years now. My conclusion: it's the wrong way to go. And for me Avalon is the true alternative here. - I was looking for a container which could be the basis for really reusable business components. I found it here - I was looking for a container which does a clear and strict separation between business logic and technology issues. I can reach that goal with Avalon => I like to create a productivity breakthrough with Avalon in building large business applications! > 2. What do I feel Avalon's mission to be?
1. Ease of use. Avalon will be "the" reference for how to build business applications with ease and fun. 2. stability (with references to Niclas post) Avalon will have "A strong Contract & Specification driven Component Oriented Programming model/platform/framework, with a Test Compatibility Kit (TCK) for each defined specification, for each the Components and the Containers respectively" so that enterprises can trust the specification and trust in not having endless migration costs. 3. separation of concerns Avalon will be the container which - has a clear separation of system and business application concerns - has a clear separation of business application concerns (presentation, process, assembly, core business components) - has a pluggable system architecture > 3. Where do I see Avalon by the end of 2004? Technically 1. Rock-solid component specification 2. excellent tool support 3. pluggable persistence-, process- and presentation support 4. basic business components out of the box 5. distributed containers 6. subject level security Community - More than 30 committers working at Avalon - More than 10 projects based on Merlin had started in the business area around the world - Avalon is under the top 20 of "influencing technologies" in the IT industry > 4. How do I feel about Avalon as an umbrella project vs. a single > product? Single product with a pluggable architecture (a bit like Eclipse) > 5. Should there be a formal framework specification? Yes. Let's start with it and let us always be careful when things are becoming "over specified"! > 6. If so, what should it consist of? > All we need for a "reuse contract". All the best Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
