Re: is this a BUG at class loading from jarfiles

2001-04-14 Thread Mario Koch


- Original Message -
From: "Craig R. McClanahan" [EMAIL PROTECTED]
To: "Mario Koch" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, April 13, 2001 11:09 PM
Subject: Re: is this a BUG at class loading from jarfiles




 On Fri, 13 Apr 2001, Mario Koch wrote:

  Situation:
 
  I have several webapplications that using the same jar filename.
 
  webapps/app.new/WEB-INF/lib/javaserver.jar
  webapps/app.stable/WEB-INF/lib/javaserver.jar
  webapps/app.test/WEB-INF/lib/javaserver.jar
 
  these jarfiles are different
 

Sorry my fault i delete the version line in this email (was late in the
night).
Yes iam using 4.0b3. and thank you the nightly build works fine.



 Is this Tomcat 4.0-beta-3?  If so, this bug has already been fixed, and
 you should grab the most recent nightly distribution.  Otherwise, please
 include the version number and submit a bug report to:

 http://nagoya.apache.org/bugzilla/

 Craig McClanahan





Re: JDBCStore package for Tomcat 4.x

2001-04-14 Thread Kief Morris

Bip Thelin typed the following on 03:57 PM 4/13/2001 -0700
 - Would it be possible to parameterize the SQL statements used to
   access the database?  The idea would be that we can adapt to different
   table and column names (like JDBCRealm does on the authentication side).
...
I would like to propose that we save additional data in the database. The 
table would
then look something like following:
TABLE:
[int  ID]   The ID for this session
[boolean  ISVALID]  True if this session is valid
[int  MAXINACTIVE]  The Max inactive attribute
[Blob SESSION]  The session object

Then you could have a StoredProcedure if you want to that checks for 
timedout sessions
and delete/invalidate them.

I think this is a good way to go about it: it looks like the table name can be 
configured
in the server.xml file. Probably the column names should also maintained as JDBCStore
properties for configurability.

The table will need a column for the lastAccessedTime. And the ID column will need to 
be something like CHAR, VARCHAR, or BYTE rather than an int.

Kief




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session FileStore.java

2001-04-14 Thread kief

kief01/04/14 03:56:29

  Modified:catalina/src/share/org/apache/catalina/session
FileStore.java
  Log:
  Removed code which duplicates that in Manager, namely the background
  thread checking for expired sessions. This involved removing implementation
  of the Lifecycle and Runnable interfaces.
  
  Also changed the log method to indicate messages as comming from FileStore
  rather than Manager.
  
  Revision  ChangesPath
  1.4   +9 -267
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/FileStore.java
  
  Index: FileStore.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/FileStore.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- FileStore.java2001/04/12 18:18:58 1.3
  +++ FileStore.java2001/04/14 10:56:29 1.4
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/FileStore.java,v
 1.3 2001/04/12 18:18:58 kief Exp $
  - * $Revision: 1.3 $
  - * $Date: 2001/04/12 18:18:58 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/session/FileStore.java,v
 1.4 2001/04/14 10:56:29 kief Exp $
  + * $Revision: 1.4 $
  + * $Date: 2001/04/14 10:56:29 $
*
* 
*
  @@ -105,11 +105,11 @@
* saved are still subject to being expired based on inactivity.
*
* @author Craig R. McClanahan
  - * @version $Revision: 1.3 $ $Date: 2001/04/12 18:18:58 $
  + * @version $Revision: 1.4 $ $Date: 2001/04/14 10:56:29 $
*/
   
   public final class FileStore
  -implements Lifecycle, Runnable, Store {
  +implements Store {
   
   
   // - Constants
  @@ -125,17 +125,12 @@
   
   
   /**
  - * The interval (in seconds) between checks for expired sessions.
  - */
  -private int checkInterval = 60;
  -
  -
  -/**
* The pathname of the directory in which Sessions are stored.
* Relative to the temp directory for the web application.
*/
   private String directory = ".";
   
  +
   /**
* A File representing the directory in which Sessions are stored.
*/
  @@ -149,12 +144,6 @@
   
   
   /**
  - * The lifecycle event support for this component.
  - */
  -protected LifecycleSupport lifecycle = new LifecycleSupport(this);
  -
  -
  -/**
* The string manager for this package.
*/
   private StringManager sm =
  @@ -162,30 +151,12 @@
   
   
   /**
  - * Has this component been started yet?
  - */
  -private boolean started = false;
  -
  -
  -/**
* The property change support for this component.
*/
   private PropertyChangeSupport support = new PropertyChangeSupport(this);
   
   
   /**
  - * The background thread.
  - */
  -private Thread thread = null;
  -
  -
  -/**
  - * The background thread completion semaphore.
  - */
  -private boolean threadDone = false;
  -
  -
  -/**
* The Manager with which this FileStore is associated.
*/
   protected Manager manager;
  @@ -197,42 +168,10 @@
   protected int debug = 0;
   
   
  -/**
  - * Name to register for the background thread.
  - */
  -private String threadName = "FileStore";
  -
  -
   // - Properties
   
   
   /**
  - * Return the check interval (in seconds) for this Manager.
  - */
  -public int getCheckInterval() {
  -
  -return (this.checkInterval);
  -
  -}
  -
  -
  -/**
  - * Set the check interval (in seconds) for this Manager.
  - *
  - * @param checkInterval The new check interval
  - */
  -public void setCheckInterval(int checkInterval) {
  -
  -int oldCheckInterval = this.checkInterval;
  -this.checkInterval = checkInterval;
  -support.firePropertyChange("checkInterval",
  -   new Integer(oldCheckInterval),
  -   new Integer(this.checkInterval));
  -
  -}
  -
  -
  -/**
* Return the directory path for this Store.
*/
   public String getDirectory() {
  @@ -495,6 +434,7 @@
   
   }
   
  +
   /**
* Remove a property change listener from this component.
*
  @@ -548,82 +488,6 @@
   }
   
   
  -// -- Lifecycle Methods
  -
  -
  -/**
  - * Add a lifecycle event listener to this component.
  - *
  - * @param listener The listener to add
  - */
  -public void addLifecycleListener(LifecycleListener listener) {
  -
  -

ULI Rewriting with SSL fix-Date ?

2001-04-14 Thread Wolle

Hello,
i have a question about the URI Rewiting bug, when I use SSL without
cookies.
Bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=578

This includes a workaround,
but my question is, when will in wich version will this bug be fixed ?
Because i have to garant it, it it would be not such a problem to
install my servlets,
but when you have to patch the main webserver.jar and so on, it's not so
good.
For the 3.2.2b2 Version i have done the fix, but you can't import it in
another verision, because of the jar fil.
All in all, i only want to know, when you insert the fix in a official
verion,

plz wrote back,
thanks for inconvenience,
Michael

--
Gruss,
Wolle

---
Auf dem Vorst 73Eckertweg 20 (112)
50171 Kerpen 52072 Aachen
Tel.: 02237-55897   Tel.:0241-89499950
  Tel.:0177-8403863
  E-Mail: [EMAIL PROTECTED]
  E-Mail: [EMAIL PROTECTED]
  http://www.get.to/wolle
ICQ: 23605031
---