>On Friday, November 30, 2012 1:23:51 PM UTC+1, Joseph Ottinger wrote: >You guys do realize you're ignoring the Java EE definition, where a deployer's role is to actually tailor the deployment for a specific container, right?
I believe this is a sign of the times. We started from a situation where the choice of the container was prioritary, strategic and made to last for years. Porting a complex app to another container may still be a nightmare today, and a key reason to stick to the legacy. Now I hear good people say that a Tomcat instance with more than one app is an antipattern. AFAIK Grails ships an embedded Tomcat with every webapp unless told otherwise. I understand single-app-Tomcat is not exactly what this thread is about, but still I see analogies with the current-thread-relevant move to virtual servers on demand, clouds and stuff; because it all makes the container a lesser priority. The business case for moving heavy apps is growing and I think that therefore the case of self-sufficient apps is getting more important. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/0hDNX6_bSQ4J. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
