Re: automatic deployment without server.xml - bad request

2010-12-03 Thread Pid
On 12/2/10 11:39 PM, Justin Case wrote: > But what do you think about the 400 > error? Is it really appropriate as answer in this setup? Well, 404 might be appropriate from the client's point of view. I think I remember the recent suggestion of a default ROOT application, used when no other is p

Re: automatic deployment without server.xml - bad request

2010-12-03 Thread Justin Case
> From: Markus Schönhaber > > Yes, it is an error. But in this case, I, too, consider the error erroneous. > A status code of 400 basically means that the request was syntactically > b0rked. But, as I understand it, that's not the problem here: the > request is syntactically fine - it fails be

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Markus Schönhaber
02.12.2010 20:44, Pid: > On 12/2/10 12:34 PM, Justin Case wrote: >>> From: Pid >>> If the request isn't being routed to your application, then without a >>> ROOT application the host hasn't got a mechanism to serve any response >>> other than an error. >> >> Error is fine, as long it's a 404 (a

RE: automatic deployment without server.xml - bad request

2010-12-02 Thread Caldarale, Charles R
> From: Justin Case [mailto:send_lotsa_spam_h...@yahoo.com] > Subject: Re: automatic deployment without server.xml - bad request > ...or maybe I should consider whether my application can be > both root AND answer to the context... Really, you *must* have a default webapp. Why do

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: Pid > > On 12/2/10 10:24 PM, Justin Case wrote: > > Yeah I probably will do that - but I will still regard it as a dirty hack... > > A ROOT app should be mandatory. It's not - yet :) so I'm all legal without. But what do you think about the 400 error? Is it really appropriate as ans

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Pid
On 12/2/10 10:24 PM, Justin Case wrote: > Yeah I probably will do that - but I will still regard it as a dirty hack... A ROOT app should be mandatory. p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: Pid > > On 12/2/10 12:34 PM, Justin Case wrote: > > Error is fine, as long it's a 404 (and not this enigmatic 400)... > > 400 isn't enigmatic and /is/ an error. ;) It IS an error indeed, but we're not talking about throwing just ANY random error number here :) 400 is a specific er

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Pid
On 12/2/10 12:34 PM, Justin Case wrote: >> From: Pid >> If the request isn't being routed to your application, then without a >> ROOT application the host hasn't got a mechanism to serve any response >> other than an error. > > Error is fine, as long it's a 404 (and not this enigmatic 400)...

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Pid
On 12/2/10 12:23 PM, Justin Case wrote: >> From: Pid >> This is either because your application is not deployed, or because the >> request path you're using does not match the actual request path deployed. >> >> When you start Tomcat, is there a message in the logs saying: >> >> 02-Dec-2010 10:

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: "Caldarale, Charles R" > > When you say "standalone context.xml", are you referring to a >element located in the webapp's META-INF/context.xml directory? Yes, that one. > Make sure you don't have a conf/Catalina/[host]/[appName].xml file, since > that > >will override anything i

RE: automatic deployment without server.xml - bad request

2010-12-02 Thread Caldarale, Charles R
> From: Justin Case [mailto:send_lotsa_spam_h...@yahoo.com] > Subject: Re: automatic deployment without server.xml - bad request > when I use the standalone context.xml it creates under > "work/Catalina/localhost" a directory com.mycompany.myapp > - which stays empty

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: Pid > If the request isn't being routed to your application, then without a > ROOT application the host hasn't got a mechanism to serve any response > other than an error. Error is fine, as long it's a 404 (and not this enigmatic 400)... Thank you, JC ---

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: Pid > This is either because your application is not deployed, or because the > request path you're using does not match the actual request path deployed. > > When you start Tomcat, is there a message in the logs saying: > > 02-Dec-2010 10:44:17 org.apache.catalina.startup.HostConfig

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Pid
On 12/2/10 9:01 AM, Justin Case wrote: >> From: "Caldarale, Charles R" > >> JSPs are only compiled upon first reference, not before. That results in a >> slight (usually very slight) pause for the first guy in, >> >> so if you want to pre-compile them, there is a script available to do so:

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Pid
On 12/2/10 10:00 AM, Justin Case wrote: >> From: Konstantin Kolinko > >> >> Just curious: why wtpwebapps? Eclipse IDE uses that name. > > Precisely :) Only because Eclipse publishes it there, so the name was kept. > No > other reason. > >> Try with recent 6.0.x (build it yourself), or 6.0.3

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: Konstantin Kolinko > > Just curious: why wtpwebapps? Eclipse IDE uses that name. Precisely :) Only because Eclipse publishes it there, so the name was kept. No other reason. > Try with recent 6.0.x (build it yourself), or 6.0.30 (when it comes > out), or 7.0.5 -- they will log such

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Konstantin Kolinko
2010/12/1 Justin Case : > >             deployOnStartup="false" >                name="localhost" unpackWARs="true" xmlNamespaceAware="false" >                xmlValidation="false"> >                                    directory="logs" pattern="common" prefix="access_log." >                    reso

Re: automatic deployment without server.xml - bad request

2010-12-02 Thread Justin Case
> From: "Caldarale, Charles R" > JSPs are only compiled upon first reference, not before. That results in a >slight (usually very slight) pause for the first guy in, > > so if you want to pre-compile them, there is a script available to do so: >http://tomcat.apache.org/tomcat-6.0-doc/jasper

RE: automatic deployment without server.xml - bad request

2010-12-01 Thread Caldarale, Charles R
> From: Justin Case [mailto:send_lotsa_spam_h...@yahoo.com] > Subject: Re: automatic deployment without server.xml - bad request >...and will it compile the JSPs as well? JSPs are only compiled upon first reference, not before. That results in a slight (usually very slight) paus

Re: automatic deployment without server.xml - bad request

2010-12-01 Thread Justin Case
First of all, thanks for your long answer. > Please read (carefully), the following documentation: Exactly from there I got the approach of "Copy unpacked directory hierarchy...". > Your docBase would only work if you have a directory > $CATALINA_BASE/com.mycompany.myapp. It works actually,

Re: automatic deployment without server.xml - bad request

2010-12-01 Thread Mark Eggers
Short answer: Please read (carefully), the following documentation: http://tomcat.apache.org/tomcat-6.0-doc/appdev/deployment.html Longer answer: 1. remove the docBase attribute from your Context Your docBase would only work if you have a directory $CATALINA_BASE/com.mycompany.myapp. 2. rem