Thanks!
So, from this, it says it's very slow, causes weird errors, and
generally should not be used. I can see why, since it starts a new
instance and shuts it down for every page load.
Is there another way to make changes show up right away?
If not, how do you do your code/test/release cycle?
So, I'm testing some stuff, and I have to restart the server for my
changes to servlets to show up. I've tried clearing the cache, but it
does not help.
Is there a way to not have to restart the server on my machine for each
change?
Thanks,
Mike.
--
Security Management Consulting
2501 Blue Ridg
So, could someone point me to the right docs for this.
I don't understand how to add a 'context', point it at a directory, and
have that load a default page to start a section of a site.
The httpd/apache equivalent would be creating a directory under the
document root, adding an index.html file,
