cvs commit: jakarta-tomcat-jasper/jasper34/tools - New directory

2001-05-28 Thread costin

costin  01/05/27 23:47:28

  jakarta-tomcat-jasper/jasper34/tools - New directory



cvs commit: jakarta-tomcat-jasper/jasper34/tools manifest.jspc

2001-05-28 Thread costin

costin  01/05/27 23:48:15

  Modified:jasper34 build.xml
   jasper34/generator/org/apache/jasper34/generator
SetPropertyGenerator.java
   jasper34/runtime/org/apache/jasper34/runtime
JspRuntimeLibrary.java
  Added:   jasper34/tools manifest.jspc
  Log:
  Fixed build.xml to include the javac adapters.
  
  Added a manifest for jspc.
  
  Revision  ChangesPath
  1.3   +4 -1  jakarta-tomcat-jasper/jasper34/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-jasper/jasper34/build.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- build.xml 2001/05/28 02:20:42 1.2
  +++ build.xml 2001/05/28 06:48:13 1.3
  @@ -89,11 +89,14 @@
 /fileset
   /copy
   
  -jar jarfile=${build.dir}/jasper34.jar 
  +jar manifest=${jasper34.src}/tools/manifest.jspc 
  +  jarfile=${build.dir}/jasper34.jar 
 basedir=${build.dir}/classes 
 include name=org/apache/jasper34/generator/**/
 include name=org/apache/jasper34/core/**/
  +  include name=org/apache/jasper34/javacompiler/**/
 include name=org/apache/jasper34/resources/**/
  +  
   /jar
 /target
   
  
  
  
  1.2   +0 -4  
jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/generator/SetPropertyGenerator.java
  
  Index: SetPropertyGenerator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/generator/SetPropertyGenerator.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- SetPropertyGenerator.java 2001/05/27 23:19:31 1.1
  +++ SetPropertyGenerator.java 2001/05/28 06:48:14 1.2
  @@ -1,8 +1,4 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-jasper/jasper34/generator/org/apache/jasper34/generator/SetPropertyGenerator.java,v
 1.1 2001/05/27 23:19:31 costin Exp $
  - * $Revision: 1.1 $
  - * $Date: 2001/05/27 23:19:31 $
  - *
* 
* 
* The Apache Software License, Version 1.1
  
  
  
  1.3   +0 -1  
jakarta-tomcat-jasper/jasper34/runtime/org/apache/jasper34/runtime/JspRuntimeLibrary.java
  
  Index: JspRuntimeLibrary.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper34/runtime/org/apache/jasper34/runtime/JspRuntimeLibrary.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- JspRuntimeLibrary.java2001/05/28 05:07:37 1.2
  +++ JspRuntimeLibrary.java2001/05/28 06:48:15 1.3
  @@ -358,7 +358,6 @@
* @param unescString The string to shell-escape
* @return The escaped shell string.
*/
  -
   public static String escapeQueryString(String unescString) {
   if ( unescString == null )
   return null;
  
  
  
  1.1  jakarta-tomcat-jasper/jasper34/tools/manifest.jspc
  
  Index: manifest.jspc
  ===
  Manifest-Version: 1.0
  Main-Class: org.apache.jasper34.JspC
  Class-Path: ../container/tomcat_util.jar ../common/tomcat_core.jar 
../container/tomcat_modules.jar ../common/servlet.jar ../container/facade22.jar 
../container/jaxp.jar ../container/parser.jar ../container/xerces.jar 
../container/crimson.jar ../container/jasper.jar
  
  
  
  



RE: java.rmi.UnmarshalException

2001-05-28 Thread Bartsch Axel

Hi,

Have you also copied the class ..._skel.class into that directory?

And secondly the classes STUB and SKEL have to correspond on the server and client 
side!

Axel   Lannion/France

 -Original Message-
 From: Kleegrewe Christian [SMTP:[EMAIL PROTECTED]]
 Sent: vendredi 25 mai 2001 10:39
 To:   'Tomcat Developer Mailing List'
 Subject:  java.rmi.UnmarshalException
 
 Hi Tomcat Developers!
 
 I have a problem using the tomcat servlet engine.
 We are developing a servlet based web application. 
 My Configuration is:
 
 apache web server
 tomcat servlet engine 3.2.1 
 windows nt 4.0 servicepack 6a.
 jdk 1.2.2 build _007
 
 starting up tomcat seems to work fine:
 --8
 Including all jars in D:\jakarta-tomcat-3.2.1\lib in your CLASSPATH.
 
 Using CLASSPATH:
 D:\jakarta-tomcat-3.2.1\classes;D:\jakarta-tomcat-3.2.1\lib\ant
 .jar;D:\jakarta-tomcat-3.2.1\lib\jasper.jar;D:\jakarta-tomcat-3.2.1\lib\jaxp
 .jar
 ;D:\jakarta-tomcat-3.2.1\lib\parser.jar;D:\jakarta-tomcat-3.2.1\lib\servlet.
 jar;
 D:\jakarta-tomcat-3.2.1\lib\webserver.jar;E:\kleegrewe_c\Project-Code\ic-tag
 -dem
 o\NegotiationEngine\web-inf\classes;c:\programme\jdk1.2.2\lib\tools.jar
 
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /examples )
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /admin )
 2001-05-25 09:37:07 - Ctx( /ne ): Set debug to 9
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /ne )
 Starting tomcat. Check logs/tomcat.log for error messages
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx(  )
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /test )
 2001-05-25 09:37:07 - Ctx( /ne ): XmlReader - init  /ne
 E:/kleegrewe_c/Project-C
 ode/ic-tag-demo/NegotiationEngine
 2001-05-25 09:37:07 - Ctx( /ne ): Loading -2147483646 jsp
 2001-05-25 09:37:08 - PoolTcpConnector: Starting HttpConnectionHandler on
 8080
 2001-05-25 09:37:08 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
 8007
 --8
 --
 
 When I start my applicaition and request a servlet for the first time I get
 the following exception
 
 --8
 --java.rmi.UnmarshalException: error unmarshalling return; nested
 exception is:
 java.lang.ClassNotFoundException: negotiation.ConnectionManager_Stub
 java.lang.ClassNotFoundException: negotiation.ConnectionManager_Stub
 at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:981)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
 at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
 at java.rmi.Naming.lookup(Naming.java:89)
 
 at
 negotiation.servlet.LoginFrameServlet.init(LoginFrameServlet.java:20)
 
 at
 org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
 
 at org.apache.tomcat.core.Handler.init(Handler.java:215)
 .
 
 --8
 --
 
 The Code in the class
 negotiation.servlet.LoginFrameServlet.init(LoginFrameServlet.java:20)
 is the following:
 
 18System.setSecurityManager(new RMISecurityManager());
 19try {
 20 cm = (ConnectionRMIInterface)Naming.lookup(// +
 Constants.SERVER_IP + : + Constants.RMI_PORT + /Connection);
 21  //cm.printTest(initialization of Actualization servlet);
 22}catch (Exception e){ e.printStackTrace(); }
 
 The value of Constants.SERVER_IP  is the ip adress of the computer where the
 tomcat engine and apache and my application are running.
 
 The Value of Constants.RMI_PORT is 2005. My connectionManager is listening 
 to this port.
 
 the classpath environment variable of tomcat points to the directory where
 the class that can not befound is situated in. The class
 ConnaectionManager_Stub.class also exists in the proposed directory. So
 where is the error?
 
 Any help we be appreciated.
 
 Thanks Christian Kleegrewe
 
 
 -8
 
 Christian Kleegrewe
 Siemens AG:   ZT IK 6
 Fon:  +49 89 636 42722
 Fax:  +49 89 636 41423
 em@il:[EMAIL PROTECTED]
 
 ---



RE: java.rmi.UnmarshalException

2001-05-28 Thread Kleegrewe Christian

Hi Axel!

Yes there is a corresponding _SKEL.class file in the same directory. When I
rebuild my system both classes are generated by rmic.

Christian

-Original Message-
From: Bartsch Axel [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 8:58 AM
To: '[EMAIL PROTECTED]'
Subject: RE: java.rmi.UnmarshalException


Hi,

Have you also copied the class ..._skel.class into that directory?

And secondly the classes STUB and SKEL have to correspond on the server and
client side!

Axel   Lannion/France

 -Original Message-
 From: Kleegrewe Christian [SMTP:[EMAIL PROTECTED]]
 Sent: vendredi 25 mai 2001 10:39
 To:   'Tomcat Developer Mailing List'
 Subject:  java.rmi.UnmarshalException
 
 Hi Tomcat Developers!
 
 I have a problem using the tomcat servlet engine.
 We are developing a servlet based web application. 
 My Configuration is:
 
 apache web server
 tomcat servlet engine 3.2.1 
 windows nt 4.0 servicepack 6a.
 jdk 1.2.2 build _007
 
 starting up tomcat seems to work fine:

--8
 Including all jars in D:\jakarta-tomcat-3.2.1\lib in your CLASSPATH.
 
 Using CLASSPATH:
 D:\jakarta-tomcat-3.2.1\classes;D:\jakarta-tomcat-3.2.1\lib\ant

.jar;D:\jakarta-tomcat-3.2.1\lib\jasper.jar;D:\jakarta-tomcat-3.2.1\lib\jaxp
 .jar

;D:\jakarta-tomcat-3.2.1\lib\parser.jar;D:\jakarta-tomcat-3.2.1\lib\servlet.
 jar;

D:\jakarta-tomcat-3.2.1\lib\webserver.jar;E:\kleegrewe_c\Project-Code\ic-tag
 -dem
 o\NegotiationEngine\web-inf\classes;c:\programme\jdk1.2.2\lib\tools.jar
 
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /examples )
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /admin )
 2001-05-25 09:37:07 - Ctx( /ne ): Set debug to 9
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /ne )
 Starting tomcat. Check logs/tomcat.log for error messages
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx(  )
 2001-05-25 09:37:07 - ContextManager: Adding context Ctx( /test )
 2001-05-25 09:37:07 - Ctx( /ne ): XmlReader - init  /ne
 E:/kleegrewe_c/Project-C
 ode/ic-tag-demo/NegotiationEngine
 2001-05-25 09:37:07 - Ctx( /ne ): Loading -2147483646 jsp
 2001-05-25 09:37:08 - PoolTcpConnector: Starting HttpConnectionHandler on
 8080
 2001-05-25 09:37:08 - PoolTcpConnector: Starting Ajp12ConnectionHandler on
 8007

--8
 --
 
 When I start my applicaition and request a servlet for the first time I
get
 the following exception
 

--8
 --java.rmi.UnmarshalException: error unmarshalling return; nested
 exception is:
 java.lang.ClassNotFoundException:
negotiation.ConnectionManager_Stub
 java.lang.ClassNotFoundException: negotiation.ConnectionManager_Stub
 at
java.io.ObjectInputStream.inputObject(ObjectInputStream.java:981)
 at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
 at
java.io.ObjectInputStream.readObject(ObjectInputStream.java:232)
 at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
 at java.rmi.Naming.lookup(Naming.java:89)
 
 at
 negotiation.servlet.LoginFrameServlet.init(LoginFrameServlet.java:20)
 
 at
 org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317)
 
 at org.apache.tomcat.core.Handler.init(Handler.java:215)
 .
 

--8
 --
 
 The Code in the class
 negotiation.servlet.LoginFrameServlet.init(LoginFrameServlet.java:20)
 is the following:
 
 18System.setSecurityManager(new RMISecurityManager());
 19try {
 20 cm = (ConnectionRMIInterface)Naming.lookup(// +
 Constants.SERVER_IP + : + Constants.RMI_PORT + /Connection);
 21  //cm.printTest(initialization of Actualization servlet);
 22}catch (Exception e){ e.printStackTrace(); }
 
 The value of Constants.SERVER_IP  is the ip adress of the computer where
the
 tomcat engine and apache and my application are running.
 
 The Value of Constants.RMI_PORT is 2005. My connectionManager is
listening 
 to this port.
 
 the classpath environment variable of tomcat points to the directory where
 the class that can not befound is situated in. The class
 ConnaectionManager_Stub.class also exists in the proposed directory. So
 where is the error?
 
 Any help we be appreciated.
 
 Thanks Christian Kleegrewe
 
 
 -8
 
 Christian Kleegrewe
 Siemens AG:   ZT IK 6
 Fon:  +49 89 636 42722
 Fax:  +49 89 636 41423
 em@il:[EMAIL PROTECTED]
 
 ---



Re: synchronize keyword may produce deadlocks.

2001-05-28 Thread Paul Speed

You do know your code has a typo that will cause deadlocks, don't
you?  See below...

[EMAIL PROTECTED] wrote:
 
 Hi,
The synchronize call may deadlock due to thread starvation. This is present
 in all versions of java on all platforms i could test (jdk 1.1 thru 1.4b
 on win/sol/lin)
 Example code for interlock.java is as follows :
 import java.io.*;
 import java.lang.*;
 public class interlock{
 public static int test=0; // 0 - test java synchronize. 1 - test java regular
 private static boolean atomic_spinlock1=false;
 private static boolean atomic_spinlock2=false; public interlock(){}
 public static void main(String[] args) throws InterruptedException {
 log(InterlockTest : If this code completes test was a success.); 
if(args.length==1){test=Integer.valueOf(args[0]).intValue();}
 new interlock().startup();}
 public static void log(String s){ System.err.println(+s); }
 public static void blink(int 
i){try{Thread.currentThread().sleep(10+i);}catch(Exception
 e){}}
 public static void spinlock1_rel(){atomic_spinlock1=false;}
 public static boolean spinlock1_set(){
 if (atomic_spinlock1==false) { atomic_spinlock1=true; return true; } else
 { return false; } }
 public static void spinlock2_rel(){atomic_spinlock2=false;}
 public static boolean spinlock2_set(){
 if (atomic_spinlock2==false) { atomic_spinlock2=true; return true; } else
 { return false; } }
 public static synchronized void s_spinlock1_rel(){atomic_spinlock1=false;}
 public static synchronized boolean s_spinlock1_set(){
 if (atomic_spinlock1==false) { atomic_spinlock1=true; return true; } else
 { return false; } }
 public static synchronized void s_spinlock2_rel(){atomic_spinlock2=false;}
 public static synchronized boolean s_spinlock2_set(){
 if (atomic_spinlock2==false) { atomic_spinlock2=true; return true; } else
 { return false; } }
 private void startup() { if (test==0) {log(Testing atomic spinlocks with
 Java Virtual Machine sync ); }
 else {log( Testing atomic spinlocks without Java Virtual Machine sync...);}
 Runner y=new Runner(0);Runner s=new Runner(1); y.start();blink(100);s.start();
 }
 class Runner extends Thread implements Runnable{ private int runr=0;
 Runner(int seq) { runr=seq; } public void run() { log( Started runner +runr+
 -- );
 log(runr+: Setting atomic spinlock 1...);
 if (test!=0){while(spinlock1_set()==false){}} else { 
while(s_spinlock2_set()==false){}

Note in the line above that test!=0 is setting spinlock 1 and the else
branch is setting spinlock 2.  So, whenever you test the synchronized
version you are going to get a deadlock since your locking has no
thread identity... a thread can block itself by checking the lock
after setting it.

-Paul Speed

 }
 log(runr+: Set spinlock 1. Now sleeping... );
 blink(1000); log(runr+: Finished sleeping. Now setting spinlock 2... (if
 bug exists it will hang here...) );
 if (test!=0){while(spinlock2_set()==false){}} else { while(spinlock2_set()==false){}
 }
 log(runr+: Spinlock 2 set. Now unsetting both spinlocks... );
 if (test!=0){spinlock2_rel(); spinlock1_rel();}else{s_spinlock2_rel(); 
s_spinlock1_rel();}
 log(runr+: Completed. );  }}  }
 
 BTW, my email has changed.
 [EMAIL PROTECTED] -- [EMAIL PROTECTED]
 Thanks.
 -Ys-
 
 Free, encrypted, secure Web-based email at www.hushmail.com



RE: jsp compacter to be released

2001-05-28 Thread Paulo Gaspar

Triming heading and trailing whitespace for each line of text does (most of)
the trick with very minimal code.

I am doing that to Velocity templates.

Have fun,
Paulo Gaspar

 -Original Message-
 From: Carlos Gaston Alvarez [mailto:[EMAIL PROTECTED]]
 Sent: Saturday, May 26, 2001 6:25 AM
 To: [EMAIL PROTECTED]
 Subject: jsp compacter to be released


 Hi there,

 I have the jsp compacter running and now I am doing the documentation.
 It is a reader that compact the jsps. It can also compact html.
 It works by taking out the blank spaces of html and
 javascript. So a jsp
 like this

 html
body
!-- comment --
script language=javascript
   !--
alert( %= message % );
--
 /script
!-- result = %= result % --
/body
 /html

 will become something like:

 htmlbodyscript language=javascript
 !--
 alert( %= message % );
 --
 /script!-- result = %= result % --/body/html

 My stimates is that it 'compacts' about a 10% ratio.

 My original idea was to integrate it with tomcat so at load time
 of the jsp
 file it compacts it so the source code is generated over
 'compacted' code. I
 will do it, but it will take me some time. I have a plan of action.

 1 - release it as stand alone aplication.
 2 - release it as tag library.
 3 - integrate it with jasper.
 4 -  ¿¿include another language??

 Step one is done.

 Step two needs the tag code to be optimized (for not creating so many
 objects).

 Step three ... well I will need some guidance. Anyway, you should
 be accord.
 And of course, it should have configuration so you can turn it on only if
 you want to and in the files that you want it.

 Step four  ¿velocity?


 I was thinking of sending the source at the list, it is about 20K zipped.
 Please, I need a committer to tell me wath to do.

 Thanks in advance,

 Gaston





RE: Vacation

2001-05-28 Thread GOMEZ Henri

 
 The buffers do belong to jakarta-tomcat-connectors/util, and 
in a perfect
 world we wouldn't have them duplicated - 3.3 should only use 
what's in
 connectors.
 
 I wouldn't mind making tomcat-connectors/util the master 
source for the
 buffer stuff, but it needs some changes in the build 
scripts. I'm not sure
 how other people would feel about this - we are very close 
to 3.3beta.
 

it would be great to have the buffer code in one place, but, i've never
really been comfortable with jakarta-tomcat-connectors/util being that
place.  it would make more sense to me to have something like
jakarta-tomcat-util, where common utility code like the buffers stuff
could live.  jtc should be just for connectors.

+1 and again why not a jakarta-tomcat-commons ?


if people don't want a whole new module for utility code, then 
i suppose
jtc is the next best place...

-kevin.




RE: cvs commit:jakarta-tomcat/src/share/org/apache/tomcat/util/buf DateTool.java

2001-05-28 Thread GOMEZ Henri

 
  It has all to do with standards. Tabs have been used for 
indentation
for
  at least the last 15 years ( that's when I started playing with
computers-
  and the tab was there ).

 But the point is that we're using SPACES... Since _EVER_... 
Discussion
 closed.

I really doubt you guys have been using spaces everywhere 
since JServ. Look
at Craig's source for JServ 2 (err, I mean, Catalina) : there are tabs
everywhere ;)

Frankly, I don't think we should make a big deal of the whole issue.

Space Wars - Vi Strike Back ?)



RE: connector status in tomcat 4

2001-05-28 Thread GOMEZ Henri

My question is what the status is on the apache connector in 
tomcat 4. I've
been testing Jakarta 4 in standalone mode and is very pleased 
with it, but
we can't run it like that once we release the system for all 
our students..
;)

There is actually 2 connectors for Apache Tomcat 4.0 :

- warp/webapp : Developped specifically for TC 4.0 have 
  autoconfig stuff but lack load-balancing or IIS/NES support

- ajp13/jk : Available since TC 3.2, works with TC 3.3 and
  now with 4.0 (thanks to Kevin). Miss the autoconfig stuff 
  (will came in ajp14) but have load-balancing and IIS/NES
  support.

Your contribution must match your need !) 



Re: connector status in tomcat 4

2001-05-28 Thread kevin seguin

GOMEZ Henri wrote:
 
 My question is what the status is on the apache connector in
 tomcat 4. I've
 been testing Jakarta 4 in standalone mode and is very pleased
 with it, but
 we can't run it like that once we release the system for all
 our students..
 ;)
 
 There is actually 2 connectors for Apache Tomcat 4.0 :
 
 - warp/webapp : Developped specifically for TC 4.0 have
   autoconfig stuff but lack load-balancing or IIS/NES support
 
 - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
   now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
   (will came in ajp14) but have load-balancing and IIS/NES
   support.
 

er...  the load-balancing doesn't work yet for tc 4 -- the java side of
it hasn't been done yet.  it shouldn't be too hard to do though :)  i
think it's just a matter of figuring out what to do with jvmRoute on the
java side (set a cookie??).

 Your contribution must match your need !)



RE: connector status in tomcat 4

2001-05-28 Thread Erik Hellman

Ok, so which one would you say should has highest priority?

Having a quick look at the CVS repository I see jakarta-tomcat-connectors,
which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. Is
this right? Won't ajp13/jk be included in tc4? Is it going to be replaced by
warp/webapp?

// Erik

 -Original Message-
 From: kevin seguin [mailto:[EMAIL PROTECTED]]
 Sent: Monday, May 28, 2001 3:05 PM
 To: [EMAIL PROTECTED]
 Subject: Re: connector status in tomcat 4


 GOMEZ Henri wrote:
 
  My question is what the status is on the apache connector in
  tomcat 4. I've
  been testing Jakarta 4 in standalone mode and is very pleased
  with it, but
  we can't run it like that once we release the system for all
  our students..
  ;)
 
  There is actually 2 connectors for Apache Tomcat 4.0 :
 
  - warp/webapp : Developped specifically for TC 4.0 have
autoconfig stuff but lack load-balancing or IIS/NES support
 
  - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
(will came in ajp14) but have load-balancing and IIS/NES
support.
 

 er...  the load-balancing doesn't work yet for tc 4 -- the java side of
 it hasn't been done yet.  it shouldn't be too hard to do though :)  i
 think it's just a matter of figuring out what to do with jvmRoute on the
 java side (set a cookie??).

  Your contribution must match your need !)




RE: jsp compacter to be released

2001-05-28 Thread Carlos Gaston Alvarez

I can modify it. It is not dificult.
But the main idea was not to run it for every page but to run it only once,
when the page is been loaded to be compiled. That way it would save
proccessing time. To put it as a tag library was an idea that came later so
everyone could use it. (inside the cache tag is more powerfull).
Anyway, it can run stand alone.

Chau,

Gaston


- Original Message -
From: Jon Stevens [EMAIL PROTECTED]
To: tomcat-dev [EMAIL PROTECTED]
Sent: Sunday, May 27, 2001 5:00 PM
Subject: Re: jsp compacter to be released


A better way to write this would be as a Servlet API 2.3 filter (assuming
they can work on an output stream...i forget...).

-jon

on 5/25/01 9:25 PM, Carlos Gaston Alvarez [EMAIL PROTECTED] wrote:

 Hi there,

   I have the jsp compacter running and now I am doing the documentation.
   It is a reader that compact the jsps. It can also compact html.
   It works by taking out the blank spaces of html and javascript. So a jsp
 like this

 html
  body
  !-- comment --
  script language=javascript
 !--
  alert( %= message % );
  --
   /script
  !-- result = %= result % --
  /body
 /html

 will become something like:

 htmlbodyscript language=javascript
 !--
 alert( %= message % );
 --
 /script!-- result = %= result % --/body/html

 My stimates is that it 'compacts' about a 10% ratio.

 My original idea was to integrate it with tomcat so at load time of the
jsp
 file it compacts it so the source code is generated over 'compacted' code.
I
 will do it, but it will take me some time. I have a plan of action.

 1 - release it as stand alone aplication.
 2 - release it as tag library.
 3 - integrate it with jasper.
 4 -  ¿¿include another language??

 Step one is done.

 Step two needs the tag code to be optimized (for not creating so many
 objects).

 Step three ... well I will need some guidance. Anyway, you should be
accord.
 And of course, it should have configuration so you can turn it on only if
 you want to and in the files that you want it.

 Step four  ¿velocity?


 I was thinking of sending the source at the list, it is about 20K zipped.
 Please, I need a committer to tell me wath to do.

 Thanks in advance,

 Gaston



--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
http://jakarta.apache.org/velocity/ymtd/ymtd.html





Re: connector status in tomcat 4

2001-05-28 Thread kevin seguin

 
 Ok, so which one would you say should has highest priority?
 

that probably depends on who you ask ;-)

 Having a quick look at the CVS repository I see jakarta-tomcat-connectors,
 which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. Is
 this right? Won't ajp13/jk be included in tc4? Is it going to be replaced by
 warp/webapp?
 

jakarta-tomcat-connectors (jtc) is a new module where connectors like
ajp, warp/webapp, etc. should live.  the idea is that the core parts of
connectors should be container-agnostic.  only the request/response
adapters should know about containers.

ajp/jk will not be included in tc4, but it will support tc4 -- there
will be (is) an ajp13 connector for tc 4 (it's is a work in progress). 
going forward, ajp connectors for tc 3, tc 4, and maybe other containers
will live in jtc.

warp/webapp will not replace ajp/jk, but it will give you another
choice.  you'll be free to make the decision yourself as to what
connector you want to use.

 // Erik
 
  -Original Message-
  From: kevin seguin [mailto:[EMAIL PROTECTED]]
  Sent: Monday, May 28, 2001 3:05 PM
  To: [EMAIL PROTECTED]
  Subject: Re: connector status in tomcat 4
 
 
  GOMEZ Henri wrote:
  
   My question is what the status is on the apache connector in
   tomcat 4. I've
   been testing Jakarta 4 in standalone mode and is very pleased
   with it, but
   we can't run it like that once we release the system for all
   our students..
   ;)
  
   There is actually 2 connectors for Apache Tomcat 4.0 :
  
   - warp/webapp : Developped specifically for TC 4.0 have
 autoconfig stuff but lack load-balancing or IIS/NES support
  
   - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
 now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
 (will came in ajp14) but have load-balancing and IIS/NES
 support.
  
 
  er...  the load-balancing doesn't work yet for tc 4 -- the java side of
  it hasn't been done yet.  it shouldn't be too hard to do though :)  i
  think it's just a matter of figuring out what to do with jvmRoute on the
  java side (set a cookie??).
 
   Your contribution must match your need !)



Re: connector status in tomcat 4

2001-05-28 Thread Dave Oxley

I thought the idea of warp/webapp was that it was to support servlet api 2.3 
and ajp/jk couldn't eaily be modified to support the new specs.

Dave
[EMAIL PROTECTED]


From: kevin seguin [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: connector status in tomcat  4
Date: Mon, 28 May 2001 09:52:43 -0500

 
  Ok, so which one would you say should has highest priority?
 

that probably depends on who you ask ;-)

  Having a quick look at the CVS repository I see 
jakarta-tomcat-connectors,
  which contains the jk-park, and in jakarta-tomcat I see the warp/webapp. 
Is
  this right? Won't ajp13/jk be included in tc4? Is it going to be 
replaced by
  warp/webapp?
 

jakarta-tomcat-connectors (jtc) is a new module where connectors like
ajp, warp/webapp, etc. should live.  the idea is that the core parts of
connectors should be container-agnostic.  only the request/response
adapters should know about containers.

ajp/jk will not be included in tc4, but it will support tc4 -- there
will be (is) an ajp13 connector for tc 4 (it's is a work in progress).
going forward, ajp connectors for tc 3, tc 4, and maybe other containers
will live in jtc.

warp/webapp will not replace ajp/jk, but it will give you another
choice.  you'll be free to make the decision yourself as to what
connector you want to use.

  // Erik
 
   -Original Message-
   From: kevin seguin [mailto:[EMAIL PROTECTED]]
   Sent: Monday, May 28, 2001 3:05 PM
   To: [EMAIL PROTECTED]
   Subject: Re: connector status in tomcat 4
  
  
   GOMEZ Henri wrote:
   
My question is what the status is on the apache connector in
tomcat 4. I've
been testing Jakarta 4 in standalone mode and is very pleased
with it, but
we can't run it like that once we release the system for all
our students..
;)
   
There is actually 2 connectors for Apache Tomcat 4.0 :
   
- warp/webapp : Developped specifically for TC 4.0 have
  autoconfig stuff but lack load-balancing or IIS/NES support
   
- ajp13/jk : Available since TC 3.2, works with TC 3.3 and
  now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
  (will came in ajp14) but have load-balancing and IIS/NES
  support.
   
  
   er...  the load-balancing doesn't work yet for tc 4 -- the java side 
of
   it hasn't been done yet.  it shouldn't be too hard to do though :)  i
   think it's just a matter of figuring out what to do with jvmRoute on 
the
   java side (set a cookie??).
  
Your contribution must match your need !)

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.




RE: connector status in tomcat 4

2001-05-28 Thread GOMEZ Henri

I thought the idea of warp/webapp was that it was to support 
servlet api 2.3 
and ajp/jk couldn't eaily be modified to support the new specs.

What's the supposed features in 2.3 that ajp/jk couldn't support ?
At least there will be in ajp14/jk the autoconfig (ie list of
URL/URI handled ) =

/examples/servlet/*
/examples/*.jsp
/examples/*.xml


Dave
[EMAIL PROTECTED]


From: kevin seguin [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: connector status in tomcat  4
Date: Mon, 28 May 2001 09:52:43 -0500

 
  Ok, so which one would you say should has highest priority?
 

that probably depends on who you ask ;-)

  Having a quick look at the CVS repository I see 
jakarta-tomcat-connectors,
  which contains the jk-park, and in jakarta-tomcat I see 
the warp/webapp. 
Is
  this right? Won't ajp13/jk be included in tc4? Is it going to be 
replaced by
  warp/webapp?
 

jakarta-tomcat-connectors (jtc) is a new module where connectors like
ajp, warp/webapp, etc. should live.  the idea is that the 
core parts of
connectors should be container-agnostic.  only the request/response
adapters should know about containers.

ajp/jk will not be included in tc4, but it will support tc4 -- there
will be (is) an ajp13 connector for tc 4 (it's is a work in progress).
going forward, ajp connectors for tc 3, tc 4, and maybe other 
containers
will live in jtc.

warp/webapp will not replace ajp/jk, but it will give you another
choice.  you'll be free to make the decision yourself as to what
connector you want to use.

  // Erik
 
   -Original Message-
   From: kevin seguin [mailto:[EMAIL PROTECTED]]
   Sent: Monday, May 28, 2001 3:05 PM
   To: [EMAIL PROTECTED]
   Subject: Re: connector status in tomcat 4
  
  
   GOMEZ Henri wrote:
   
My question is what the status is on the apache connector in
tomcat 4. I've
been testing Jakarta 4 in standalone mode and is very pleased
with it, but
we can't run it like that once we release the system for all
our students..
;)
   
There is actually 2 connectors for Apache Tomcat 4.0 :
   
- warp/webapp : Developped specifically for TC 4.0 have
  autoconfig stuff but lack load-balancing or IIS/NES support
   
- ajp13/jk : Available since TC 3.2, works with TC 3.3 and
  now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
  (will came in ajp14) but have load-balancing and IIS/NES
  support.
   
  
   er...  the load-balancing doesn't work yet for tc 4 -- 
the java side 
of
   it hasn't been done yet.  it shouldn't be too hard to do 
though :)  i
   think it's just a matter of figuring out what to do with 
jvmRoute on 
the
   java side (set a cookie??).
  
Your contribution must match your need !)

___
__
Get Your Private, Free E-mail from MSN Hotmail at 
http://www.hotmail.com.



RE: connector status in tomcat 4

2001-05-28 Thread Dave Oxley

In that case, what is the point of warp. Is it going to be faster, more 
scalable or something? If not why was it created?

Dave
[EMAIL PROTECTED]


From: GOMEZ Henri [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: connector status in tomcat 4
Date: Mon, 28 May 2001 17:43:41 +0200

 I thought the idea of warp/webapp was that it was to support
 servlet api 2.3
 and ajp/jk couldn't eaily be modified to support the new specs.

What's the supposed features in 2.3 that ajp/jk couldn't support ?
At least there will be in ajp14/jk the autoconfig (ie list of
URL/URI handled ) =

/examples/servlet/*
/examples/*.jsp
/examples/*.xml

 
 Dave
 [EMAIL PROTECTED]
 
 
 From: kevin seguin [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Re: connector status in tomcat  4
 Date: Mon, 28 May 2001 09:52:43 -0500
 
  
   Ok, so which one would you say should has highest priority?
  
 
 that probably depends on who you ask ;-)
 
   Having a quick look at the CVS repository I see
 jakarta-tomcat-connectors,
   which contains the jk-park, and in jakarta-tomcat I see
 the warp/webapp.
 Is
   this right? Won't ajp13/jk be included in tc4? Is it going to be
 replaced by
   warp/webapp?
  
 
 jakarta-tomcat-connectors (jtc) is a new module where connectors like
 ajp, warp/webapp, etc. should live.  the idea is that the
 core parts of
 connectors should be container-agnostic.  only the request/response
 adapters should know about containers.
 
 ajp/jk will not be included in tc4, but it will support tc4 -- there
 will be (is) an ajp13 connector for tc 4 (it's is a work in progress).
 going forward, ajp connectors for tc 3, tc 4, and maybe other
 containers
 will live in jtc.
 
 warp/webapp will not replace ajp/jk, but it will give you another
 choice.  you'll be free to make the decision yourself as to what
 connector you want to use.
 
   // Erik
  
-Original Message-
From: kevin seguin [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 3:05 PM
To: [EMAIL PROTECTED]
Subject: Re: connector status in tomcat 4
   
   
GOMEZ Henri wrote:

 My question is what the status is on the apache connector in
 tomcat 4. I've
 been testing Jakarta 4 in standalone mode and is very pleased
 with it, but
 we can't run it like that once we release the system for all
 our students..
 ;)

 There is actually 2 connectors for Apache Tomcat 4.0 :

 - warp/webapp : Developped specifically for TC 4.0 have
   autoconfig stuff but lack load-balancing or IIS/NES support

 - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
   now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
   (will came in ajp14) but have load-balancing and IIS/NES
   support.

   
er...  the load-balancing doesn't work yet for tc 4 --
 the java side
 of
it hasn't been done yet.  it shouldn't be too hard to do
 though :)  i
think it's just a matter of figuring out what to do with
 jvmRoute on
 the
java side (set a cookie??).
   
 Your contribution must match your need !)
 
 ___
 __
 Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.

_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.




Re: connector status in tomcat 4

2001-05-28 Thread kevin seguin

Dave Oxley wrote:
 
 I thought the idea of warp/webapp was that it was to support servlet api 2.3
 and ajp/jk couldn't eaily be modified to support the new specs.
 

i don't know all of the details of warp/webapp.  my main point was, both
ajp and warp/webapp will be usable with tc 4.  as a user, you are free
to look at the features of both, and based on your own requirements,
pick which is best for you.

for example, in my case, currently all i care about is being able to
forward requests based on uri from iis and netscape to tomcat.  so, for
me, ajp does what i need it to, while warp/webapp currently does not (no
iis/netscape support yet).  hence, i would pick ajp.

now, i'm not saying one is better than the other.  i'm just saying that
one might be better than the other in certain circumstances, and now you
have a choice.

 Dave
 [EMAIL PROTECTED]
 
 From: kevin seguin [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Re: connector status in tomcat  4
 Date: Mon, 28 May 2001 09:52:43 -0500
 
  
   Ok, so which one would you say should has highest priority?
  
 
 that probably depends on who you ask ;-)
 
   Having a quick look at the CVS repository I see
 jakarta-tomcat-connectors,
   which contains the jk-park, and in jakarta-tomcat I see the warp/webapp.
 Is
   this right? Won't ajp13/jk be included in tc4? Is it going to be
 replaced by
   warp/webapp?
  
 
 jakarta-tomcat-connectors (jtc) is a new module where connectors like
 ajp, warp/webapp, etc. should live.  the idea is that the core parts of
 connectors should be container-agnostic.  only the request/response
 adapters should know about containers.
 
 ajp/jk will not be included in tc4, but it will support tc4 -- there
 will be (is) an ajp13 connector for tc 4 (it's is a work in progress).
 going forward, ajp connectors for tc 3, tc 4, and maybe other containers
 will live in jtc.
 
 warp/webapp will not replace ajp/jk, but it will give you another
 choice.  you'll be free to make the decision yourself as to what
 connector you want to use.
 
   // Erik
  
-Original Message-
From: kevin seguin [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 3:05 PM
To: [EMAIL PROTECTED]
Subject: Re: connector status in tomcat 4
   
   
GOMEZ Henri wrote:

 My question is what the status is on the apache connector in
 tomcat 4. I've
 been testing Jakarta 4 in standalone mode and is very pleased
 with it, but
 we can't run it like that once we release the system for all
 our students..
 ;)

 There is actually 2 connectors for Apache Tomcat 4.0 :

 - warp/webapp : Developped specifically for TC 4.0 have
   autoconfig stuff but lack load-balancing or IIS/NES support

 - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
   now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
   (will came in ajp14) but have load-balancing and IIS/NES
   support.

   
er...  the load-balancing doesn't work yet for tc 4 -- the java side
 of
it hasn't been done yet.  it shouldn't be too hard to do though :)  i
think it's just a matter of figuring out what to do with jvmRoute on
 the
java side (set a cookie??).
   
 Your contribution must match your need !)
 
 _
 Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



RE: connector status in tomcat 4

2001-05-28 Thread GOMEZ Henri

In that case, what is the point of warp. Is it going to be 
faster, more scalable or something? 

warp is a whole new developpement using 
very recent lib tools like APR.

If not why was it created?

That's a good question and who has the answer ?

Dave
[EMAIL PROTECTED]


From: GOMEZ Henri [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: connector status in tomcat 4
Date: Mon, 28 May 2001 17:43:41 +0200

 I thought the idea of warp/webapp was that it was to support
 servlet api 2.3
 and ajp/jk couldn't eaily be modified to support the new specs.

What's the supposed features in 2.3 that ajp/jk couldn't support ?
At least there will be in ajp14/jk the autoconfig (ie list of
URL/URI handled ) =

/examples/servlet/*
/examples/*.jsp
/examples/*.xml

 
 Dave
 [EMAIL PROTECTED]
 
 
 From: kevin seguin [EMAIL PROTECTED]
 Reply-To: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: Re: connector status in tomcat  4
 Date: Mon, 28 May 2001 09:52:43 -0500
 
  
   Ok, so which one would you say should has highest priority?
  
 
 that probably depends on who you ask ;-)
 
   Having a quick look at the CVS repository I see
 jakarta-tomcat-connectors,
   which contains the jk-park, and in jakarta-tomcat I see
 the warp/webapp.
 Is
   this right? Won't ajp13/jk be included in tc4? Is it going to be
 replaced by
   warp/webapp?
  
 
 jakarta-tomcat-connectors (jtc) is a new module where 
connectors like
 ajp, warp/webapp, etc. should live.  the idea is that the
 core parts of
 connectors should be container-agnostic.  only the request/response
 adapters should know about containers.
 
 ajp/jk will not be included in tc4, but it will support 
tc4 -- there
 will be (is) an ajp13 connector for tc 4 (it's is a work 
in progress).
 going forward, ajp connectors for tc 3, tc 4, and maybe other
 containers
 will live in jtc.
 
 warp/webapp will not replace ajp/jk, but it will give you another
 choice.  you'll be free to make the decision yourself as to what
 connector you want to use.
 
   // Erik
  
-Original Message-
From: kevin seguin [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 3:05 PM
To: [EMAIL PROTECTED]
Subject: Re: connector status in tomcat 4
   
   
GOMEZ Henri wrote:

 My question is what the status is on the apache 
connector in
 tomcat 4. I've
 been testing Jakarta 4 in standalone mode and is 
very pleased
 with it, but
 we can't run it like that once we release the 
system for all
 our students..
 ;)

 There is actually 2 connectors for Apache Tomcat 4.0 :

 - warp/webapp : Developped specifically for TC 4.0 have
   autoconfig stuff but lack load-balancing or 
IIS/NES support

 - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
   now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
   (will came in ajp14) but have load-balancing and IIS/NES
   support.

   
er...  the load-balancing doesn't work yet for tc 4 --
 the java side
 of
it hasn't been done yet.  it shouldn't be too hard to do
 though :)  i
think it's just a matter of figuring out what to do with
 jvmRoute on
 the
java side (set a cookie??).
   
 Your contribution must match your need !)
 
 ___
 __
 Get Your Private, Free E-mail from MSN Hotmail at
http://www.hotmail.com.

___
__
Get Your Private, Free E-mail from MSN Hotmail at 
http://www.hotmail.com.



RE: connector status in tomcat 4

2001-05-28 Thread Erik Hellman

Ok, another question then.

What is it that the connector has to be able to do? Is it sufficient if it
simply can forward the HTTP request to tomcat or does it need to play around
with it? I guess it must do something or the disscusion on ajp13/jk and
warp/webapp wouldn't be.

// Erik

 -Original Message-
 From: kevin seguin [mailto:[EMAIL PROTECTED]]
 Sent: Monday, May 28, 2001 5:47 PM
 To: [EMAIL PROTECTED]
 Subject: Re: connector status in tomcat 4

 for example, in my case, currently all i care about is being able to
 forward requests based on uri from iis and netscape to tomcat.  so, for
 me, ajp does what i need it to, while warp/webapp currently does not (no
 iis/netscape support yet).  hence, i would pick ajp.

 now, i'm not saying one is better than the other.  i'm just saying that
 one might be better than the other in certain circumstances, and now you
 have a choice.





Re: connector status in tomcat 4

2001-05-28 Thread kevin seguin

Erik Hellman wrote:
 
 Ok, another question then.
 
 What is it that the connector has to be able to do? Is it sufficient if it
 simply can forward the HTTP request to tomcat or does it need to play around
 with it? I guess it must do something or the disscusion on ajp13/jk and
 warp/webapp wouldn't be.

i think in the simplest case, forwarding an HTTP request is enough.  i
think that some of the things warp/webapp might add are security
(honoring security stuff specified in a webapp's web.xml), auto-config,
etc..  again, i'm not that familiar with warp/webapp.  ajp14 will have
auto-config, too.


 
 // Erik
 
  -Original Message-
  From: kevin seguin [mailto:[EMAIL PROTECTED]]
  Sent: Monday, May 28, 2001 5:47 PM
  To: [EMAIL PROTECTED]
  Subject: Re: connector status in tomcat 4
 
  for example, in my case, currently all i care about is being able to
  forward requests based on uri from iis and netscape to tomcat.  so, for
  me, ajp does what i need it to, while warp/webapp currently does not (no
  iis/netscape support yet).  hence, i would pick ajp.
 
  now, i'm not saying one is better than the other.  i'm just saying that
  one might be better than the other in certain circumstances, and now you
  have a choice.
 



[PATCH] JSP Reload patch

2001-05-28 Thread Tuukk4 |[:)-| p4s4n3n

hey,
I'm sorry but i'm such a lamer with this CVS so i hope everything goes well. i think 
files should be as attachmets /you can flame me down now/ So the paches make Tomcat 
4.0 b6 to reload JSP classes as Servlet classes allready do..

Tuukka

---
--Me olemme keskella jotain. jossa olemme totaalisen ulkopuolisia--



Get 250 color business cards for FREE!
http://businesscards.lycos.com/vp/fastpath/

Index: ./jasper/src/share/org/apache/jasper/servlet/JspServlet.java
===
RCS file: 
/home/cvspublic/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/servlet/JspServlet.java,v
retrieving revision 1.17
diff -r1.17 JspServlet.java
4c4
  * Copyright (c) 1999 The Apache Software Foundation.  All rights 
---
  * Copyright (c) 1999 The Apache Software Foundation.  All rights
12c12
  *notice, this list of conditions and the following disclaimer. 
---
  *notice, this list of conditions and the following disclaimer.
20,21c20,21
  *any, must include the following acknowlegement:  
  *   This product includes software developed by the 
---
  *any, must include the following acknowlegement:
  *   This product includes software developed by the
28c28
  *from this software without prior written permission. For written 
---
  *from this software without prior written permission. For written
54c54
  */ 
---
  */
102c102
  * The JSP engine (a.k.a Jasper)! 
---
  * The JSP engine (a.k.a Jasper)!
122c122
   // ServletWrapper will set this 
---
   // ServletWrapper will set this
125c125
   
---
 
131c131
   
---
 
149,151c149,151
   
   private void loadIfNecessary(HttpServletRequest req, HttpServletResponse res) 
 throws JasperException, ServletException, FileNotFoundException 
---
 
   private void loadIfNecessary(HttpServletRequest req, HttpServletResponse res)
 throws JasperException, ServletException, FileNotFoundException
153,154c153,154
 // First try context attribute; if that fails then use the 
 // classpath init parameter. 
---
 // First try context attribute; if that fails then use the
 // classpath init parameter.
165c165
 } else 
---
 } else
167,169c167,169
 
 Constants.message(jsp.message.cp_is, 
   new Object[] { 
---
 
 Constants.message(jsp.message.cp_is,
   new Object[] {
172c172
   }, 
---
   },
175c175
 if (loadJSP(jspUri, cp, isErrorPage, req, res) 
---
 if (loadJSP(jspUri, cp, isErrorPage, req, res)
180,181c180,181
   
   public void service(HttpServletRequest request, 
---
 
   public void service(HttpServletRequest request,
184c184
   throws ServletException, IOException, FileNotFoundException 
---
   throws ServletException, IOException, FileNotFoundException
213c213
   response.sendError(HttpServletResponse.SC_NOT_FOUND, 
---
   response.sendError(HttpServletResponse.SC_NOT_FOUND,
233,234c233,234
   
   
---
 
 
254,255c254,255
 
   // Setup logging 
---
 
   // Setup logging
279c279
   none  
---
   none
289c289
 try {  
---
 try {
357,359c357,359
   Constants.message(jsp.message.scratch.dir.is, 
 new Object[] { 
 options.getScratchDir().toString() 
---
   Constants.message(jsp.message.scratch.dir.is,
 new Object[] {
 options.getScratchDir().toString()
366,368c366,368
 private void serviceJspFile(HttpServletRequest request, 
   HttpServletResponse response, String jspUri, 
   Throwable exception, boolean precompile) 
---
 private void serviceJspFile(HttpServletRequest request,
   HttpServletResponse response, String jspUri,
   Throwable exception, boolean precompile)
372c372
   
---
 
378c378
   
---
 
383,384c383,384
 boolean preCompile(HttpServletRequest request) 
 throws ServletException 
---
 boolean preCompile(HttpServletRequest request)
 throws ServletException
389c389
 
---
 
391c391
   // An equal sign was specified 
---
   // An equal sign was specified
405c405
   if (qString != null  
---
   if (qString != null 
414,415d413
 
 
417c415,417
 public void service (HttpServletRequest request, 
---
 
 
 public void service (HttpServletRequest request,
422c422
 String includeUri 
---
 String includeUri
435c435
   
---
 
477c477
   

tab vs spaces

2001-05-28 Thread Carlos Gaston Alvarez

Is there any good code formatter that fills our needs?
May be we can automate it in the checkin  diff proccesses.

Chau,

Gaston




Re: tab vs spaces

2001-05-28 Thread Jon Stevens

on 5/28/01 4:51 PM, Carlos Gaston Alvarez [EMAIL PROTECTED] wrote:

 Is there any good code formatter that fills our needs?
 May be we can automate it in the checkin  diff proccesses.
 
 Chau,
 
 Gaston

It isn't something that can be automated on the server side.

The problem is that a decision was agreed upon (search the archives) and
once again Costin doesn't feel the need to respect that decision.

-jon




Re: [SERVLET-INTEREST] ANNOUNCEMENT: Tomcat bundled with webmailengine.

2001-05-28 Thread Christian Rauh

Dear Pete,

I got very interested in the Andere product but cannot connecto to either
the product site, or your company's site. How may I reach info on Andere?

Christian Rauh
NewTrade

Bonham Pete wrote:
 
 Hi,
 
 Aliaron's product company - Andere ( www.andere.com ) - has
 made Andere/iS freely available for download.  Andere/iS is
 a servlet-based webmail engine bundled with Apache Tomcat.
 
 Andere/iS is feature-competitive with portal webmail
 solutions such as Hotmail, Yahoo Mail, etc. but allows you
 to deploy a private, branded webmail server, complementing
 your existing mail infrastructure. Additionally, we hope
 that you'll find that the user experience is unsurpassed.
 
 You can download the free beta trial version for a number of
 different platforms from:
 http://www.andere.com/andere-iS/download/download.html -
 just one of the many benefits of leveraging Tomcat is a
 great out-of-box experience - you should be up and running
 within 5 minutes of completing the download.
 
 We hope you enjoy Andere/iS and we'd love both your feedback
 and all requests for addtional packaging variants.
 
 Thanks! We hope that you'll find Andere/iS to be a killer
 app demonstrating the power of Tomcat.
 
 Have fun, Pete
 
 ps: In addition to installing it yourself, you can see
 Andere/iS in action at www.ooglee.com.
 
 --
 Pete Bonham, Chairman  CEO
 aliaron, inc.
 The Marketplace Building
 Ann Arbor, MI 48104 USA
 mailto:[EMAIL PROTECTED]
 Voice: 1.734.769.1177
 Fax:   1.734.769.0876
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 ___
 To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
 of the message signoff SERVLET-INTEREST.
 
 Archives: http://archives.java.sun.com/archives/servlet-interest.html
 Resources: http://java.sun.com/products/servlet/external-resources.html
 LISTSERV Help: http://www.lsoft.com/manuals/user/user.html



Re: synchronize keyword may produce deadlocks.

2001-05-28 Thread yhs1634



You do know your code has a typo that will cause deadlocks, don't
you?  See below...
SNIP

arrgh. i screwed that one up. correcting the typo allows the code
to run fine. ok..i cant prove it with my example code, but under 
heavy loads the deadlock does occurunfortunately im not yet
ready to distribute the code that did produce the deadlock under
heavy loads as open source. :(
i'd recommend against synchronize based on the behaviour i saw
but i cant prove it with example code right now. Dekker's algorithm
with a Thread.sleep(10) at the end seems to be the cure.
-Ys-
Free, encrypted, secure Web-based email at www.hushmail.com


Re: connector status in tomcat 4

2001-05-28 Thread Pier P. Fumagalli

Dave Oxley at [EMAIL PROTECTED] wrote:

 In that case, what is the point of warp. Is it going to be faster, more
 scalable or something? If not why was it created?

It has a completely different architecture and approach to the problem of
passing HTTP requests between two endpoints in remote servers... It tries
not to be a hack, and that's all, but I'm not going over the same fight I'm
dodging since months...

Pier




Re: connector status in tomcat 4

2001-05-28 Thread Pier P. Fumagalli

Erik Hellman at [EMAIL PROTECTED] wrote:

 Ok, another question then.
 
 What is it that the connector has to be able to do? Is it sufficient if it
 simply can forward the HTTP request to tomcat or does it need to play around
 with it? I guess it must do something or the disscusion on ajp13/jk and
 warp/webapp wouldn't be.

More or less... Yes, but it needs to do it in an efficient way, trying to be
as thin as possible and so on... Long story (and it's 2 am of a bank holiday
day right now :)

Pier




Re: connector status in tomcat 4

2001-05-28 Thread Pier P. Fumagalli

GOMEZ Henri at [EMAIL PROTECTED] wrote:

 In that case, what is the point of warp. Is it going to be
 faster, more scalable or something?
 
 warp is a whole new developpement using
 very recent lib tools like APR.

And a bunch of other features and improvements, but it seems that no one
ever listen to what I write - technically speaking :) :) :) :)

 If not why was it created?
 
 That's a good question and who has the answer ?

I do, and the mailing list archive... Check out for subjects like WARP :)

Pier




Re: connector status in tomcat 4

2001-05-28 Thread egcs12md

Where to download ajp13/jk  ajp14/jk connectors for Apache Tomcat 4.0 ?

- Original Message - 
From: kevin seguin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, May 28, 2001 9:04 PM
Subject: Re: connector status in tomcat 4


 GOMEZ Henri wrote:
 
  My question is what the status is on the apache connector in
  tomcat 4. I've
  been testing Jakarta 4 in standalone mode and is very pleased
  with it, but
  we can't run it like that once we release the system for all
  our students..
  ;)
 
  There is actually 2 connectors for Apache Tomcat 4.0 :
 
  - warp/webapp : Developped specifically for TC 4.0 have
autoconfig stuff but lack load-balancing or IIS/NES support
 
  - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
(will came in ajp14) but have load-balancing and IIS/NES
support.
 
 
 er...  the load-balancing doesn't work yet for tc 4 -- the java side of
 it hasn't been done yet.  it shouldn't be too hard to do though :)  i
 think it's just a matter of figuring out what to do with jvmRoute on the
 java side (set a cookie??).
 
  Your contribution must match your need !)
 



cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime BodyContentImpl.java

2001-05-28 Thread marcsaeg

marcsaeg01/05/28 17:55:33

  Modified:src/share/org/apache/jasper/runtime Tag: tomcat_32
BodyContentImpl.java
  Log:
  Larry found this one while comparing 3.2.2 with 3.3.  Hopefully this is the
  last time we need to 'fix' this buffer sizing problem.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.6.6.5   +9 -13 
jakarta-tomcat/src/share/org/apache/jasper/runtime/BodyContentImpl.java
  
  Index: BodyContentImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/jasper/runtime/BodyContentImpl.java,v
  retrieving revision 1.6.6.4
  retrieving revision 1.6.6.5
  diff -u -r1.6.6.4 -r1.6.6.5
  --- BodyContentImpl.java  2001/04/23 19:00:20 1.6.6.4
  +++ BodyContentImpl.java  2001/05/29 00:55:32 1.6.6.5
  @@ -109,19 +109,15 @@
   
   char[] tmp = null;
   
  - //XXX Should it be multiple of DEFAULT_BUFFER_SIZE??
  -
  -int newBufferSize = bufferSize * 2;
  -if (len = newBufferSize) {
  - bufferSize = newBufferSize;
  - tmp = new char [bufferSize];
  - } else {
  - tmp = new char [bufferSize + len];
  - bufferSize += len;
  - }
  - System.arraycopy(cb, 0, tmp, 0, cb.length);
  - cb = tmp;
  - tmp = null;
  +if(len = bufferSize){
  +bufferSize *= 2;
  +}else{
  +bufferSize += len;
  +}
  +tmp = new char[bufferSize];
  +System.arraycopy(cb, 0, tmp, 0, cb.length);
  +cb = tmp;
  +tmp = null;
   }
   
   /**
  
  
  



FW: 404 Not Found

2001-05-28 Thread Pier P. Fumagalli


-- Forwarded Message
From: Deshpande Anand [EMAIL PROTECTED]
Date: Sun, 27 May 2001 21:49:22 -0700 (PDT)
To: [EMAIL PROTECTED]
Subject: 404 Not Found

Please Help. I am getting following Error.


404 Not Found

The requested URL /tomcat/tomcat-3.2-doc/style.css was
not found on this server.


Apache/2.0.16 Server at jakarta.apache.org Port 80

http://jakarta.apache.org/tomcat/tomcat-3.2-doc/style.css


Anand Deshpande.

__
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/

-- End of Forwarded Message




Re: connector status in tomcat 4

2001-05-28 Thread Pier P. Fumagalli

egcs12md at [EMAIL PROTECTED] wrote:

 Where to download ajp13/jk  ajp14/jk connectors for Apache Tomcat 4.0 ?

Check out the jakarta-tomcat-connectors CVS module.

Pier




Re: connector status in tomcat 4

2001-05-28 Thread kevin seguin

egcs12md wrote:
 
 Where to download ajp13/jk  ajp14/jk connectors for Apache Tomcat 4.0 ?
 

you need to checkout the cvs module jakarta-tomcat-connectors and build
from source.  i don't think the build instructions are very detailed... 
the build.xml files will have to suffice for now.  anyway, short version
of instructions:

cvs co jakarta-tomcat-connectors
cd jakarta-tomcat-connectors/util
ant
cd ../jk
ant

i will be updating instructions, build.xml, etc. in the near future.

-kevin.

 - Original Message -
 From: kevin seguin [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Monday, May 28, 2001 9:04 PM
 Subject: Re: connector status in tomcat 4
 
  GOMEZ Henri wrote:
  
   My question is what the status is on the apache connector in
   tomcat 4. I've
   been testing Jakarta 4 in standalone mode and is very pleased
   with it, but
   we can't run it like that once we release the system for all
   our students..
   ;)
  
   There is actually 2 connectors for Apache Tomcat 4.0 :
  
   - warp/webapp : Developped specifically for TC 4.0 have
 autoconfig stuff but lack load-balancing or IIS/NES support
  
   - ajp13/jk : Available since TC 3.2, works with TC 3.3 and
 now with 4.0 (thanks to Kevin). Miss the autoconfig stuff
 (will came in ajp14) but have load-balancing and IIS/NES
 support.
  
 
  er...  the load-balancing doesn't work yet for tc 4 -- the java side of
  it hasn't been done yet.  it shouldn't be too hard to do though :)  i
  think it's just a matter of figuring out what to do with jvmRoute on the
  java side (set a cookie??).
 
   Your contribution must match your need !)
 



Re: connector status in tomcat 4

2001-05-28 Thread egcs12md

But I'm Win32 user !

- Original Message - 
From: Pier P. Fumagalli [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 29, 2001 9:00 AM
Subject: Re: connector status in tomcat 4


 egcs12md at [EMAIL PROTECTED] wrote:
 
  Where to download ajp13/jk  ajp14/jk connectors for Apache Tomcat 4.0 ?
 
 Check out the jakarta-tomcat-connectors CVS module.
 
 Pier
 
 



cvs commit: jakarta-tomcat/src/webpages index.html

2001-05-28 Thread marcsaeg

marcsaeg01/05/28 18:28:37

  Modified:src/share/org/apache/tomcat/core Tag: tomcat_32
Constants.java
   src/webpages Tag: tomcat_32 index.html
  Log:
  Updating version numbers for the Tomcat 3.2.2 final release.
  
  Revision  ChangesPath
  No   revision
  
  
  No   revision
  
  
  1.22.2.16 +1 -1  
jakarta-tomcat/src/share/org/apache/tomcat/core/Attic/Constants.java
  
  Index: Constants.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/core/Attic/Constants.java,v
  retrieving revision 1.22.2.15
  retrieving revision 1.22.2.16
  diff -u -r1.22.2.15 -r1.22.2.16
  --- Constants.java2001/05/11 23:21:44 1.22.2.15
  +++ Constants.java2001/05/29 01:28:35 1.22.2.16
  @@ -67,7 +67,7 @@
   
   public class Constants {
   public static final String TOMCAT_NAME = Tomcat Web Server;
  -public static final String TOMCAT_VERSION = 3.2.2 beta 5;
  +public static final String TOMCAT_VERSION = 3.2.2;
   
   public static final String JSP_NAME = JSP;
   public static final String JSP_VERSION = 1.1;
  
  
  
  No   revision
  
  
  No   revision
  
  
  1.13.2.18 +2 -2  jakarta-tomcat/src/webpages/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/webpages/index.html,v
  retrieving revision 1.13.2.17
  retrieving revision 1.13.2.18
  diff -u -r1.13.2.17 -r1.13.2.18
  --- index.html2001/05/11 23:21:42 1.13.2.17
  +++ index.html2001/05/29 01:28:36 1.13.2.18
  @@ -4,13 +4,13 @@
   meta http-equiv=Content-Type content=text/html; charset=iso-8859-1
   meta name=GENERATOR content=Mozilla/4.72 [en] (WinNT; U) [Netscape]
   meta name=Author content=Anil K. Vijendran
  -titleTomcat v3.2.2 beta 5/title
  +titleTomcat v3.2.2/title
   /head
   body bgcolor=#FF
   img SRC=tomcat.gif height=92 width=130 align=LEFTbfont face=Arial, 
Helvetica, sans-seriffont size=+3Tomcat/font/font/b 
   br
   bfont face=Arial, Helvetica, sans-seriffont size=-1Version
  -3.2.2 beta 5/font/font/b
  +3.2.2/font/font/b
   pThis is the default Tomcat home page. This page serves as a quick reference
   guide to related resources and is located at:
   ul
  
  
  



cvs commit: jakarta-tomcat-site/xdocs news.xml

2001-05-28 Thread marcsaeg

marcsaeg01/05/28 20:49:09

  Modified:docs news.html
   xdocsnews.xml
  Log:
  Removed some bogus stuff from previous edit.
  
  Revision  ChangesPath
  1.3   +4 -6  jakarta-tomcat-site/docs/news.html
  
  Index: news.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/docs/news.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- news.html 2001/05/29 03:21:45 1.2
  +++ news.html 2001/05/29 03:49:09 1.3
  @@ -105,19 +105,15 @@
 a name=News  StatusstrongNews  Status/strong/a
   /font
 /td/tr
  +  trtdbr//td/tr
 trtd
   blockquote
   h328 May 2001 - Jakarta Tomcat 3.2.2 
Released/h3
   pstrongTomcat 3.2.2/strong is 
a maintenance release that fixes
  -several bugs since the 3.2.1 release and fixes all known specification
  +several bugs since the 3.2.1 release and corrects all known specification
   compliance issues.  The release is available for download
   a href=http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2;here/a.
   /p
  -pstrongTomcat 
4.0-beta-5/strong is the latest update to the next
  -generation version of Tomcat 4.0.  It fixes two security vulnerabilities
  -that were discovered in Tomcat 4.0-b4 (and prior versions).  Anyone who
  -downloaded Tomcat 4.0-b4 is urged to update immediately.  Get your copy
  -a 
href=http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b4;here/a./p
   hr noshade= size=1 /
   h314 May 2001 - Jakarta Tomcat 
4.0-beta-5 Released/h3
   pstrongTomcat 
4.0-beta-5/strong is the latest update to the next
  @@ -223,7 +219,9 @@
   the subject b[NEWS]/b to bmarcsaeg at apache dot org/b. 
   /p
   /blockquote
  +/p
 /td/tr
  +  trtdbr//td/tr
   /table
   /td
   /tr
  
  
  
  1.3   +1 -7  jakarta-tomcat-site/xdocs/news.xml
  
  Index: news.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-site/xdocs/news.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- news.xml  2001/05/29 03:21:46 1.2
  +++ news.xml  2001/05/29 03:49:09 1.3
  @@ -13,16 +13,10 @@
   h328 May 2001 - Jakarta Tomcat 3.2.2 Released/h3
   
   pstrongTomcat 3.2.2/strong is a maintenance release that fixes
  -several bugs since the 3.2.1 release and fixes all known specification
  +several bugs since the 3.2.1 release and corrects all known specification
   compliance issues.  The release is available for download
   a href=http://jakarta.apache.org/builds/jakarta-tomcat/release/v3.2.2;here/a.
   /p
  -
  -pstrongTomcat 4.0-beta-5/strong is the latest update to the next
  -generation version of Tomcat 4.0.  It fixes two security vulnerabilities
  -that were discovered in Tomcat 4.0-b4 (and prior versions).  Anyone who
  -downloaded Tomcat 4.0-b4 is urged to update immediately.  Get your copy
  -a 
href=http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b4;here/a./p
   
   hr noshade= size=1/
 
  
  
  



jakarta-tomcat-4.0 nightly

2001-05-28 Thread SongDongsheng



Hi,

Why http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/not 
updating since jakarta-tomcat-4.0-20010523 ?


cvs commit: jakarta-tomcat-connectors/util README.txt

2001-05-28 Thread seguin

seguin  01/05/28 22:40:48

  Modified:util README.txt
  Log:
  a little (not much) better readme file.
  
  Revision  ChangesPath
  1.2   +3 -0  jakarta-tomcat-connectors/util/README.txt
  
  Index: README.txt
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/util/README.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.txt2001/05/16 23:17:27 1.1
  +++ README.txt2001/05/29 05:40:47 1.2
  @@ -3,3 +3,6 @@
   
   It probably doesn't belong in jakarta-tomcat-connectors, but perhaps
   in something like jakarta-tomcat-util, or something [seguin].
  +
  +To build, simply run ant.  The default target creates tomcat-util.jar
  +int ./build/lib.
  
  
  



cvs commit: jakarta-tomcat-connectors/util build.xml

2001-05-28 Thread seguin

seguin  01/05/28 22:41:18

  Modified:util build.xml
  Log:
  prime for build.properties file usage.
  
  Revision  ChangesPath
  1.2   +3 -0  jakarta-tomcat-connectors/util/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/util/build.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.xml 2001/05/16 23:17:26 1.1
  +++ build.xml 2001/05/29 05:41:18 1.2
  @@ -1,6 +1,9 @@
   project name=tomcat-util default=build-main basedir=.
   
   !-- = Initialize Property Values === --
  +property file=build.properties/
  +property file=${user.home}/build.properties/
  +
   property name=tomcat-util.build value=${basedir}/build/
   
   target name=build-prepare
  
  
  



cvs commit: jakarta-tomcat-connectors/jk/src/java/org/apache/ajp Ajp13.java

2001-05-28 Thread seguin

seguin  01/05/28 22:44:15

  Modified:jk/src/java/org/apache/ajp Ajp13.java
  Log:
  changed my email address in author tag.
  
  Revision  ChangesPath
  1.4   +1 -1  jakarta-tomcat-connectors/jk/src/java/org/apache/ajp/Ajp13.java
  
  Index: Ajp13.java
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/src/java/org/apache/ajp/Ajp13.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- Ajp13.java2001/05/17 23:55:32 1.3
  +++ Ajp13.java2001/05/29 05:44:15 1.4
  @@ -88,7 +88,7 @@
*
* @author Dan Milstein [[EMAIL PROTECTED]]
* @author Keith Wannamaker [[EMAIL PROTECTED]]
  - * @author Kevin Seguin [[EMAIL PROTECTED]]
  + * @author Kevin Seguin [[EMAIL PROTECTED]]
*/
   public class Ajp13 {
   
  
  
  



cvs commit: jakarta-tomcat-connectors/jk README.txt

2001-05-28 Thread seguin

seguin  01/05/28 22:46:45

  Modified:jk   README.txt
  Log:
  a little better readme file -- still a long way to go...
  
  Revision  ChangesPath
  1.2   +16 -3 jakarta-tomcat-connectors/jk/README.txt
  
  Index: README.txt
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/README.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- README.txt2001/05/12 05:52:39 1.1
  +++ README.txt2001/05/29 05:46:44 1.2
  @@ -1,8 +1,21 @@
  +This directory contains both the native and java-side code for
  +ajp connectors.
  +
  +Building
  +
  +Build tomcat-util.jar in jakarta-tomcat-connectors/util.
  +Copy build.properties.sample to build.properties.
  +Edit build.properties to taste.
  +Build ajp.jar by running ant.  The default target creates ./build/lib/ajp.jar.
  +
  +Tomcat 4
  +
   To use the ajp13 connector for tomcat 4:
   
  - 1) build ajp.jar
  - 2) copy ajp.jar to $TOMCAT4_HOME/{build|dist}/server/lib
  + 1) build tomcat-util.jar (in ../util)
  + 1) build ajp.jar (by running ant)
  + 2) copy ajp.jar, tomcat-util.jar to $TOMCAT4_HOME/{build|dist}/server/lib
3) add the following to server.xml:
   
Connector className=org.apache.ajp.tomcat4.Ajp13Connector
  -   port=8009 acceptCount=10 debug=10/
  +   port=8009 acceptCount=10 debug=0/
  
  
  



cvs commit: jakarta-tomcat-connectors/jk build.xml

2001-05-28 Thread seguin

seguin  01/05/28 22:47:16

  Modified:jk   build.xml
  Log:
  update to use build.properties files
  
  Revision  ChangesPath
  1.5   +2 -7  jakarta-tomcat-connectors/jk/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/jk/build.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- build.xml 2001/05/17 23:54:58 1.4
  +++ build.xml 2001/05/29 05:47:15 1.5
  @@ -1,13 +1,8 @@
   project name=jk default=build-main basedir=.
   
   !-- = Initialize Property Values === --
  -property name=tomcat4.home value=../../jakarta-tomcat-4.0/build/
  -property name=servletapi.home   value=../../jakarta-servletapi-4/dist/
  -property name=tomcat-util.home value=../util/build/
  -
  -property name=catalina.jar value=${tomcat4.home}/server/lib/catalina.jar/
  -property name=servlet.jar value=${servletapi.home}/lib/servlet.jar/
  -property name=tomcat-util.jar 
value=${tomcat-util.home}/lib/tomcat-util.jar/
  +property file=build.properties/
  +property file=${user.home}/build.properties/
   
   property name=jk.build value=${basedir}/build/
   
  
  
  



cvs commit: jakarta-tomcat-connectors/jk build.properties.sample

2001-05-28 Thread seguin

seguin  01/05/28 22:47:29

  Added:   jk   build.properties.sample
  Log:
  sample build.properties file
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-connectors/jk/build.properties.sample
  
  Index: build.properties.sample
  ===
  #
  # sample build.properties for ajp connector.
  # edit to taste...
  #
  # $Id: build.properties.sample,v 1.1 2001/05/29 05:47:29 seguin Exp $
  #
  
  catalina.jar = ../../jakarta-tomcat-4.0/build/server/lib/catalina.jar
  servlet.jar = ../../jakarta-servletapi-4/dist/lib/servlet.jar
  tomcat-util.jar = ../util/build/lib/tomcat-util.jar
  
  
  



[ANNOUNCEMENT] Tomcat 3.2.2 released

2001-05-28 Thread Marc Saegesser

I am pleased to announce that the Tomcat 3.2.2 release is now
available for download at

http://jakarta.apache.org/builds/tomcat/release/v3.2.2

Tomcat 3.2.2 is a maintenance release that fixes several bugs from version
3.2.1 and corrects all known specification compliance issues.  The release
notes file in src/doc/readme covers the details of the Tomcat 3.2.2 release.

Tomcat 3.2.2 is now the latest production quality Tomcat release.  Users of
version 3.2.1 and earlier release are encouraged to update to this release.

Marc A. Saegesser




Reloading modified included JSP files

2001-05-28 Thread Sankar Kondur


Hi,

I read an old post that said the problem of not reloading a modified inlude
file unless the outer file was also modified was going to be fixed in 3.x 

I tested this problem in 
 - 3.3 milestone 3 
 - 3.3 dev
 - 4.0 dev

but it doesn't seem to have been fixed.

Just wanted to know if it has been fixed. 


thanks,
Shankar