While I like many of the ideas (http://www.freeroller.net/page/acoliver/20021202#interfaces_services_and_anonymous_classes) in the Avalon framework, I'm underwhelmed by the community surrounding it (which is on one long continuous feud caused by an overly theoretical project) and more so by the actual implementations.
If you need a high performance and stable container you'd be best advised towards JBoss rather than Avalon Phoenix or one of their OTHER containers. If you need persistance, etc... JBoss. The downside being of course that you'll have to deal with the disgusting interfaces and antipaterns of EJBs. However, my advice would be to learn from Avalon while using something else. (The next version of JBoss will allow you to use Plain Old Java Objects but thats too far away).
If you have any specific questions about either I'll do my best to answer them or forward them to someone who can. Perhaps Nicola will give an opposing viewpoint. (though perhaps not)
-Andy
Richard O. Hammer wrote:
I am starting to work with Apache Avalon <http://avalon.apache.org/>. This provides a container for components, for services. I am curious about how this container compares to the EJB containers (such as JBoss, BEA, Websphere Application Server) about which I've heard so much, but which I've never used.
Could someone who knows give a rundown of the differences and similarities, pros and cons?
Thank you, Rich Hammer
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
