[clug] [glug] tomcat problems

[Rousak, Boris]

Thank for this. These articles are proving very useful indeed. :)
Boris

-----Original Message-----
From: Antti.Roppola at brs.gov.au [mailto:Antti.Roppola at brs.gov.au]
Sent: Friday, 9 May 2003 9:39 AM
To: richard_c at tpg.com.au; Boris.Rousak at actewagl.com.au
Cc: linux at lists.samba.org
Subject: RE: [clug] [glug] tomcat problems


I found these articles useful background in what's going on.
Nice and concise.

	http://www.onjava.com/pub/ct/33

Next time I'll read them *before* I set the server up. :o)

(For a basic overview, read the first three at the bottom of the page;
 which cover description, installation and application deployment)

Cheers,

Antti

-----Original Message-----
From: Richard Cottrill [mailto:richard_c at tpg.com.au]
Sent: Thursday, 8 May 2003 8:20 PM
To: Rousak, Boris
Cc: 'GLUG'
Subject: Re: [clug] [glug] tomcat problems


Rousak, Boris wrote:
<snip>
> word?). Has anyone out there played with tomcat or knows of any tutorials
> out on the net that explain in lamens terms how get tomcat to compile
> programs. I would really appreciate any info or comments at this point.
<snip>

Tomcat compiling programs? I don't think so (well, not unless you want 
to get pedantic about JIT compilers, but then it's not Tomcat anyway). 
I'm not an expert on Tomcat configuration, but I believe you'll need 
finished class/jar files to work with; preferably a war file.

I have done some servlet deployment/fiddling in the past, but I'm now 
sufficiently rusty I can't give specific instructions.

 From memory, you need to add a section or two to the top-level Tomcat 
configuration file, and/or a trivial (almost empty) configuration file 
in the servlet's directory.

I think that you can also just specify a war file (if available) through 
the management interface and it will deploy it; but this will not be 
written to the config file, therefore it will not survive a restart.

The Tomcat doco is a bit obtuse, but it is quite complete - when you 
find the phrase that's helpful.

Richard


************************************************************************
*PLEASE NOTE*  This email and any attachments may
be confidential. If received in error, please delete all 
copies and advise the sender. The reproduction or 
dissemination of this email or its attachments is 
prohibited without the consent of the sender.

WARNING RE VIRUSES:  Our computer systems sweep
outgoing email to guard against viruses, but no warranty 
is given that this email or its attachments are virus free. 
Before opening or using attachments, please check for 
viruses.  Our liability is limited to the re-supply of any 
affected attachments.

Any views expressed in this message are those of the 
individual sender, except where the sender expressly,
and with authority, states them to be the views of the 
organisation.
************************************************************************