On Thu, 28 Jun 2001 19:15, you wrote:
> OH SORRY... I didn't want to say that you gave advice with TWO servlet tags
> - no YOU DIDN'T...
(o: no worries...
> The fact that two are too much wasn't known to me - you
> know, example of web.xml is the only thing I have to learn from. ;-)))
> This was web.xml of one of my mate in work - I was just trying to let it
> run as admin of Tomcat ;-)...
> Now I can see that I have to write it from scratch or something... ;-)
Have you got a copy of the (2.2) spec? It has a reasonably readable (IMHO)
overview of the web.xml dtd. Might clear up a few things. If you're
interested in buying a book - my first introduction to servlets was
O'Reilly's "Java Servlet Programming". Recommend it as a good intro,
although having said that I cant remember it covering the web.xml in detail
(not to say it doesn't).
> So - after your last mail I woke up and I'm checking logs now... but all at
> all - the only thing I see is in mod_jk.log well known two lines:
Ahh yes - you'll need to edit your server.xml. Have a look for tc_log -
there's a comment there saying put in path="logs/tomcat.log" to get more
logging... do that. otherwise your logging is going to stdout (I think).
Hopefully that will give you some more info. You can also crank up the debug
levels in there.
> Another "so" - so where is the differences between Apache-mod_jk-Tomcat and
> standalone Tomcat? I mean differences in servlet processing. On
> localhost:8080 everything runs perfectly and via virtual host of Apache and
> mod_jk... only jsp. But - as I can see now - servlet request is redirected
> - jk_uri_worker_map can't resolve it and Apache then sends obvious Not
> found. Hm...
I think it would be worth taking a few steps back and following the example
to the letter. In the doco there's a good walk through of how to get it
working using mod_jk.conf-auto. Have you been able to get it working without
virtuals at the apache end?
cheers
dim
