Trying to understand the concept of embedded Tomcat

[Frank Neslon]

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

[Frank Neslon]

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
>

[Filip Hanik - Dev Lists]

there are many ways of doing it,
one is 100% embedded, where you create all the components programmatically,
another one is to distribute a regular tomcat,
and you can use a hybrid model

Filip

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
>
>  
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 269.23.11/1422 - Release Date: 5/8/2008 5:24 PM
>  

---------------------------------------------------------------------
To start a new topic, e-mail: users@...
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...