RE: Using JkMount with mod_jk question...
Thanks for the reply, I think. The configurations I have have been working since tomcat 3.1. They work on tomcat 4 with mod_jk. I see no reason to change them, especially considering the amount of time I wasted trying to get mod_webapp to work, and the amount of posts to this list from people having problems when changing their configuration to something new. The JkMount directives may be redundant, I'm not worried about it. They work. John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 6:56 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... On Thu, 20 Jun 2002, Turner, John wrote: Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. Maybe I can add a little here. A long time ago in a galaxy far away, servlets used to be called with URL's like http://www.domain.com/servlet/ServletName;, where ServletName was the actual name of the servlet class. servlet/ was a virtual directory that told the servlet container (servlet engine back then) to find the named servlet. Of course, the web server had to be told to pass URL's with servlet/ in them to the servlet container. That was before they came up with the idea of defining servlets in the web.xml file, and specifying servlet-mapping's to allow url-pattern's to point to these defined servlets. Then you could define a servlet dothis that was actually ServletName, and with the appropriate mappings, you could use a URL like http://www.domain.com/dothis;. Now, I don't recall what the spec has to say about this, that is, whether it requires/allows/disallows using the old style URL's with servlet/ and the actual servlet class name. But some people think it's a good idea not to use them, in fact, even to disable it, such that you can only reach servlets that have been defined in web.xml. In some ways, it allows more control and greater security. Anyway, the JkMount /servlet ajp13 in the examples is a vestige of all this. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. Wouldn't specifying index.jps as a welcome-file in web.xml be a better way of doing this? -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
Thanks for the clarification John and Milt, I appreciate it. I am kind of curious though about the configuration of index.jsp on the apache side of things If I use a JkMount /*.jsp ajp13 directive will any jsp file in the Apache DocumentRoot be handled by Tomcat? Or does this just mean that any jsp file in $TOMCAT_HOME/webapps will be handled by tomcat? I'm assuming that JkMount / ajp13 means that / is relative to $TOMCAT_HOME/webapps, but I've found that I actually have to specify the subdirectories under $TOMCAT_HOME/webapps in order to have access to them. I guess my general confusion here is that it seems like the JkMount directive allows one to overlay parts/pieces of the $TOMCAT_HOME/webapps directory over top of the Apache DocumentRoot. Kind of analogous to creating a directory structure on a filesystem (e.g. /home) then mounting a new filesystem as /home and being able to see files from both at the same time (of course that's not the way it work). That's what it sounds like JkMount does. On Fri, 2002-06-21 at 08:49, Turner, John wrote: Thanks for the reply, I think. The configurations I have have been working since tomcat 3.1. They work on tomcat 4 with mod_jk. I see no reason to change them, especially considering the amount of time I wasted trying to get mod_webapp to work, and the amount of posts to this list from people having problems when changing their configuration to something new. The JkMount directives may be redundant, I'm not worried about it. They work. John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 6:56 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... On Thu, 20 Jun 2002, Turner, John wrote: Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. Maybe I can add a little here. A long time ago in a galaxy far away, servlets used to be called with URL's like http://www.domain.com/servlet/ServletName;, where ServletName was the actual name of the servlet class. servlet/ was a virtual directory that told the servlet container (servlet engine back then) to find the named servlet. Of course, the web server had to be told to pass URL's with servlet/ in them to the servlet container. That was before they came up with the idea of defining servlets in the web.xml file, and specifying servlet-mapping's to allow url-pattern's to point to these defined servlets. Then you could define a servlet dothis that was actually ServletName, and with the appropriate mappings, you could use a URL like http://www.domain.com/dothis;. Now, I don't recall what the spec has to say about this, that is, whether it requires/allows/disallows using the old style URL's with servlet/ and the actual servlet class name. But some people think it's a good idea not to use them, in fact, even to disable it, such that you can only reach servlets that have been defined in web.xml. In some ways, it allows more control and greater security. Anyway, the JkMount /servlet ajp13 in the examples is a vestige of all this. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. Wouldn't specifying index.jps as a welcome-file in web.xml be a better way of doing this? -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache
RE: Using JkMount with mod_jk question...
Sure, /*.jsp will send JSP files to tomcat. But apache doesn't know that index.jsp is a home page unless you tell it so in httpd.conf: Directory /web/test/jsp Options Indexes FollowSymLinks DirectoryIndex index.html index.htm index.jsp /Directory John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 10:17 AM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... Thanks for the clarification John and Milt, I appreciate it. I am kind of curious though about the configuration of index.jsp on the apache side of things If I use a JkMount /*.jsp ajp13 directive will any jsp file in the Apache DocumentRoot be handled by Tomcat? Or does this just mean that any jsp file in $TOMCAT_HOME/webapps will be handled by tomcat? I'm assuming that JkMount / ajp13 means that / is relative to $TOMCAT_HOME/webapps, but I've found that I actually have to specify the subdirectories under $TOMCAT_HOME/webapps in order to have access to them. I guess my general confusion here is that it seems like the JkMount directive allows one to overlay parts/pieces of the $TOMCAT_HOME/webapps directory over top of the Apache DocumentRoot. Kind of analogous to creating a directory structure on a filesystem (e.g. /home) then mounting a new filesystem as /home and being able to see files from both at the same time (of course that's not the way it work). That's what it sounds like JkMount does.
RE: Using JkMount with mod_jk question...
On Fri, 21 Jun 2002, Turner, John wrote: Thanks for the reply, I think. The configurations I have have been working since tomcat 3.1. They work on tomcat 4 with mod_jk. I see no reason to change them, especially considering the amount of time I wasted trying to get mod_webapp to work, and the amount of posts to this list from people having problems when changing their configuration to something new. The JkMount directives may be redundant, I'm not worried about it. They work. OK, that all makes sense. FWIW, I installed tomcat 4.0.3 and mod_webapp on a Solaris machine recently, and it took me only about a half-hour's worth of work. It was very simple and straightforward. So you might ask why I don't just go with mod_webapp now. A couple of reasons. First, the above was for a test/development environment, so I just wanted to get it going quickly, I didn't care so much about which connector I used. Now I need to install it in a production environment, so I want to use the best connector. Second, this is for AIX, and the tomcat site doesn't have AIX binaries for the connectors. It does have binaries for Solaris (both mod_webapp and mod_jk, IIRC). Regarding the possibly redundant JkMount directives, it would be nice to understand exactly what is going on with them, because there may be performance and/or security considerations. -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 6:56 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... On Thu, 20 Jun 2002, Turner, John wrote: Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. Maybe I can add a little here. A long time ago in a galaxy far away, servlets used to be called with URL's like http://www.domain.com/servlet/ServletName;, where ServletName was the actual name of the servlet class. servlet/ was a virtual directory that told the servlet container (servlet engine back then) to find the named servlet. Of course, the web server had to be told to pass URL's with servlet/ in them to the servlet container. That was before they came up with the idea of defining servlets in the web.xml file, and specifying servlet-mapping's to allow url-pattern's to point to these defined servlets. Then you could define a servlet dothis that was actually ServletName, and with the appropriate mappings, you could use a URL like http://www.domain.com/dothis;. Now, I don't recall what the spec has to say about this, that is, whether it requires/allows/disallows using the old style URL's with servlet/ and the actual servlet class name. But some people think it's a good idea not to use them, in fact, even to disable it, such that you can only reach servlets that have been defined in web.xml. In some ways, it allows more control and greater security. Anyway, the JkMount /servlet ajp13 in the examples is a vestige of all this. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. Wouldn't specifying index.jps as a welcome-file in web.xml be a better way of doing this? -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you
RE: Using JkMount with mod_jk question...
On Fri, 21 Jun 2002, Turner, John wrote: Sure, /*.jsp will send JSP files to tomcat. But apache doesn't know that index.jsp is a home page unless you tell it so in httpd.conf: Directory /web/test/jsp Options Indexes FollowSymLinks DirectoryIndex index.html index.htm index.jsp /Directory So is this something you actually have set up and are using? Is /web/test/jsp known to tomcat (i.e. as part of a context/web application)? Or are you allowing jsp's to appear outside of tomcat contexts/web applications? The thing I wonder about is how this all fits with the directory/web application structure as per the servlet/jsp spec. Basically, I believe the spec says that everything is set up as context/web application (and there's also the ROOT/default context), and the directory hierarchy has a certain structure (e.g. in terms of the WEB-INF, classes, lib directories and the web.xml file). Being able to have jsp's (and/or servlets) elsewhere might seem like a nice convenience, but is it going against the spec? Also, it seems mod_jk allows this, but not mod_webapp. -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Friday, June 21, 2002 10:17 AM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... Thanks for the clarification John and Milt, I appreciate it. I am kind of curious though about the configuration of index.jsp on the apache side of things If I use a JkMount /*.jsp ajp13 directive will any jsp file in the Apache DocumentRoot be handled by Tomcat? Or does this just mean that any jsp file in $TOMCAT_HOME/webapps will be handled by tomcat? I'm assuming that JkMount / ajp13 means that / is relative to $TOMCAT_HOME/webapps, but I've found that I actually have to specify the subdirectories under $TOMCAT_HOME/webapps in order to have access to them. I guess my general confusion here is that it seems like the JkMount directive allows one to overlay parts/pieces of the $TOMCAT_HOME/webapps directory over top of the Apache DocumentRoot. Kind of analogous to creating a directory structure on a filesystem (e.g. /home) then mounting a new filesystem as /home and being able to see files from both at the same time (of course that's not the way it work). That's what it sounds like JkMount does. Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
On 21 Jun 2002, Sean M Alderman wrote: Thanks for the clarification John and Milt, I appreciate it. I am kind of curious though about the configuration of index.jsp on the apache side of things If I use a JkMount /*.jsp ajp13 directive will any jsp file in the Apache DocumentRoot be handled by Tomcat? Or does this just mean that any jsp file in $TOMCAT_HOME/webapps will be handled by tomcat? Well, the mod_jk documentation (and source) refers to the first argument to JkMount as a URL prefix. This suggests that it's the first piece of the URL (after any server:port info). The first thing to note is that it's referring to something in the URL-space, not in the file-space. So I think it's confusing to ask what files (in the file-space) it's saying will be handled by Tomcat. Rather, I'd think in terms of what URL's it's saying should be handled by Tomcat, and what files those URL's will be mapped to. That is, what files Tomcat will look for. Anyway, by all this, I'd say it's neither of what you suggest above. Rather, I'd say it's to map all jsp files in Tomcat's ROOT (i.e. default) context (modified by whatever servlet-mapping's are in the ROOT context's web.xml file -- that's the other complication). Anyway, this can easily be verified (if you have a working mod_jk, which I don't yet; but as soon as I do, I'll try it :-). I'm assuming that JkMount / ajp13 means that / is relative to $TOMCAT_HOME/webapps, but I've found that I actually have to specify the subdirectories under $TOMCAT_HOME/webapps in order to have access to them. Well, again, think URL-space. I think this essentially tells Apache to have Tomcat handle everything (although I'm a bit unclear on the distinction between / and /*). But then that would suggest you wouldn't need to specify separate JkMount's for the subdirectories (i.e. contexts), so my understanding can't be 100% correct. Maybe there's some interaction here with how Tomcat determines the context. I guess my general confusion here is that it seems like the JkMount directive allows one to overlay parts/pieces of the $TOMCAT_HOME/webapps directory over top of the Apache DocumentRoot. Kind of analogous to creating a directory structure on a filesystem (e.g. /home) then mounting a new filesystem as /home and being able to see files from both at the same time (of course that's not the way it work). That's what it sounds like JkMount does. Well, again, I'd say think URL-space. JkMount's don't really have anything to do with file-space, they just say how URL's should be handled. So if it says some URL should be handled by Tomcat, any corresponding location in Apache's file-space would be blocked/unreachable. For example, suppose under Apache's DocumentRoot there is a subdirectory examples with a file index.html in it. If you refernce the URL http://www.domain.com/examples/index.html it will lead to that file. But if you have the following JkMount directive JkMount /examples ajp13 and/or JkMount /examples/* ajp13 (again, I'm not quite sure of the distinction -- and if anyone has more to say about it, I'd appreciate it) then the URL http://www.domain.com/examples/index.html will lead to the index.html file in the context examples under Tomcat, and the aforementioned directory/file under Apache's DocumentRoot will be blocked/unreachable. Again, you should be able to verify this pretty easuly. On Fri, 2002-06-21 at 08:49, Turner, John wrote: Thanks for the reply, I think. The configurations I have have been working since tomcat 3.1. They work on tomcat 4 with mod_jk. I see no reason to change them, especially considering the amount of time I wasted trying to get mod_webapp to work, and the amount of posts to this list from people having problems when changing their configuration to something new. The JkMount directives may be redundant, I'm not worried about it. They work. John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Milt Epstein [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 6:56 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... On Thu, 20 Jun 2002, Turner, John wrote: Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. Maybe I can add a little here. A long time ago in a galaxy far away, servlets used to be called with URL's like http://www.domain.com/servlet/ServletName;, where ServletName was the actual name of the servlet class. servlet
RE: Using JkMount with mod_jk question...
If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
On Thu, 20 Jun 2002, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Can you explain why you have the two of those there? Do they do something different? Are they both necessary? From what I can discern from the FD (fine documentation), the first argument to JkMount is the URL prefix* to match against when passing things to the named worker (the second argument). It seems the above two are (at least somewhat) redundant. *The FD says prefix, but that can't be literally true, because, as you show below with *.jsp, it can specify suffixes as well. So perhaps pattern is more accurate. Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Using JkMount with mod_jk question...
On Thu, 20 Jun 2002, Turner, John wrote: Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. Maybe I can add a little here. A long time ago in a galaxy far away, servlets used to be called with URL's like http://www.domain.com/servlet/ServletName;, where ServletName was the actual name of the servlet class. servlet/ was a virtual directory that told the servlet container (servlet engine back then) to find the named servlet. Of course, the web server had to be told to pass URL's with servlet/ in them to the servlet container. That was before they came up with the idea of defining servlets in the web.xml file, and specifying servlet-mapping's to allow url-pattern's to point to these defined servlets. Then you could define a servlet dothis that was actually ServletName, and with the appropriate mappings, you could use a URL like http://www.domain.com/dothis;. Now, I don't recall what the spec has to say about this, that is, whether it requires/allows/disallows using the old style URL's with servlet/ and the actual servlet class name. But some people think it's a good idea not to use them, in fact, even to disable it, such that you can only reach servlets that have been defined in web.xml. In some ways, it allows more control and greater security. Anyway, the JkMount /servlet ajp13 in the examples is a vestige of all this. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. Wouldn't specifying index.jps as a welcome-file in web.xml be a better way of doing this? -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. Milt Epstein Research Programmer Systems and Technology Services (STS) Campus Information Technologies and Educational Services (CITES) University of Illinois at Urbana-Champaign (UIUC) [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Using JkMount with mod_jk question...
PLEASE do not email me any more. I am not a member of Tomcat, never have been. I have emailed them several times asked them to remove me from their members email list, but they have failed to do so, that is why I am asking you to do so. Thank you! - Original Message - From: Turner, John [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, June 20, 2002 4:16 PM Subject: RE: Using JkMount with mod_jk question... Good questions, all. It doesn't matter to me if servlet shows up in the URL (it matters to some people/projects) so I haven't worried about it. I think using servlet is just a convention...in my projects, I usually prepend the application name to it. For example, if the application is XYZ, then I use XYZServlet to denote that application's servlet directory, not servlet. Same goes for company names...if you have company ABC using a particular app, you might say ABCServlet. I think, if you tell apache that index.jsp is a valid starting page, you can just call /mydir instead of /mydir/ and have that JSP page redirect wherever you want. John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 5:00 PM To: Tomcat Users List Subject: RE: Using JkMount with mod_jk question... So I need to shut apache down, change the config and restart everytime I deploy a new webapp? OK...so I did what you said, and now I can point my browser to http://host/examples/ and it shows me a directory listing like page...which is better than I saw before. If I do http://host/examples/jsp/ I get the index.html page I expect to get. Great! so I put a JkMount /myApp ajp13 in httpd.conf and if I have $TOMCAT_HOME/webapps/myApp.war the app will deploy and I should be able to visit http://host/myApp and run the app. One last stupid question... So what's JkMount /servlet ajp13 for in the examples?...I mean is /servlet specific or should there be an additional note for stupid guys like me who don't get that /servlet should be replaced with actual real servlets on your system? On Thu, 2002-06-20 at 16:44, Turner, John wrote: If you were using mod_jk, apache, and tomcat, and wanted to reach the tomcat examples (default install) on port 80 (instead of 8080 or whatever), this would work: JkMount /examples ajp13 JkMount /examples/* ajp13 Season to taste, that is, you could easily put /path/*.jsp or some other expression...it doesn't have to be /*. HTH John Turner [EMAIL PROTECTED] http://www.aas.com -Original Message- From: Sean M Alderman [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 20, 2002 4:38 PM To: Tomcat Users List Subject: Using JkMount with mod_jk question... Hi again, Is there a good source to read for understanding how the JkMount path relates to $TOMCAT_HOME/webapps ? Everytime I put a url in that works for the standalone server, I get a 404 when I try it via the AJP connector. -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Sean M. Alderman ITRACK Systems Analyst PACE/NCI - NASA Glenn Research Center (216) 433-2795 Calling a windowed operating system Windows is like naming an automobile Wheels. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
