Since there are multiple point, I address them all here: > This is the wrong place for this discussion. Please > use the online forums.
Since no one who know anything read or reply to those forum, this kind of like say "go away". > JBoss 3.0 includes a servlet container, Jetty This one really puzzle me. You abandon Tomcat/Catalina for Jetty. Jetty implement Servlet 2.2, not 2.3. Jetty can not even run Struts. None of the security stuff work with Jetty, or at least if it do it not documented how. Why is Jetty priority over Catalina? I think maybe 10 people in the world use Jetty. Tomcat/Catalina used by thousands. > This is alpha software, use 2.x Generally, alpha software is mostly feature complete. For the next version, you would hope that the alpha would at least work 80% as functions as the previous version. Instead, you seem to have rewrite all the code, and now stuff that used to work either not work or work in some way that require reading the source code to figure out how. > We have to rewrite code because Sun makes many changes to spec. If the last version was so great, why you have to rearchitect everything this time? A good architecture should support change. You not even close to a usable product if you break every existing user with every new release. BEA not have to rewrite all code and screw all user for J2EE 1.3. > Use 2.4 2.4 is not supported. No one answer any question about 2.4 on user forums. It dead product with bug that never be fixed. __________________________________________________ Do You Yahoo!? Send your FREE holiday greetings online! http://greetings.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
