I'm not sure I get the problem. One interpretation is you have something (a static page, CGI / hander generated output) that contains a link to a URL which is in turn handled by a Java servlet ... somewhere else. In which case, a link to the URL handled by that servlet should be sufficient. Another interpretation is that you have the code for a Java servlet that you'd like to be able to execute when someone accesses a specific URL on your site.

Apache httpd can't do this on its own. Java servlets must run inside a servlet container, such as Tomcat. Now, what you can do is set up a servlet container, and set Apache httpd to run "in front of" the servlet container, and to set up Apache to pass requests for certain URLs onto the servlet container. How to do that with Tomcat is documented on the Tomcat site (op cit.); other servlet containers do it in different ways. But a discussion of setting up Tomcat and Apache really is a topic for another site.

HTH.

Sorry for the confusion.

We're moving a static form from an IIE site on which is a submit button that calls an existing servlet. We're trying to eliminate the IIE site. I think vet's LWP call is what we're looking for. I was actually asking the question for a friend and the more I think about it, the more I'm realizing that I'm going to have to dig into the issue farther and see for myself the exact configuration he's attempting.

coreolyn

I have a mod perl site that contains a page that...

Just use LWP to call the servlet from your mod_perl handler.