tomcat root context
The server.xml provided with tomcat 4.01 includes: !-- Tomcat Root Context -- !-- Context path= docBase=ROOT debug=0/ -- and yet the files in webapps/ROOT are server up when the url http://localhost:8080 is used regardless of the fact that the Context element above is commented out. Does this mean that ROOT has special significance and it is hardcoded somewhere or am I missing something in a config file that instructs tomcat to use this as the default context? Thanks, Scott -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Missing Step in deployng TDk app?
From: Ivo Zivkov [EMAIL PROTECTED] To: [EMAIL PROTECTED] I have a question about deploying the application. I am using the latest Turbine TDK with Tomcat 4.0.1 on Linux. After successfully building the sample 'newapp' in the turbine TDK, tomcat reposted Not fond error 404' to the URL: http://localhost:8080/newapp/servlet/newapp, even though I have correctly set CATALINA_HOME variable. I can verify that TOMCAT is running properly, because id displays its information when browser pointed to http://localhost:8080 http://localhost:8080/ . The only way I could get it to work is by making a link from the TDK directory: $SOME_TDK_HOME/webapps/newapp to the tomcat directory: $CATALINA_HOME/webapps/newapp I could then access the application using the URL http://localhost:8080/newapp/servlet/newapp. Was this step not supposed to be made automatically by the build process? Is there anything special to be done to make tomcat find the application. I could not find anything that links the TDK application to the tomcat directory. Any help would be greatly appreciated. Regards, Ivo Zivkov [EMAIL PROTECTED] You would probably get a better response from the turbine-user mailing list. The tdk comes with it's own tomcat (4.0b6 I think) and it should fire up correctly if you use the startup.sh in /tdk/bin with CATALINA_HOME set to /tdk If you want to use tomcat 4.01 installed elsewhere you need to copy webapp/newapp over to the 4.01 webapp directory or use the link that you are already using. HTH Scott -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Turbine/Velocity abd PostgreSQL problem
Try the turbine-user list. - Original Message - From: Ivo Zivkov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 02, 2002 11:13 AM Subject: Turbine/Velocity abd PostgreSQL problem Has anyone been able to get turbine and velocity to work with PostgreSQL? I followed the instruction to build the sample application (newapp), and applied the patch to the PostgreSQL JDBC driver as recommended here: http://jakarta.apache.org/turbine/turbine-2/howto/postgres-howto.html Still, I am getting the following errors in the app log file: [Tue Jan 01 18:44:15 EST 2002] -- ERROR -- Error rendering Velocity template: s\ creens/user/FluxUserList.vm: Invocation of method 'getUsers' in class org.apac\ he.turbine.flux.tools.FluxTool threw exception class org.apache.turbine.util.se\ curity.DataBackendException and: [Tue Jan 01 18:44:15 EST 2002] -- ERROR -- Error rendering Velocity template: s\ creens/user/FluxUserList.vm: Error rendering Velocity template: screens/user/Fl\ uxUserList.vm: Invocation of method 'getUsers' in class org.apache.turbine.flu\ x.tools.FluxTool threw exception class org.apache.turbine.util.security.DataBac\ kendException I understand it has something to do with velocity and PostgreSQL not handling BLObs correctly, but has anyone been able to resolve this? Regards, Ivo Zivkov -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
servlet-mapping problem - tomcat 4.0.1
How do I default a user to my servlet without blocking access to other directories? Using a default mapping of / results in failure to gain access to resources under my servlet directory. I think I have a fairly standard set-up of tomcat 4.0.1 on win2k. Within C:\jakarta-tomcat-4.0.1\webapps I have a directory structure like this: myapp styles global.css WEB_INF web.xml lib [jar files] web.xml defines a servlet whose output includes a reference to http://mysite.com/myapp/styles/global.css If I set my servlet mapping up like this: servlet-mapping servlet-namemyapp/servlet-name url-pattern//url-pattern /servlet-mapping then the stylesheet cannot be loaded when the user surfs to http://mysite.com/myapp/ Alternatively if I set up my mapping like this: servlet-mapping servlet-namemyapp/servlet-name url-pattern/foo/*/url-pattern /servlet-mapping then the stylesheet can be located, but the user must surf to http://mysite.com/myapp/foo/ How can I configure tomcat or structure my directories so that a user can surf to http://mysite.com/myapp/ and also successfully access the stylesheet? Note that the above is a contrived example. The real servlet includes many other resources in the myapp directory to which the servlet refers. Any advice would be most welcome. Thanks, Scott -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: servlet-mapping problem - tomcat 4.0.1
From: Craig R. McClanahan [EMAIL PROTECTED] On Fri, 21 Dec 2001, Scott Eade wrote: Subject: servlet-mapping problem - tomcat 4.0.1 How do I default a user to my servlet without blocking access to other directories? Using a default mapping of / results in failure to gain access to resources under my servlet directory. Understanding this requires a little explanation about what is really going on. * The servlet mapping pattern of / establishes the default servlet -- in other words, the servlet that Tomcat will hand the request to if it can find no other servlet mapping that matches. * Tomcat, out of the box, defines a default servlet that serves the static resources (including your stylesheet). * You can take over the default mapping yourself, but then you give up Tomcat's standard file-serving service and do it yourself if you still need that feature. To give you suggestions, it would be helpful to understand what you mean by default a user to my servlet. What application functionality are you trying to accomplish? Thanks Craig. What I would like to do is be able to serve up some static content from the root of my web server, say http://mysite.com/ and from there provide a link to an Apache Turbine application located at webapps/myapp. I am simply hoping to provide a relatively clean url for the application - http://mysite.com/myapp rather than http://mysite.com/myapp/foo. I actually have this working at one host provider that uses Zeus and Resin. The root directory they provide contains the necessary resources (styles, templates, etc.) along with the WEB-INF directory that contains a web.xml with a url-mapping of /myapp/* and everything works fine. I am switching to a new hosting organization that uses Apache and Tomcat and I am only now running into this problem. I thought the problem was that the new host provider is running tomcat 3.1 (upgrading to 4.01 next week) but then I realised that all of my development was being done under tomcat with servlet mappings that included at least some additional component such as /myapp/foo/*. Ultimately I guess I am worried about the aesthetics of the url, however it would be great if I could somehow mimic the behaviour of the old site. What about users that have bookmarked the old address without the foo - I'll have to provide a redirect for them on top of a redirect that turbine does as a matter of course. This will cause some messy behaviour at the beginning of my application. Incidentally the new hosting organization provides me with my own virtual tomcat server. By default they configured a root context (path=) pointing to a directory called public_html and I had them provide another (path=/myapp docBase=/home/myaccount/tomcat/webapps/myapp) where I am installing my turbine application. I do have the ability to change server.xml and restart tomcat if this will help. I host provider does need to alter something (mod_jserv or apache I guess) if I add any new contexts. It is unclear how this will change when they upgrade to tomcat 4.01. I hope this gives you a clearer idea of what I am trying to achieve. Thanks in advance for any advice. Scott -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Newbee - how does tomcat 3.1 know the names of the jar files to load
Hi, I have had a brief look at the archives, but I can't find this particular needle in the haystack. I am trying to get an servlet up and running at an ISP that has tomcat 3.1 and I am running into a couple of problems. (The ISP will soon be upgrading to 4.01 but for now I have to make do with 3.1). Apart from the fact that the servlet isn't yet running, I am noticing something quite odd. If I restart tomcat with one of the necessary jar files missing from my WEB-INF/lib directory I get: Error loading default servlet java.lang.IllegalArgumentException: Repository //WEB-INF/lib/turbine-2.1.jar doesn't exist! How is it that tomcat knows the name of the jar file rather than just not finding a particular class? I actually have the contents of this particular jar file packaged up in another jar file (with various patched classes included). I would have thought the name of the jar files was irrelevant. Can someone please give me a clue as to how this is happening so that I can get back to the real problem of getting the servlet to work. Thanks, Scott -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
