Yes, I agree, Apache is an unnecessary complication for the moment and I am focused now on getting things to work through port 8080.

But Tomcat does serve up pages when I run the app through Apache---for one thing, the error messages are Tomcat-generated, not Apache, and for another, the servlets do work, which Apache cannot make happen without Tomcat.

I don't fully understand the invoker servlet myself, but here's what I think I know:

The invoker mapping only applies to servlets, not html or jsps, and the servlets are working (at least through Apache). If the invoker mapping specifies /servlets/* then "servlets" must be included in the URL. By taking it out of the invoker mapping, it does not need to be included in the URL. So, http://localhost/servlets/do_something is required if the mapping is as you say it should be, and http://localhost/do_something is the URL if the mapping is as I have it.

Is that not correct?

Jerry

Parsons Technical Services wrote:

Tomcat manager shows EBook is running. And, when I request it through
Apache, Tomcat does serve it up. When I request it through port 8080,
Tomcat says it's not available:


I suggest for now you forget running via Apache totally, since if it is
not working directly from Tomcat, it cannot be running via Apache. What
you see Tomcat is serving via Apache, actually it is not, rather the
Apache itself is serving it.

You say Tomcat manager shows EBook is running, did you run
localhost:8080//manager/list? Can you post the result of the url?




Jerry,


I think BAO is right about apache here.

I have a stand alone setup and did a quick test of something. You have in
your web.xml:

 <servlet-mapping>
     <servlet-name>invoker</servlet-name>
     <url-pattern>/*</url-pattern>
  </servlet-mapping>

When I set mine to this I get 404 resource not found.
Curiously, even though it gave a 404 resource not found, the manager showed
it running.

But with this it works fine.

 <servlet-mapping>
     <servlet-name>invoker</servlet-name>
     <url-pattern>/servlet/*</url-pattern>
  </servlet-mapping>

I had this same problem myself. Sorry I didn't spot it sooner.

Doug



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to