bug in 4.1.30?? PageContextImpl hides exception cause

2004-10-09 Thread Dean Hiller
In 4.1.30, In PageContextImpl, I see this code (should I post this on the dev list instead) 525 if (t instanceof IOException) throw (IOException)t; 526 if (t instanceof ServletException) throw (ServletException)t; 527if (t instanceof RuntimeException) throw (RuntimeException)t

Javascript and cookie

2004-10-09 Thread Carlos Bracho
Hi everybody... Can I know if the browser has cookies and javascript set as enable? of course using jps or servlet. Regards Carlos -- -- Carlos J, Bracho M. "The significant problems we face canno

Re: Rename jsessionid

2004-10-09 Thread Tim Funk
This is exactly what you'll need to do. There is no feature (or never will be a feature) to allow the renameing of jsessionid. -Tim Michael Echerer wrote: Built Tomcat from source and change the few java class files where jsessionid is in. What we once did: Patch the binary! :-) you can grep fo

Example of MBean for own component?

2004-10-09 Thread Michael Schuerig
I'm looking for a simple example of how to add managability through JMX to a webapp. The Tomcat docs aren't helping me, unfortunately. I understand that Tomcat supports Commons Modeler for generating model MBeans. What I don't see is how to register those MBeans. Do I have to do this programma

Re: Name jdbc is not bound in this Context

2004-10-09 Thread Mauro Romano Trajber
On Sat, 09 Oct 2004 19:48:45 +0200, Michael Echerer <[EMAIL PROTECTED]> wrote: > If you put the ResourceParams stuff in server.xml as GlobalResource, > you must put e.g. this into your server.xml's context respectively your > myapp.xml context descriptor. Ok, did it > type="javax.sql.DataSource

Re: Rename jsessionid

2004-10-09 Thread Michael Echerer
Built Tomcat from source and change the few java class files where jsessionid is in. What we once did: Patch the binary! :-) you can grep for jsessionid in the tomcat jars somewere in server/lib (don't ask me which, but 1 think in 2-3 jars there was 1 class file each) You may simple replace the

Re: Name jdbc is not bound in this Context

2004-10-09 Thread Michael Echerer
If you put the ResourceParams stuff in server.xml as GlobalResource, you must put e.g. this into your server.xml's context respectively your myapp.xml context descriptor. Of course name and global can differ, but I think this is easiest. There's some hint in the Tomcat 5 docu that this is neede

Name jdbc is not bound in this Context

2004-10-09 Thread Mauro Romano Trajber
I have configured the following datasource in $TOMCAT_HOME/conf/Catalina/localhost/myapp.xml: factoryorg.apache.commons.dbcp.BasicDataSourceFactory driverClassNamecom.mysql.jdbc.Driver urljdbc:mysql://localhost/myappt ... Then in my web.xml: ... jdbc/myapp javax.sql.DataSource Container ..

Rename jsessionid

2004-10-09 Thread Ben
How can I use a different name for the session id? I would like to use: SID=27D2A9CA7006C94A9CAAE1D96D4D39BD instead of: jsessionid=27D2A9CA7006C94A9CAAE1D96D4D39BD Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

RE: TOMCAT not Starting up

2004-10-09 Thread Caldarale, Charles R
> From: Kumar Singh Rathour, Raj (Vedam) [mailto:[EMAIL PROTECTED] > Subject: RE: TOMCAT not Starting up > > I am getting following error when I am running catalina from > DOS command prompt > > Using JAVA_HOME: c:\jdk1.3 > sun.misc.InvalidJarIndexException: Invalid index! You need to upg

RE: [Possible bug?] Context configurations and .WAR deployment

2004-10-09 Thread D'Alessandro, Arthur
A suggestion, include the ROOT.xml as context.xml under META-INF, tomcat will create it under your host as ROOT.xml when it is deployed. That doesn't solve the problem your experiencing, what does your ROOT.xml look like? What are you referencing your docBase? Ours word fine by referencing the ROO

[Possible bug?] Context configurations and .WAR deployment

2004-10-09 Thread raiden
Hello, I recently upgraded from Tomcat 5.0.19 to Tomcat 5.0.28. I am now running into a conflict between ROOT.xml and ROOT.war. This happens when I deploy to production: 1. I delete the ROOT.war and ROOT directory from /usr/local/tomcat/webapps 2. I delete the ROOT.xml context configuration file