Sorry, ApJservAction appears to be some sort of framework for
handlers for different extensioned files. Sorta what the JSP runner
is for jsp's. They created their own tag library.. I want to move away
from it and go to standard stuff. Especially since they still have just
about as many servlets as they have their-answer-to-jsp-files.
I believe mod_jserv is suppose to continue to be supported with 3.2.
I'm thinking I might have to stick with it for the moment...though
lamentfully. I wish there were a better set of documentation clearly
explaining the transition from mod_jserv and tomcat 3.1 (the nuances
that change each time). I searched like mad for this ApJservAction stuff.
-andy
James Devenish wrote:
> On Fri, Dec 08, 2000 at 02:08:02PM -0800, Andrew Oliver wrote:
> > I'm working with some 3rd party code that uses
> > ApJServAction (the servlets run in Jserv), I'm
> > attempting to convert over to Tomcat and Ajp13.
> > However, I'm not sure how to set this up or even
> > IF it can be setup. Is there a way to do something
> > similar with the new connector/tomcat?
> >
> > Secondly, if not, is there a way to use both tomcat
> > and jserv concurrently (point new code to one and old
> > code to the other and replace them as we rewrite it)?
>
> This can be the stuff nightmares are made of! You may find that Tomcat
> 3.2 is very strict about how these things are done, due to the
> simplistic and strict nature of the Java Servlet Specification (which
> has become a bit narrow minded).
>
> Firstly, I have not used ApJServActions so I don't *know* the answer.
> I will assume that ApJServActions map Apache URLs to servlets?
> In that case, you need to modify (or create) a web.xml in your web
> application's context directory and add:
>
> <servlet-mapping>
> <servlet-name>
> invoker
> </servlet-name>
> <url-pattern>
> /path/*
> </url-pattern>
> </servlet-mapping>
>
> where /path/* is the URL (not corresponding to an existing filesystem
> directory) which will achieve this:
>
> http://tomcat.host:8080/web_app/path/ServletName
>
> will execute ../tomcat/webapps/web_app/WEB-INF/classes/ServletName.class
>
> The /path/* can be a wildcard match like that, or a *.extension wildcard
> match or a literal match. I don't think it is possible to use other
> wildcard styles like /path/*.extension.
>
> I don't think you can have mod_jserv and mod_jk running concurrently in
> Apache. However, mod_jserv will work with Tomcat 3.1 (though I'm not
> sure about Tomcat 3.2).
>
> Another thing you could try is using mod_proxy
> (http://httpd.apache.org/docs/mod/mod_proxy.html) to proxy requests from
>
> http://web.host/blah/ServletName
>
> through to
>
> http://web.host:8090/web_app/path/ServletName
>
> where :80 is your Apache with mod_jk and :8090 is a separate server
> config using mod_jserv. Or alternatively Proxy
>
> http://web.host/blah/ServletName
>
> through to
>
> http://web.host:8080/web_app/path/ServletName
>
> (ie. direct to Tomcat)
>
> Hope that helps (but as I say, i don't know what ApJServAction does, so
> I might be off track :)
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
