Well I guess that answers my question. Jetty it is.
On 5/9/08, Frank Neslon <
frank.neslon@...> wrote:
>
> Hello,
> So I had the idea that I would like to deploy my application with Tomcat
> 'built in'. The goal is to just consolodate everything into one spot
> instead of scattering components all over the system. I keep reading about
> how Tomcat is 'embeddable', but I'm just not understanding something. I
> find several code samples about how to start up Tomcat from Java code using
> the 'Embedded' class, but I don't see what the file structure would look
> like if it were embedded. I keep reading that you need to deploy your app
> as a WAR in embedded Tomcat... but isn't this embedding your app inside of
> Tomcat instead of embedding Tomcat in your app?
>
> In other words, it just seems as if people are just packaging their app
> into a WAR, distributing full blown tomcat (in its default directory
> structure), then starting up Tomcat from a custom Java class instead of
> using the default startup options. Am I wrong? If not, then how is that
> considered embedded? If I am wrong, then could somebody show me a sample
> dir/file structure of an embedded Tomcat? Like I would expect to see
> Tomcat jars in their app's own lib directory, a way to point Tomcat to their
> own context.xml file in their project's file structure, etc.
>
> Any pointers to clear my head would be much appreciated! Thanks
>
