RE: WebAppDeploy Vs WebAppMount
jakarta.apache.org it's there. sorry but I looked into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src/ but I couldn't find anything related to mod_webapp I think you specify this in web.xml of the web application. but web.xml will relate to port 8080 (or whichever port tomcat listen to). Frankly am rather confused how come web.xml wiil relate to something in WebAppDeploy. It seem to me that both can do servlet to URL mapping but while web.xml will be serving servlets on port 8080, Webappdeploy will do it on port 80 and that the 1 am interested. Dom -Original Message- From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]] Sent: 30 January 2002 06:59 To: Tomcat Users List Subject: Re: WebAppDeploy Vs WebAppMount where do I get the latest source of mod_webapp? jakarta.apache.org it's there. Beside how do specify the mapping? What I want to be able to do is point my browser to: http://localhost/examples/HelloWorldExmample instead of having to do: http://localhost/examples/servlet/HelloWorldExmample How do I specify that in WebAppDeploy ? I think you specify this in web.xml of the web application. Nix. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: WebAppDeploy Vs WebAppMount
jakarta.apache.org it's there. sorry but I looked into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src/ but I couldn't find anything related to mod_webapp It usually accompanies the distribution of Tomcat. Haven't looked lately. I think you specify this in web.xml of the web application. but web.xml will relate to port 8080 (or whichever port tomcat listen to). There seams to be a misconception here. Port is set in $CATALINA_BASE/config/server.xml, while web.xml is in Context/WEB-INF/web.xml. web.xml sets up the particular context, dfining URL-to-servlet mappings, parameters, etc. Frankly am rather confused how come web.xml wiil relate something in WebAppDeploy. It won't, exactly. WARP is supposed to pick it up, the whole context. seem to me that both can do servlet to URL mapping but while web.xml will be serving servlets on port 8080, Webappdeploy will do it on port 80 and that the 1 am interested. Hmm, well, no, not exactly. WebAppDeploy does just URL-to-connection mapping, directing certain URLs to WARP connection, while Tomcat does the URL-to-servlet mapping. Tomcat has the final word, in any case. Nix.
RE: WebAppDeploy Vs WebAppMount
Hi, -Original Message- From: Cressatti, Dominique [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 1:05 PM To: Tomcat Users List Subject: RE: WebAppDeploy Vs WebAppMount jakarta.apache.org it's there. sorry but I looked into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src/ but I couldn't find anything related to mod_webapp I think you specify this in web.xml of the web application. but web.xml will relate to port 8080 (or whichever port tomcat listen to). Frankly am rather confused how come web.xml wiil relate to something in WebAppDeploy. It seem to me that both can do servlet to URL mapping but while web.xml will be serving servlets on port 8080, Webappdeploy will do it on port 80 and that the 1 am interested. If all you need is port 80 then there is no need in mod_webapp. You can just modify your server.xml to have TC listen to 80. Dom Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: WebAppDeploy Vs WebAppMount
Are you saying that in order to get something like: http://localhost/examples/HelloWorldExample working, I need to have something like: WebAppDeploy examples WarpConnection /examples in httpd.conf and have a URL-to-Servlet mapping in a web.xml? Dom -Original Message- From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]] Sent: 30 January 2002 13:39 To: Tomcat Users List Subject: Re: WebAppDeploy Vs WebAppMount jakarta.apache.org it's there. sorry but I looked into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src/ but I couldn't find anything related to mod_webapp It usually accompanies the distribution of Tomcat. Haven't looked lately. I think you specify this in web.xml of the web application. but web.xml will relate to port 8080 (or whichever port tomcat listen to). There seams to be a misconception here. Port is set in $CATALINA_BASE/config/server.xml, while web.xml is in Context/WEB-INF/web.xml. web.xml sets up the particular context, dfining URL-to-servlet mappings, parameters, etc. Frankly am rather confused how come web.xml wiil relate something in WebAppDeploy. It won't, exactly. WARP is supposed to pick it up, the whole context. seem to me that both can do servlet to URL mapping but while web.xml will be serving servlets on port 8080, Webappdeploy will do it on port 80 and that the 1 am interested. Hmm, well, no, not exactly. WebAppDeploy does just URL-to-connection mapping, directing certain URLs to WARP connection, while Tomcat does the URL-to-servlet mapping. Tomcat has the final word, in any case. Nix. -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: WebAppDeploy Vs WebAppMount
You can just modify your server.xml to have TC listen to 80. Thanks but I still want to serve static pages hence need to have apache. -Original Message- From: Anton Brazhnyk [mailto:[EMAIL PROTECTED]] Sent: 30 January 2002 14:48 To: Tomcat Users List Subject: RE: WebAppDeploy Vs WebAppMount Hi, -Original Message- From: Cressatti, Dominique [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 1:05 PM To: Tomcat Users List Subject: RE: WebAppDeploy Vs WebAppMount jakarta.apache.org it's there. sorry but I looked into http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src/ but I couldn't find anything related to mod_webapp I think you specify this in web.xml of the web application. but web.xml will relate to port 8080 (or whichever port tomcat listen to). Frankly am rather confused how come web.xml wiil relate to something in WebAppDeploy. It seem to me that both can do servlet to URL mapping but while web.xml will be serving servlets on port 8080, Webappdeploy will do it on port 80 and that the 1 am interested. If all you need is port 80 then there is no need in mod_webapp. You can just modify your server.xml to have TC listen to 80. Dom Anton -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: WebAppDeploy Vs WebAppMount
You can just modify your server.xml to have TC listen to 80. Thanks but I still want to serve static pages hence need to have apache. NB: TC will server static pages quite happily. Now, I've *just* been discussing this for implementation at my current contract. We are wondering what the load difference is likely to be on the whole machine. We serve approximately the same number of .jsp and .png requests, plus a tiny amount of html. Has anyone implemented this structure and do they have any opinions? J. -- You're only jealous cos the little penguins are talking to me. *** For more information on Ordnance Survey products and services, visit our web site at http://www.ordnancesurvey.co.uk *** -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
WebAppDeploy Vs WebAppMount
what's the difference between the 2? I grabed what I think was the lastest mod_webapp module ( http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.2-b2/rpms/) and it added the following in my httpd.conf WebAppConnection WarpConnection warp localhost:8008 WebAppDeploy examples WarpConnection /examples IfModule mod_webapp.c WebAppConnection warpConnection warp localhost:8008 WebAppMount examples warpConnection /examples/ WebAppMount manager warpConnection /manager/ WebAppMount webdav warpConnection /webdav/ /IfModule whoever set up the rpm, there was already an error when tried to start apache. Apache complained about the same connection name. It appear that the connection name is NOT case sensitive. Anyway after I changed 1of the connection name to avoid the duplicate apache came with the error: Syntax error on line 1453 of /etc/httpd/conf/httpd.conf: Invalid command 'WebAppMount', perhaps mis-spelled or defined by a module not in cluded in the server configuration Has anybody else encountered the same problem? The reason I wanted a recent version of mod_webapp is that it is supposed to support specification of complete path as David Smith mentionned in post (BTW David, I couldn't find any mod_webapp in the nightly snapshot, so that's why I used the rpm). Best regards. Dom Dominique Cressatti Newlook/PC/Network support LANSA Ltd Legal stuff This E-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately by telephoning +44 (0) 1727 790300. You should not copy it or use it for any other purpose, nor disclose its contents to any other person. In messages of non-business nature, the views and opinions expressed are the author's own and do not necessarily reflect the views and opinions of the Company
Re: WebAppDeploy Vs WebAppMount
WebAppConnection WarpConnection warp localhost:8008 WebAppDeploy examples WarpConnection /examples IfModule mod_webapp.c WebAppConnection warpConnection warp localhost:8008 WebAppMount examples warpConnection /examples/ WebAppMount manager warpConnection /manager/ WebAppMount webdav warpConnection /webdav/ /IfModule Obviously there is something wrong here... should be something like IfModule mod_webapp.c WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples WarpConnection /examples WebAppDeploy manager WarpConnection /manager WebAppDeploy webdav WarpConnection /webdav /IfModule WebAppMount is not document with mod_webapp 1.0.2-tc402 more over, manager servlet doesn't work, I guess it's because it require BASIC authentication and the RELEASE-NOTES for tomcat 402b says it's broken in mod_webapp... The reason I wanted a recent version of mod_webapp is that it is supposed to support specification of complete path as David Smith mentionned in post (BTW David, I couldn't find any mod_webapp in the nightly snapshot, so that's why I used the rpm). you can always try to compile it, it's quite easy now hope this help pkr -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: WebAppDeploy Vs WebAppMount
you can always try to compile it, it's quite easy now where do I get the latest source of mod_webapp? Beside how do specify the mapping? What I want to be able to do is point my browser to: http://localhost/examples/HelloWorldExmample instead of having to do: http://localhost/examples/servlet/HelloWorldExmample How do I specify that in WebAppDeploy ? Thanks Dom -Original Message- From: Patrick Roumanoff [mailto:[EMAIL PROTECTED]] Sent: 29 January 2002 17:22 To: Tomcat Users List Subject: Re: WebAppDeploy Vs WebAppMount WebAppConnection WarpConnection warp localhost:8008 WebAppDeploy examples WarpConnection /examples IfModule mod_webapp.c WebAppConnection warpConnection warp localhost:8008 WebAppMount examples warpConnection /examples/ WebAppMount manager warpConnection /manager/ WebAppMount webdav warpConnection /webdav/ /IfModule Obviously there is something wrong here... should be something like IfModule mod_webapp.c WebAppConnection warpConnection warp localhost:8008 WebAppDeploy examples WarpConnection /examples WebAppDeploy manager WarpConnection /manager WebAppDeploy webdav WarpConnection /webdav /IfModule WebAppMount is not document with mod_webapp 1.0.2-tc402 more over, manager servlet doesn't work, I guess it's because it require BASIC authentication and the RELEASE-NOTES for tomcat 402b says it's broken in mod_webapp... The reason I wanted a recent version of mod_webapp is that it is supposed to support specification of complete path as David Smith mentionned in post (BTW David, I couldn't find any mod_webapp in the nightly snapshot, so that's why I used the rpm). you can always try to compile it, it's quite easy now hope this help pkr -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED] -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
