Re: Can't get caseSensitive=false to work
Nobody has any suggestions on this? I still can't get it to go. Thnaks! Dave David Kerber wrote: I read the thread from last week about case-sensitivity, and did some additional googling when it didn't work, but still can't get my Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for the context path. That is a problem for my users, because we migrated them from SilverStream, which is NOT case-sensitive in the context path. I have tried the following Context entries. Note the entry in both the Context field, and the Resources entry (I found that one via google). I have tried these entries eash separately, and together, and still cannot get my context path to be case-INsensitive. I don't care if things are case sensitive once they get into the app, but would really like to get the context path to not matter. This is in my server.xml, because I can't get the context path to work in context.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\WebSiraCommon\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false caseSensitive=false Resources caseSensitive=false/ /Context And yes, I know about the security warning about being non case-sensitive on Windows! I also know that this context path setup is not the usual way of doing things; it's because I need to keep the path the same after the migration to Tomcat. Thanks! Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can't get caseSensitive=false to work
I know that it works in conf/context.xml. Can you just setup a minimal config in the context.xml file? Context caseSensitive=false !-- Default set of monitored resources -- WatchedResourceWEB-INF/web.xml/WatchedResource /Context According to the docs, the server.xml is not recommended place to put Context setup. http://tomcat.apache.org/tomcat-5.5-doc/config/context.html -Original Message- From: David Kerber [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 15, 2006 8:49 AM To: Tomcat Users List Subject: Re: Can't get caseSensitive=false to work Nobody has any suggestions on this? I still can't get it to go. Thnaks! Dave David Kerber wrote: I read the thread from last week about case-sensitivity, and did some additional googling when it didn't work, but still can't get my Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for the context path. That is a problem for my users, because we migrated them from SilverStream, which is NOT case-sensitive in the context path. I have tried the following Context entries. Note the entry in both the Context field, and the Resources entry (I found that one via google). I have tried these entries eash separately, and together, and still cannot get my context path to be case-INsensitive. I don't care if things are case sensitive once they get into the app, but would really like to get the context path to not matter. This is in my server.xml, because I can't get the context path to work in context.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\WebSiraCommon\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false caseSensitive=false Resources caseSensitive=false/ /Context And yes, I know about the security warning about being non case-sensitive on Windows! I also know that this context path setup is not the usual way of doing things; it's because I need to keep the path the same after the migration to Tomcat. Thanks! Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** Confidentiality Notice The information contained in this e-mail is confidential and intended for use only by the person(s) or organization listed in the address. If you have received this communication in error, please contact the sender at O'Neil Associates, Inc., immediately. Any copying, dissemination, or distribution of this communication, other than by the intended recipient, is strictly prohibited. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't get caseSensitive=false to work
Thanks for the response, but I still can't get it to go. I set up another server with the Context entries in the context.xml instead of in server.xml, so things are where the docs recomment, but still nothing. I've put the caseSensitive=false in both the one in /conf, and in META-INF with no luck. Are you sure it works in 5.5.12? A couple of the posts I've seen while googling have implied that the last version this worked in was 5.5.9. That would really suck if correct! If it matters, I'm running jdk 1.5.0_06. David Kerber wrote: Nobody has any suggestions on this? I still can't get it to go. Thnaks! Dave David Kerber wrote: I read the thread from last week about case-sensitivity, and did some additional googling when it didn't work, but still can't get my Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for the context path. That is a problem for my users, because we migrated them from SilverStream, which is NOT case-sensitive in the context path. I have tried the following Context entries. Note the entry in both the Context field, and the Resources entry (I found that one via google). I have tried these entries eash separately, and together, and still cannot get my context path to be case-INsensitive. I don't care if things are case sensitive once they get into the app, but would really like to get the context path to not matter. This is in my server.xml, because I can't get the context path to work in context.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\WebSiraCommon\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false caseSensitive=false Resources caseSensitive=false/ /Context And yes, I know about the security warning about being non case-sensitive on Windows! I also know that this context path setup is not the usual way of doing things; it's because I need to keep the path the same after the migration to Tomcat. Thanks! Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can't get caseSensitive=false to work
I'm using Tomcat 5.5.14 and jdk 1.5.0_06. -Original Message- From: David Kerber [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 15, 2006 9:44 AM To: Tomcat Users List Subject: Re: Can't get caseSensitive=false to work Thanks for the response, but I still can't get it to go. I set up another server with the Context entries in the context.xml instead of in server.xml, so things are where the docs recomment, but still nothing. I've put the caseSensitive=false in both the one in /conf, and in META-INF with no luck. Are you sure it works in 5.5.12? A couple of the posts I've seen while googling have implied that the last version this worked in was 5.5.9. That would really suck if correct! If it matters, I'm running jdk 1.5.0_06. David Kerber wrote: Nobody has any suggestions on this? I still can't get it to go. Thnaks! Dave David Kerber wrote: I read the thread from last week about case-sensitivity, and did some additional googling when it didn't work, but still can't get my Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for the context path. That is a problem for my users, because we migrated them from SilverStream, which is NOT case-sensitive in the context path. I have tried the following Context entries. Note the entry in both the Context field, and the Resources entry (I found that one via google). I have tried these entries eash separately, and together, and still cannot get my context path to be case-INsensitive. I don't care if things are case sensitive once they get into the app, but would really like to get the context path to not matter. This is in my server.xml, because I can't get the context path to work in context.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\WebSiraCommon\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false caseSensitive=false Resources caseSensitive=false/ /Context And yes, I know about the security warning about being non case-sensitive on Windows! I also know that this context path setup is not the usual way of doing things; it's because I need to keep the path the same after the migration to Tomcat. Thanks! Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** Confidentiality Notice The information contained in this e-mail is confidential and intended for use only by the person(s) or organization listed in the address. If you have received this communication in error, please contact the sender at O'Neil Associates, Inc., immediately. Any copying, dissemination, or distribution of this communication, other than by the intended recipient, is strictly prohibited. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't get caseSensitive=false to work
Ok, thanks. Obviously I'm missing something, then. I'll keep digging... Bob Faist wrote: I'm using Tomcat 5.5.14 and jdk 1.5.0_06. -Original Message- From: David Kerber [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 15, 2006 9:44 AM To: Tomcat Users List Subject: Re: Can't get caseSensitive=false to work Thanks for the response, but I still can't get it to go. I set up another server with the Context entries in the context.xml instead of in server.xml, so things are where the docs recomment, but still nothing. I've put the caseSensitive=false in both the one in /conf, and in META-INF with no luck. Are you sure it works in 5.5.12? A couple of the posts I've seen while googling have implied that the last version this worked in was 5.5.9. That would really suck if correct! If it matters, I'm running jdk 1.5.0_06. David Kerber wrote: Nobody has any suggestions on this? I still can't get it to go. Thnaks! Dave David Kerber wrote: I read the thread from last week about case-sensitivity, and did some additional googling when it didn't work, but still can't get my Tomcat 5.5.12 on Win2k, running with Java 1.5.0_06 to be case-INsensitive for the context path. That is a problem for my users, because we migrated them from SilverStream, which is NOT case-sensitive in the context path. I have tried the following Context entries. Note the entry in both the Context field, and the Resources entry (I found that one via google). I have tried these entries eash separately, and together, and still cannot get my context path to be case-INsensitive. I don't care if things are case sensitive once they get into the app, but would really like to get the context path to not matter. This is in my server.xml, because I can't get the context path to work in context.xml: Context path=/wradev/pelican docBase=e:\TomcatClients\WebSiraCommon\webapps\SiteData debug=0 reloadable=true autoDeploy=true unpackWARs=true crossContext=false caseSensitive=false Resources caseSensitive=false/ /Context And yes, I know about the security warning about being non case-sensitive on Windows! I also know that this context path setup is not the usual way of doing things; it's because I need to keep the path the same after the migration to Tomcat. Thanks! Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
