Re: ROOT.xml problem

OK, so now, how is this working? How to fix it? ROOT.xml is located in conf/Catalina/localhost File contents are thus: in the browser I am entering http://localhost:8080 the URL is comes up with is thus: http://localhost:8080/dashboards/welcome/main.dashxml However it should be: http://l

Re: ROOT.xml problem

01/06/2012 22:53, Kevin Marx wrote: >> OK… here's what I've done. >> >> ROOT.xml located in /conf/Catalina/localhost >> >> contents of Root.xml > > Case matters. Which is it? > >> >> > docBase="C:\Corda\CenterView4\Se

Re: ROOT.xml problem

01/06/2012 22:53, Kevin Marx wrote: >> OK… here's what I've done. >> >> ROOT.xml located in /conf/Catalina/localhost >> >> contents of Root.xml > > Case matters. Which is it? > >> >> > docBase="C:\Corda\CenterView4\Se

Re: ROOT.xml problem

the same results. Kevin On Jun 1, 2012, at 2:27 PM, Mark Thomas wrote: > On 01/06/2012 22:22, Kevin Marx wrote: >> The ROOT.xml file is in the Catalina/localhost folder >> >> Renaming the folder didn't work BTW. >> >> I have the /corda folder located in

Re: ROOT.xml problem

p the ROOT.xml file so that it makes the /corda the default rather than /ROOT as the default? Kevin On Jun 1, 2012, at 12:43 PM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Kevin, > > On 6/1/12 2:40 PM, Kevin Marx wrote: >> I am usin

ROOT.xml problem

I am using Tomcat 7 and wish to have my app open as the default page. I have googled and basically found the following recommendation, but its not working. Wondering what I am missing? ROOT.xml code…. ……. Thanks in advance. Kevin

Tomcat 4/Java 6 Digester logging

I've seen lots of people asking this or similar questions, but I can't seem to get a working solution. I'm running Tomcat 4.1.40 on java 1.6.0_20-b02 on Solaris 10 and getting these type messages in catalina.out [org.apache.commons.digester.Digester] : addRuleSet() with no namespace URI

Re: Tomcat5,Apache2,mod_ssl and mod_jk

good, for example I know I need mod_proxy together with mod_proxy_ajp, hovewer mod_proxy is strict http I don't want to have (need to secure his port), I would like to have only connector with ajp13 protocol whch seems rather safe. Marx ---

Re: Tomcat5,Apache2,mod_ssl and mod_jk

One more information, everything works ok if I use directive , bu I want to be more secure and I want to use Marx - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For

Tomcat5,Apache2,mod_ssl and mod_jk

cate) and whatever directive I would write I can't unblock some directories to not need certificate. Last word - such configuration worked with Apache 1.3, Tomcat 4, mod_ssl and mod_jk. Marx - To start a new topic,