Number of X's up to 5 shows the intensity of belief lack of any is a lack of belief in anything.
> Components are more than code. > [ ] Correct > [ ] Incorrect I'd rather say components should be POJO's or beans. Where this falls under your poll I get confused but trying to get in your head I think you're asking if components should be Plain Old Java Objects right? If so I say yes. But the reality is no. > Components should come in "a box", dropped in place and used without even > need to look at it. > [X] Correct > [ ] Incorrect Call me when you find anything meeting this panacea. I don't think it exists - hope it will one day. > Simplicity for Component User more important than simplicity for Container > Developer. > [XXXXX] Correct > [ ] Incorrect I emphatically believe in it! > Simplicity for Component Author more important than simplicity for > Container > Developer. > [XXXXX] Correct > [ ] Incorrect I emphatically believe in this too! > Simplicity for Component User more important than simplicity for Component > Author. > [XXX] Correct > [ ] Incorrect Again I agree strongly > Without a large Component Repository, COP is pretty meaningless. > [ ] Correct > [ ] Incorrect Don't know about this need to think it over a bit. It seems like too strong of a statement right now. > COP is not the same as Java classes defined over an API. I.e. just because > you > can instantiate it, doesn't mean it is a Component. > [X] Correct > [X] Incorrect COP considers organization and services built on these components. Component can be a POJO too I feel. > Avalon is about a domain-neutral server framework.[1][2] > [XXX] Correct > [ ] Incorrect > Components should be runtime replacable. A true server doesn't need > restart. > [XX] Correct > [ ] Incorrect Nice feature but not a must have. > Avalon-compliant Components could be made to work in non-Avalon-compliant > containers, effectively running as POJOs, by the Component Author. > [ ] Correct > [ ] Incorrect The other direction is much easier actually. POJO + Wrapper -> Avalon Component This is how I'm building Eve. I'm not going to deal with another container switch so I'm making Eve components all POJOs and container neutral with the primary container of choice being Merlin. But wrappers can be made for each project. Take a look at this SVN structure document here: http://incubator.apache.org/directory/subprojects/eve/source-layout.html here's more on the COP approach: http://incubator.apache.org/directory/subprojects/eve/components.html > These are values that I carry dearly, without mentioning any approach, > design Same here but there should always be room for new ideas and it's a great skill to sit back and really listen. I've learned so much but finally at the age of 30 figuring out just how to do that. You guys are gods to me and playing at Avalon is like being on Olympus. Let's keep it fun. > or implementation aspects of our community. As you may understand, they > are > all formulated in such a way I will answer "Correct" to all of them > > I would also appreciate that no elaboration is given in the response mail, > just to keep it clean. Post those separately. OOooops ok I'll send this out and re-respond with the [POLL] in it. You should have said this in the beginning. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
