Thom Park wrote:
>
> Wow!
>
> I'm impressed - that looks pretty good for a default case but, what if I
> want
> tweak and tune my web app to use things like custom loggers or realms or
> even
> valves or listeners?
>
> I guess in that case I need to edit the server.xml directly wouldn't you
> say?
>
> What happens if my WebAppDeploy command matches an already defined webapp,
> will it
> override the existing one or just notice that it's already there and ignore
> the webappdeploy
> request.
>
> What happens if they conflict, ie.
> WebAppDeploy says the following:
>
> WebAppDeploy example.jar myConnection /servlet-examples/
>
> but my server.xml entry is something like
>
> <Context path="/servlet-examples", docBase="example_two", debug="99">
> <Realm className="myRealm">
> </Realm>
> </Context>
>
> Now I have two jar/webapp folders referring to the same path name and am
> looking
> at a potentially nasty conflict.
>
> Will the Warp handler object to this?
I have tried to deploy an existing application it seems it works. (As least I
think it does!).
>
> -Thom
>
> p.s. Damn good job though - it looks much simpler to manage that mod_jk -
mod_jk relies on the Tomcat server.xml, and mod_jk manage is improving a lot.
> now, how about
> load balancing ;-)
>
> -----Original Message-----
> From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 19, 2001 8:20 AM
> To: [EMAIL PROTECTED]
> Subject: Re: cvs commit: jakarta-tomcat-connectors/webapp/lib
> pr_warp_config.c
>
> Thom Park at [EMAIL PROTECTED] wrote:
>
> > Pier,
> >
> > I'm curious and appear to be too thick to understand exactly what the
> > WebAppDeploy step does with the webAppConnector, could you find some time
> in
> > your extremely busy schedule to jot down a few notes w.r.t. the what the
> > WebAppDeploy/configure step does exactly.
> >
> > I'm curious to know what information is passed between tomcat and apache
> in
> > that stage.
>
> Oh, simple... In the web-server configuration file you have something like:
>
> WebAppConnection myConnection warp localhost:8008
> WebAppDeploy example.jar myConnection /servlet-examples/
>
> Basically you configure a warp connection between Apache and Tomcat (first
> line), and over that connection you "deploy" a web application:
>
> Specifically what goes on, is that Apache tells to Tomcat that there should
> be a web application in its directories, in a file called "example.jar", and
> that should be deployed under the "/servlet-examples/" URL path (it's
> Context path). Tomcat finds the example.jar file, unpacks it, deploys it
> into the appropriate host (which is derived from Apache's VirtualHost
> directive), and is ready to process requests...
>
> So you don't have to configure the same thing twice :)
>
> Actually, my server.xml file for Tomcat is something like:
>
> <Server ....>
> <Service ....>
> <Connector className="....WarpConnector" port="8008" ..../>
> <Engine ..../>
> </Service>
> </Server>
>
> SIX LINES :)
>
> Pier
