jaaron,
It was more about Tomcat that Avalon, but yes it is true. Avalon (Phoenix) was the microkernel that came first. Our grand plan road-map has always been to assimilate just about every port listening service.http://jakarta.apache.org/avalon/apps/index.htmlSomeone correct me if I'm wrong but I believe JBoss initially looked into using
Are the applications on the above pages up-to-date? I noticed that Axis
wasn't mentioned at all.
Also, Avalon and the JBoss microkernel architecture seem very similar in
purpose. I'm curious what it is that Avalon users see as being the
difference?
Thanks!
Jonathan Carlson
Minneapolis, Minnesota
Avalon when the project started; however, JBoss was to be GPL'd while Avalon is
under the Apache License. JBoss is currently offered under the LGPL, so
apparently some attitudes about licensing changed.
JBoss is about 100 time better known that Avalon (or any subproject) now. Fact of life.
That said, JBoss from the start was to be a J2EE application server, while Avalon is more a framework for servers. I think it would be more accurate to say that Pheonix and JBoss have similiarities.Speaking of JBoss, has anyone ever gotten any of the JBoss MBeans to run within Pheonix? I say this knowing very little about Pheonix, but I think it should be possible to modify them or put a wrapper around them in some way. Wouldn't this give a whole new set of blocks for use within Pheonix?
That and Phoenix services inside JBoss are being looked at. - PAul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>