Well, at our company these changes are slowing the adoption of Seam, because I analyzed Seam's Tomcat features during the 1.2.1 times and was happy to see that you would just have to throw some EJB3 jars at it and you could package it as a straight war file. No container changes needed, nothing.
In other words, Seam was not as invasive to Tomcat as it is now. I know it is not a big thing to drop a shared lib in Tomcat, but try to convince some Spring zealots from the early days to modify their beloved production Tomcat. They will rant about how much superior and lightweight their friggin IoC container is. I would not have to listen to that, if I had the ability to just drop them a final war file ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092900#4092900 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092900 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
