title: Startup Deployment Architecture- Running Glassfish V3 Prelude without Apache
body: <p>So am I crazy for considering doing a beta/production release on Glassfish V3 Prelude?
  Since all of my content is dynamic, I'm not even thinking of bothering to set up apache in front either.  Doing so complicates the setup by requiring something like AJP or mod_jk and will not offer us much in terms of capability.</p>
  
  <p>So there will be three war files on deployment.
  3 JNDI data sources with about 90 connections parked, scaling up to 160 to a PGSQL datastore....</p>
  
  <p>The three wars comprise a CMS system and a grails application?</p>
  
  <p>Is my logic fatally flawed that I don't need to put apache in front of this setup?</p>