Can't guess about your code without more detail but make sure whatever ports
you are talking on are allowed through your firewall. Also if your systems
have files listing local machines addresses that they use to get dns numbers
without a server lookup, you could be feeding off of those on you net
I don't think it is so hard to do the java part, and I suspect that the
tomcat part isn't that hard either, but I am really criticising the
documentation more than anything else. I am not opposed to extra keystrokes
for benefits of java, but I do really dislike reading page after irrelevant
page h
act this is how my apps work -- servlets take all user input, and do
all
> the processing / database work / error-intensive / security-conscious
tasks,
> etc. -- and then forward the request to a simple display-only jsp (after
> putting items into the request scope hashtable). This is k
ost invariably use Tomcat as a standalone server, for your average
> website where you might use something like php or whatever, but you want a
> more "robust" application design, it's fine.
>
> Content negotiation is a pit I have not stepped into, maybe someone else
can
You can also rewrite *.jsp to /jsp/*.jsp
Then use ProxyPass and ProxyPassReverse to serv up any /jsp/ from a local
tomcat instance.
That avoids connectors entirely.
- Original Message -
From: "Nikola Milutinovic" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Mond
Hi,
I've been playing with tomcat a little bit, I like JSP, and it does that well, but
when it comes to operating on it's own as a web server, I have been a bit frustrated.
I don't seem to be able to find mechanisms in Tomcat that support things like URL
rewriting or content negotiation. Grant
