On Thu, Jun 27, 2013 at 04:18:40PM -0400, John Burwell wrote: > All, > > I am +1 for Java7. However, I would like to propose ridding > ourselves of Tomcat entirely and embedding a network stack such as > Netty (http://netty.io) with a servlet bridge. We have one JSP in > the system that generates JSON resources. It could be easily > eliminated with a simple servlet that generates JSON from a > ResourceBundle. Outside of this JSP. I don't see any other > requirements for a JEE container besides hosting a servlet. We > would gain a far simpler, self-contained deployment model (a single > jar). Additionally, we would gain greater control of the startup > and shutdown lifecycle, as well as, threading dynamics. If there is > interest in this approach, I have thoughts on how to achieve this > embedding and create a lightweight daemon framework that could be > used for all CloudStack daemons. > > As an aside, I also think we should replace our hand-rolled NIO code > with Netty as well. >
John - could you break this and other thoughts down a little more in what's involved? Perhaps into its own thread. I don't know Netty. And my J2EE is shaky at best. It's been a previous wish on this list to have the packaging of cloudstack into a single easily deployable war instead of all the complicated packaging we do. So I'd like to hear more of that and other issues you describe. -- Prasanna., ------------------------ Powered by BigRock.com
