cvs commit: jakarta-tomcat-4.0/webapps/examples/servlets jndi.html index.html

2000-11-01 Thread remm

remm00/11/01 22:17:24

  Modified:webapps/examples/servlets index.html
  Added:   webapps/examples/servlets jndi.html
  Log:
  - Link the new JNDI sevlet example from the servlet examples index page
  
  Revision  ChangesPath
  1.2   +8 -0  jakarta-tomcat-4.0/webapps/examples/servlets/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/examples/servlets/index.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- index.html2000/08/17 00:58:20 1.1
  +++ index.html2000/11/02 06:17:24 1.2
  @@ -89,6 +89,14 @@
   
   
   
  +Naming
  +
  +Execute
  +
  +Source
  +
  +
  +
   Sessions
   
   Execute
  
  
  
  1.1  jakarta-tomcat-4.0/webapps/examples/servlets/jndi.html
  
  Index: jndi.html
  ===
  
  
  Untitled Document
  
  
  
  
  
  Source Code for Naming Example
 
   
  
  import java.io.IOException;
  import java.io.PrintWriter;
  import java.util.Enumeration;
  import java.util.Hashtable;
  import javax.servlet.*;
  import javax.servlet.http.*;
  import javax.naming.NamingException;
  import javax.naming.Context;
  import javax.naming.InitialContext;
  import javax.naming.NamingEnumeration;
  import javax.naming.directory.InitialDirContext;
  
  /**
   * Demonstration of the web application environment support.
   *
   * @author Remy Maucherat
   */
  
  public class JndiServlet 
  extends HttpServlet {
  
  
  public void doGet(HttpServletRequest request, 
HttpServletResponse response)
  throws ServletException, IOException {
  
  PrintWriter out = response.getWriter();
  response.setContentType("text/plain");
  
  Context ctx = null;
  
  try {
  ctx = new InitialContext();
  } catch (NamingException e) {
  out.println("Couldn't build an initial 
context : " + e);
  return;
  }
  
  try {
  Object value = ctx.lookup("java:/comp/env/maxExemptions)";
  out.println("Simple lookup test : 
");
  out.println("Max exemptions value : 
" + value);
  } catch (NamingException e) {
  out.println("JNDI lookup failed : 
" + e);
  }
  
  try {
  Context envCtx = (Context) ctx.lookup("java:/comp/env/");
  out.println("list() on /comp/env Context : 
");
  NamingEnumeration enum = ctx.list("java:/comp/env/");
  while (enum.hasMoreElements()) {
  out.print("Binding : ");
  out.println(enum.nextElement().toString());
  }
  out.println("listBindings() on /comp/env 
Context : ");
  enum = ctx.listBindings("java:/comp/env/");
  while (enum.hasMoreElements()) {
  out.print("Binding : ");
  out.println(enum.nextElement().toString());
  }
  } catch (NamingException e) {
  out.println("JNDI lookup failed : 
" + e);
  }
  
  }
  
  
  }
  
  
  
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/webapps/examples/WEB-INF web.xml

2000-11-01 Thread remm

remm00/11/01 22:16:49

  Modified:webapps/examples/WEB-INF web.xml
  Log:
  - Updated web.xml with some env-entry elements
  
  Revision  ChangesPath
  1.8   +35 -0 jakarta-tomcat-4.0/webapps/examples/WEB-INF/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/examples/WEB-INF/web.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- web.xml   2000/10/29 00:35:06 1.7
  +++ web.xml   2000/11/02 06:16:49 1.8
  @@ -138,4 +138,39 @@
 
   
   
  +
  +
  +
  +  minExemptions
  +  1
  +  java.lang.Integer
  +
  +
  +  foo/name1
  +  value1
  +  java.lang.String
  +
  +
  +  foo/bar/name2
  +  true
  +  java.lang.Boolean
  +
  +
  +  name3
  +  1
  +  java.lang.Integer
  +
  +
  +  foo/name4
  +  10
  +  java.lang.Integer
  +
  +
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/webapps/examples/WEB-INF/classes JndiServlet.java

2000-11-01 Thread remm

remm00/11/01 22:16:17

  Added:   webapps/examples/WEB-INF/classes JndiServlet.java
  Log:
  - Add a naming servlet example
  
  Revision  ChangesPath
  1.1  
jakarta-tomcat-4.0/webapps/examples/WEB-INF/classes/JndiServlet.java
  
  Index: JndiServlet.java
  ===
  /* $Id: JndiServlet.java,v 1.1 2000/11/02 06:16:16 remm Exp $
   *
   */
  
  import java.io.IOException;
  import java.io.PrintWriter;
  import java.util.Enumeration;
  import java.util.Hashtable;
  import javax.servlet.*;
  import javax.servlet.http.*;
  import javax.naming.NamingException;
  import javax.naming.Context;
  import javax.naming.InitialContext;
  import javax.naming.NamingEnumeration;
  import javax.naming.directory.InitialDirContext;
  
  /**
   * Demonstration of the web application environment support.
   *
   * @author Remy Maucherat
   */
  
  public class JndiServlet 
  extends HttpServlet {
  
  
  public void doGet(HttpServletRequest request, HttpServletResponse response)
  throws ServletException, IOException {
  
  PrintWriter out = response.getWriter();
  response.setContentType("text/plain");
  
  Context ctx = null;
  
  try {
  ctx = new InitialContext();
  } catch (NamingException e) {
  out.println("Couldn't build an initial context : " + e);
  return;
  }
  
  try {
  Object value = ctx.lookup("java:/comp/env/maxExemptions");
  out.println("Simple lookup test : ");
  out.println("Max exemptions value : " + value);
  } catch (NamingException e) {
  out.println("JNDI lookup failed : " + e);
  }
  
  try {
  Context envCtx = (Context) ctx.lookup("java:/comp/env/");
  out.println("list() on /comp/env Context : ");
  NamingEnumeration enum = ctx.list("java:/comp/env/");
  while (enum.hasMoreElements()) {
  out.print("Binding : ");
  out.println(enum.nextElement().toString());
  }
  out.println("listBindings() on /comp/env Context : ");
  enum = ctx.listBindings("java:/comp/env/");
  while (enum.hasMoreElements()) {
  out.print("Binding : ");
  out.println(enum.nextElement().toString());
  }
  } catch (NamingException e) {
  out.println("JNDI lookup failed : " + e);
  }
  
  }
  
  
  }
  
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/java javaURLContextFactory.java

2000-11-01 Thread remm

remm00/11/01 22:14:18

  Modified:catalina STATUS.html build.xml
   catalina/src/bin catalina.bat catalina.sh
   catalina/src/share/org/apache/catalina/core
LocalStrings.properties StandardContext.java
StandardContextValve.java
   catalina/src/share/org/apache/catalina/startup Catalina.java
Embedded.java EmbeddedManager.java
EmbeddedManagerMBean.java
  Added:   catalina/src/share/org/apache/naming Constants.java
ContextAccessController.java ContextBindings.java
EjbRefAddr.java LocalStrings.properties
NameParserImpl.java NamingContext.java
NamingContextBindingsEnumeration.java
NamingContextEnumeration.java NamingEntry.java
NamingService.java NamingServiceMBean.java
ResourceEnvRefAddr.java ResourceRefAddr.java
SelectorContext.java StringManager.java
   catalina/src/share/org/apache/naming/factory
LocalStrings.properties
   catalina/src/share/org/apache/naming/java
javaURLContextFactory.java
  Log:
  - JNDI implementation which provides a per web application naming environment.
  - 100% independent from Catalina (root package name : org.apache.naming).
  - The Context implementation supports federation, links and references.
  - Web application environment support ("java" URL scheme), which is a special
read-only JNDI context populated using the web app deployment descriptor.
  - Updated STATUS.html to reflect that addition.
  - Generic references are used for EJB and Resources. A set of factories
(org.apache.naming.factory) will be provided to interface various popular
J2EE providers, whenever possible.
  - Each web application can also get a writable initial context, which is NOT
accessible to other web applications.
  - Adds various switches in Catalina to enable / disable the naming support :
* "-nonaming" command line option completely disables naming
* Embedded.setUseNaming(false) also completely disables naming (useful is the
  embedding application provides its own naming environment)
* In server.xml, a new attribute of Context element, "useNaming" can be used
  to disable the naming support for a specific web application.
* By default, internal naming is enabled for each of the web applications.
  - Updates to the JMX wrapper to Embedded to reflect this.
  - JMX wrapper to the naming service (named NamingService). It has simple start
and stop commands which initialize / restore to previous values when you stop
the required environment variables.
  
  Revision  ChangesPath
  1.3   +1 -9  jakarta-tomcat-4.0/catalina/STATUS.html
  
  Index: STATUS.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/STATUS.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- STATUS.html   2000/10/10 01:25:22 1.2
  +++ STATUS.html   2000/11/02 06:14:07 1.3
  @@ -115,14 +115,6 @@
   Action Item
   Volunteers
 
  -  
  -Low
  -Implement the optional web application environment support
  -described in Section 9.9 of the Servlet API Specification Version 2.2,
  -and Chapter 5 of the Java2 Platform Enterprise Edition Version 1.2
  -Specification.
  ----
  -  
   
   
   
  @@ -313,7 +305,7 @@
   
   
   
  -$Id: STATUS.html,v 1.2 2000/10/10 01:25:22 craigmcc Exp $
  +$Id: STATUS.html,v 1.3 2000/11/02 06:14:07 remm Exp $
   
   
   
  
  
  
  1.19  +10 -3 jakarta-tomcat-4.0/catalina/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/build.xml,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- build.xml 2000/10/12 23:34:09 1.18
  +++ build.xml 2000/11/02 06:14:07 1.19
  @@ -82,7 +82,12 @@
   
   
  +   
includes="org/apache/catalina/startup/Bootstrap.class,org/apache/catalina/loader/**" 
  +   />
  +
   
 
   
  @@ -151,7 +156,8 @@
 
 
   
  +  basedir="${catalina.build}/classes" 
  +  excludes="**/org/apache/naming/**" />
 
   
   
  @@ -184,7 +190,8 @@
   
   
   
  +  basedir="${catalina.build}/classes" 
  +  excludes="**/org/apache/naming/**" />
   
 
   
  
  
  
  1.12  +2 -2  jakarta-tomcat-4.0/catalina/src/bin/catalina.bat
  
  Index: catalina.bat
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/bin/catalina.bat,v
  retrieving revision 1.11
  retrieving revision 1

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/java - New directory

2000-11-01 Thread remm

remm00/11/01 22:12:21

  jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/java - New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory - New directory

2000-11-01 Thread remm

remm00/11/01 22:12:16

  jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory - New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming - New directory

2000-11-01 Thread remm

remm00/11/01 22:12:10

  jakarta-tomcat-4.0/catalina/src/share/org/apache/naming - New directory

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

2000-11-01 Thread craigmcc

craigmcc00/11/01 20:41:15

  Modified:catalina/src/share/org/apache/catalina Globals.java
   webapps/ROOT index.html
  Added:   .RELEASE-NOTES-4.0-M5.txt
  Removed: .RELEASE-NOTES-4.0-M4.txt
  Log:
  Prepare for milestone 5.
  
  Revision  ChangesPath
  1.1  jakarta-tomcat-4.0/RELEASE-NOTES-4.0-M5.txt
  
  Index: RELEASE-NOTES-4.0-M5.txt
  ===
  Apache Tomcat Version 4.0 Milestone 5
  =
  Release Notes
  =
  
  $Id: RELEASE-NOTES-4.0-M5.txt,v 1.1 2000/11/02 04:41:14 craigmcc Exp $
  
  
  
  INTRODUCTION:
  
  This document describes the changes that have been made in the current
  milestone release of Apache Tomcat, relative to the previous milestone
  release.
  
  Bug reports should be entered at the interim bug reporting system for
  Jakarta projects at:
  
  http://znutar.cortexity.com:/
  
  Please use project codes "Catalina" and "Jasper" for servlet-related and
  JSP-related bug reports, respectively.
  
  
  
  NEW FEATURES:
  
  
  
  
  =
  BUG FIXES:
  =
  
  
  
  ==
  KNOWN PROBLEMS IN THIS RELEASE:
  ==
  
  No Web Connectors Available
  ---
  Current releases of Tomcat 4.0 only run in stand-alone mode.  A new web
  connector for Apache will be integrated shortly, followed by integration
  with the other servers currently supported by Tomcat 3.x.
  
  
  URL Decoding Incomplete
  ---
  Currently, Catalina does not decode the values returned by getServletPath()
  and getPathInfo(), as required by the Servlet Specification.  This will be
  dealt with after clarifications to the requirements are completed in the
  JSR-053 expert group.
  
  
  Redeploying From a Web Application Archive
  --
  If you attempt to undeploy, then redeploy, an application from the same
  web application archive file URL (where the URL refers to an actual WAR
  file, not to a directory), the redeploy will fail with error "zip file is
  closed".  There appears to be a problem in the JDK's JarURLConnection class
  where JAR files are cached, even after they are closed, so that a request
  for a connection to the same URL returns the previous JarFile object instead
  of a new one.  As a workaround, you should do one of the following:
  * Change the URL of the web application archive each time you redeploy.
  * Deploy from an unpacked directory (on the same server) instead of from
a WAR file (this is often more convenient in a development environment
anyway).
  
  
  Running Web Apps Under A Security Manager
  -
  Support for running individual web applications under the protection of a
  security manager has not yet been completed.
  
  
  
  
  
  1.14  +5 -5  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java
  
  Index: Globals.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- Globals.java  2000/11/02 03:20:50 1.13
  +++ Globals.java  2000/11/02 04:41:14 1.14
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.13 2000/11/02 03:20:50 craigmcc Exp $
  - * $Revision: 1.13 $
  - * $Date: 2000/11/02 03:20:50 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.14 2000/11/02 04:41:14 craigmcc Exp $
  + * $Revision: 1.14 $
  + * $Date: 2000/11/02 04:41:14 $
*
* 
*
  @@ -69,7 +69,7 @@
* Global constants that are applicable to multiple packages within Catalina.
*
* @author Craig R. McClanahan
  - * @version $Revision: 1.13 $ $Date: 2000/11/02 03:20:50 $
  + * @version $Revision: 1.14 $ $Date: 2000/11/02 04:41:14 $
*/
   
   public final class Globals {
  @@ -193,7 +193,7 @@
   /**
* The descriptive information about this server and version.
*/
  -public static final String SERVER_INFO = "Apache Tomcat/4.0-m4";
  +public static final String SERVER_INFO = "Apache Tomcat/4.0-dev";
   
   
   
  
  
  
  1.8   +2 -2  jakarta-tomcat-4.0/webapps/ROOT/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/ROOT/index.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- index.html20

[ANNOUNCE] Tomcat 4.0 Milestone 4

2000-11-01 Thread Craig R. McClanahan

We're pleased to announce the availabililty of milestone 4 of the Tomcat
4.0 servlet container and JSP engine.  Compared to milestone 3, this
release reflects the following changes:

* Implementation of all the changes between "public draft" and "proposed
final draft"
  of the Servlet 2.3 and JSP 1.2 specifications.

* Implementation of all remaining 2.3 / 1.2 features -- Tomcat 4.0 is
now a
  feature complete implementation of the new specs!

* Many bug fixes (see RELEASE-NOTES-4.0-M4.txt in the top level
directory).

Binary distributions of the new release are available from:

http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4

and source releases can be downloaded from:


http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-m4/src

If you are planning on building Tomcat 4.0-m4 from source, you will want
to pick up the corresponding distribution of the servlet API classes,
found in the same directory.  Users of the binary distribution need not
do this -- a servlet.jar file containing the most current version of the
servlet API classes is included in the "bin" directory of the binary
release.

Come and get it!

Craig McClanahan



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

2000-11-01 Thread craigmcc

craigmcc00/11/01 19:20:55

  Modified:catalina/src/share/org/apache/catalina Globals.java
   webapps/ROOT index.html
  Log:
  Update identifiers for Tomcat 4.0 milestone 4.
  
  Revision  ChangesPath
  1.13  +5 -5  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java
  
  Index: Globals.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- Globals.java  2000/10/28 18:56:03 1.12
  +++ Globals.java  2000/11/02 03:20:50 1.13
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.12 2000/10/28 18:56:03 craigmcc Exp $
  - * $Revision: 1.12 $
  - * $Date: 2000/10/28 18:56:03 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/Globals.java,v 
1.13 2000/11/02 03:20:50 craigmcc Exp $
  + * $Revision: 1.13 $
  + * $Date: 2000/11/02 03:20:50 $
*
* 
*
  @@ -69,7 +69,7 @@
* Global constants that are applicable to multiple packages within Catalina.
*
* @author Craig R. McClanahan
  - * @version $Revision: 1.12 $ $Date: 2000/10/28 18:56:03 $
  + * @version $Revision: 1.13 $ $Date: 2000/11/02 03:20:50 $
*/
   
   public final class Globals {
  @@ -193,7 +193,7 @@
   /**
* The descriptive information about this server and version.
*/
  -public static final String SERVER_INFO = "Apache Tomcat/4.0-dev";
  +public static final String SERVER_INFO = "Apache Tomcat/4.0-m4";
   
   
   
  
  
  
  1.7   +2 -2  jakarta-tomcat-4.0/webapps/ROOT/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/ROOT/index.html,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- index.html2000/10/10 04:56:28 1.6
  +++ index.html2000/11/02 03:20:54 1.7
  @@ -4,13 +4,13 @@
   
   
   
  -Tomcat (v4.0-dev)
  +Tomcat (v4.0-m4)
   
   
   Tomcat 
   
   Version
  -4.0-dev
  +4.0-m4
   This is the default Tomcat home page. This page serves as a quick reference
   guide to related resources and is located at:
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tools testdriver.jar

2000-11-01 Thread craigmcc

craigmcc00/11/01 18:24:45

  Modified:.testdriver.jar
  Log:
  Update testdriver.jar to the version required by jakarta-watchdog-4.0
  tests.
  
  Revision  ChangesPath
  1.2   +183 -18   jakarta-tools/testdriver.jar
  
<>
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Redirect Tomcat System.out/System.err to logfile?

2000-11-01 Thread Jason Pell

Hello,

Is there a way I can redirect System.out/System.err to logfile.

Someone said that these go to the console where tomcat was started, but
I use the "daemon tomcat start" command, so I am not sure that there is
any
output generated at all in daemon mode.

I would therefore like to redirect to logfile instead.

Thanks
Jason

--
Jason Pell
Senior Analyst/Programmer
Deakin Software Services Pty Ltd
12 Gheringhap St, Geelong Victoria 3220 Australia
Phone: 03 5227 8858 International: +61 3 5227 8858
Fax: 03 5227 8907 International: +61 3 5227 8907
E-mail [EMAIL PROTECTED]
http://www.dssonline.com.au
Customer Support Hotline: 1800 620 497

"Callista - the brightest solution in university management"

---
Important Notice: The contents of this email transmission,
including attachments, may be privileged and confidential.
Any unauthorised use of the contents is expressly prohibited.
If you have received this transmission in error, please advise
the sender by return email or telephone immediately and
destroy all versions.
---



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources messages.properties messages_es.properties

2000-11-01 Thread pierred

pierred 00/11/01 17:12:18

  Modified:jasper/src/share/org/apache/jasper/resources
messages.properties messages_es.properties
  Log:
  Add identity of faulty TLD file in message
  jsp.error.more.than.one.taglib
  
  Revision  ChangesPath
  1.9   +2 -2  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources/messages.properties
  
  Index: messages.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources/messages.properties,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- messages.properties   2000/10/31 22:54:13 1.8
  +++ messages.properties   2000/11/02 01:12:16 1.9
  @@ -1,4 +1,4 @@
  -# $Id: messages.properties,v 1.8 2000/10/31 22:54:13 pierred Exp $
  +# $Id: messages.properties,v 1.9 2000/11/02 01:12:16 pierred Exp $
   #
   # Default localized string information
   # Localized this the Default Locale as is en_US
  @@ -119,7 +119,7 @@
   jsp.warning.unknown.element.in.TLD=Warning: Unknown element {0} in TLD
   jsp.warning.unknown.element.in.tag=Warning: Unknown element {0} in tag
   jsp.warning.unknown.element.in.attribute=Warning: Unknown element {0} in attribute
  -jsp.error.more.than.one.taglib=More than one taglib in the TLD
  +jsp.error.more.than.one.taglib=More than one taglib in the TLD: {0}
   jsp.warning.teiclass.is.null=Could not load TagExtraInfo class {0}: {1}
   jsp.error.parse.error.in.TLD=Parse Error in the tag library descriptor: {0}
   jsp.error.unable.to.open.TLD=Unable to open the tag library descriptor: {0}
  
  
  
  1.5   +2 -2  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources/messages_es.properties
  
  Index: messages_es.properties
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/resources/messages_es.properties,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- messages_es.properties2000/10/04 05:10:58 1.4
  +++ messages_es.properties2000/11/02 01:12:16 1.5
  @@ -1,4 +1,4 @@
  -# $Id: messages_es.properties,v 1.4 2000/10/04 05:10:58 pierred Exp $
  +# $Id: messages_es.properties,v 1.5 2000/11/02 01:12:16 pierred Exp $
   #
   # Default localized string information
   # Localized para Locale es_ES
  @@ -113,7 +113,7 @@
   jsp.warning.unknown.element.in.TLD=Aviso: Elemento {0} desconocido en el TLD
   jsp.warning.unknown.element.in.tag=Aviso: Elemento {0} desconocido en el tag
   jsp.warning.unknown.element.in.attribute=Aviso: Elemento {0} desconocido en el 
atributo
  -jsp.error.more.than.one.taglib=Mas de una libreria de tags en el TLD
  +jsp.error.more.than.one.taglib=Mas de una libreria de tags en el TLD: {0}
   jsp.warning.teiclass.is.null=No se puedee cargar la clase TagExtraInfo llamada {0}: 
{1}
   jsp.error.parse.error.in.TLD=Error de analisis en el descriptor de libreria de 
tags: {0}
   jsp.error.unable.to.open.TLD=No se puede abrir el descriptor de libreria de tags: 
{0}
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler TagLibrariesGlobal.java TagLibraryInfoImpl.java

2000-11-01 Thread pierred

pierred 00/11/01 17:08:42

  Modified:jasper/src/share/org/apache/jasper/compiler
TagLibrariesGlobal.java TagLibraryInfoImpl.java
  Log:
  Simply log an error instead of throwing an exception
  when problem processing a TLD.
  Also give the name of the TLD in the error message.
  
  Revision  ChangesPath
  1.3   +12 -6 
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibrariesGlobal.java
  
  Index: TagLibrariesGlobal.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibrariesGlobal.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- TagLibrariesGlobal.java   2000/11/02 00:43:20 1.2
  +++ TagLibrariesGlobal.java   2000/11/02 01:08:41 1.3
  @@ -74,8 +74,8 @@
   
   import org.apache.jasper.Constants;
   import org.apache.jasper.JasperException;
  +import org.apache.jasper.logging.Logger;
   
  -
   /**
* A container for all tag libraries that are defined "globally"
* for the web application.
  @@ -142,10 +142,12 @@
   {
   // Parse web.xml
InputStream is = ctxt.getResourceAsStream(WEB_XML);
  +
if (is == null) {
  - throw new JasperException(
  - Constants.getString("jsp.error.internal.filenotfound", 
  - new Object[]{WEB_XML}));
  + Constants.message("jsp.error.internal.filenotfound", 
  +   new Object[]{WEB_XML},
  +   Logger.WARNING);
  + return;
}
Document webtld =
JspUtil.parseXMLDoc(WEB_XML, is);
  @@ -271,8 +273,12 @@
   {
Document tld = JspUtil.parseXMLDoc(resourcePath, in);
   NodeList list = tld.getElementsByTagName("taglib");
  -if (list.getLength() != 1)
  -throw new 
JasperException(Constants.getString("jsp.error.more.than.one.taglib"));
  +if (list.getLength() != 1) {
  + Constants.message("jsp.error.more.than.one.taglib",
  +   new Object[]{resourcePath},
  +   Logger.ERROR);
  + return null;
  + }
   
   Element elem = (Element)list.item(0);
   list = elem.getChildNodes();
  
  
  
  1.12  +6 -4  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java
  
  Index: TagLibraryInfoImpl.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- TagLibraryInfoImpl.java   2000/11/01 20:25:09 1.11
  +++ TagLibraryInfoImpl.java   2000/11/02 01:08:41 1.12
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java,v
 1.11 2000/11/01 20:25:09 pierred Exp $
  - * $Revision: 1.11 $
  - * $Date: 2000/11/01 20:25:09 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibraryInfoImpl.java,v
 1.12 2000/11/02 01:08:41 pierred Exp $
  + * $Revision: 1.12 $
  + * $Date: 2000/11/02 01:08:41 $
*
* The Apache Software License, Version 1.1
*
  @@ -267,7 +267,9 @@
   NodeList list = tld.getElementsByTagName("taglib");
   
   if (list.getLength() != 1)
  -throw new 
JasperException(Constants.getString("jsp.error.more.than.one.taglib"));
  +throw new JasperException(
  +Constants.getString("jsp.error.more.than.one.taglib",
  +new Object[]{uri}));
   
   Element elem = (Element) list.item(0);
   list = elem.getChildNodes();
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup HostConfig.java

2000-11-01 Thread craigmcc

craigmcc00/11/01 17:00:17

  Modified:.RELEASE-NOTES-4.0-M4.txt
   catalina/src/share/org/apache/catalina/startup
HostConfig.java
  Log:
  Deploy a directory (under webapps) as an application if it at least has
  a WEB-INF subdirectory inside.  Previously, tested for the existence of
  a web.xml file, which isn't strictly necessary given the defaults that are
  loaded from $CATALINA_HOME/conf/web.xml.
  
  Revision  ChangesPath
  1.3   +5 -1  jakarta-tomcat-4.0/RELEASE-NOTES-4.0-M4.txt
  
  Index: RELEASE-NOTES-4.0-M4.txt
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/RELEASE-NOTES-4.0-M4.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- RELEASE-NOTES-4.0-M4.txt  2000/11/01 00:39:32 1.2
  +++ RELEASE-NOTES-4.0-M4.txt  2000/11/02 01:00:16 1.3
  @@ -3,7 +3,7 @@
   Release Notes
   =
   
  -$Id: RELEASE-NOTES-4.0-M4.txt,v 1.2 2000/11/01 00:39:32 craigmcc Exp $
  +$Id: RELEASE-NOTES-4.0-M4.txt,v 1.3 2000/11/02 01:00:16 craigmcc Exp $
   
   
   
  @@ -95,7 +95,9 @@
   web applications configured, some that require client certificates and some
   that do not, communicating through the same SSL sockets.
   
  +Jasper:  Support the new TryCatchFinally interface for tag libraries.
   
  +
   =
   BUG FIXES:
   =
  @@ -118,6 +120,8 @@
   
   Jasper:  Accept the "jsp_precompile=" query parameter in conformance to the
   specification.
  +
  +Jasper:  Do not complain if there is no web.xml file present.
   
   
   ==
  
  
  
  1.3   +8 -8  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/HostConfig.java
  
  Index: HostConfig.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/HostConfig.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- HostConfig.java   2000/10/04 23:03:05 1.2
  +++ HostConfig.java   2000/11/02 01:00:16 1.3
  @@ -1,7 +1,7 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/HostConfig.java,v
 1.2 2000/10/04 23:03:05 craigmcc Exp $
  - * $Revision: 1.2 $
  - * $Date: 2000/10/04 23:03:05 $
  + * $Header: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/startup/HostConfig.java,v
 1.3 2000/11/02 01:00:16 craigmcc Exp $
  + * $Revision: 1.3 $
  + * $Date: 2000/11/02 01:00:16 $
*
* 
*
  @@ -93,7 +93,7 @@
* of that Host, and the associated defined contexts.
*
* @author Craig R. McClanahan
  - * @version $Revision: 1.2 $ $Date: 2000/10/04 23:03:05 $
  + * @version $Revision: 1.3 $ $Date: 2000/11/02 01:00:16 $
*/
   
   public final class HostConfig
  @@ -273,10 +273,10 @@
   File dir = new File(appBase, files[i]);
   if (dir.isDirectory()) {
   
  -// Make sure there is an application deployment descriptor
  -File webXml = new File(dir, "/WEB-INF/web.xml");
  -if (!webXml.exists() || !webXml.isFile() ||
  -!webXml.canRead())
  +// Make sure there is an application configuration directory
  +File webInf = new File(dir, "/WEB-INF");
  +if (!webInf.exists() || !webInf.isDirectory() ||
  +!webInf.canRead())
   continue;
   
   // Calculate the context path and make sure it is unique
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




RE: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util MessageBytes.java MimeHeaders.java MimeMap.java SessionIdGenerator.java

2000-11-01 Thread Larry Isaacs

Hi Costin,

Good to see you back.

FYI: My helper\SessionUtil.java is still looking for
SessionIdGenerator.generateId().  Did you mean to commit SessionUtil.java
too?

Cheers,
Larry

-Original Message-
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: 11/1/00 4:43 PM
Subject: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util MessageBytes.java 
MimeHeaders.java MimeMap.java SessionIdGenerator.java

costin  00/11/01 13:43:29

  Modified:src/share/org/apache/tomcat/util MessageBytes.java
MimeHeaders.java MimeMap.java
SessionIdGenerator.java
  Log:
  - added indexOf( c, starting ) to MessageBytes
  
  - in SessionIdGenerator, allow the caller to pass a Random source.
  That will allow to configure the SessionInterceptor to use a certain
  random instead of making config decisions at tomcat.util level.
  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/context AutoSetup.java

2000-11-01 Thread nacho

nacho   00/11/01 16:43:48

  Modified:src/share/org/apache/tomcat/context AutoSetup.java
  Log:
  Adapting code to new start order.
  
  Revision  ChangesPath
  1.18  +15 -19
jakarta-tomcat/src/share/org/apache/tomcat/context/AutoSetup.java
  
  Index: AutoSetup.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/context/AutoSetup.java,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- AutoSetup.java2000/09/29 21:09:19 1.17
  +++ AutoSetup.java2000/11/02 00:43:48 1.18
  @@ -83,23 +83,6 @@
   public AutoSetup() {
   }
   
  -/** Take note of the added contexts.
  - *  We can enhance the auto-setup for virtual hosts too,
  - *  but it's up to this class how it deals with that and
  - *  existing contexts. 
  - */
  -public void addContext(ContextManager cm, Context ctx)
  - throws TomcatException
  -{
  - if( ctx.getHost()== null ) {
  - // this is a context that goes into the default server
  - // we care only about the root context for autosetup
  - // until we define a pattern for automatic vhost setup.
  - definedContexts.put( ctx.getPath(), ctx );
  - if(debug>0) log("Register explicit context " + ctx.getPath());
  - }
  -}
  -
   /** This will add all contexts to the default host.
*   We need a mechanism ( or convention ) to configure
*  virtual hosts too
  @@ -112,7 +95,19 @@
log("No webapps/ directory " + webappD );
return ; // nothing to set up
}
  - 
  +
  +Enumeration en=cm.getContexts();
  +while (en.hasMoreElements()){
  +Context ctx=(Context)en.nextElement();
  +if( ctx.getHost()== null ) {
  +// this is a context that goes into the default server
  +// we care only about the root context for autosetup
  +// until we define a pattern for automatic vhost setup.
  +definedContexts.put( ctx.getPath(), ctx );
  +if(debug>0) log("Register explicit context " + ctx.getPath());
  +}
  +}
  +
String[] list = webappD.list();
if( list.length==0 ) {
log("No apps in webapps/ ");
  @@ -123,7 +118,7 @@
String fname=name.substring(0, name.length()-4);
File appDir=new File( home + "/webapps/" + fname);
if( ! appDir.exists() ) {
  - // no check if war file is "newer" than directory 
  + // no check if war file is "newer" than directory
// To update you need to "remove" the context first!!!
appDir.mkdirs();
// Expand war file
  @@ -163,6 +158,7 @@
   Context ctx=new Context();
   ctx.setContextManager( cm );
   ctx.setPath(path);
  +definedContexts.put( path, ctx );
   // use absolute filename based on CM home instead of relative
   // don't assume HOME==TOMCAT_HOME
   ctx.setDocBase( f.getAbsolutePath() );
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler TagLibrariesGlobal.java

2000-11-01 Thread pierred

pierred 00/11/01 16:43:20

  Modified:jasper/src/share/org/apache/jasper/compiler
TagLibrariesGlobal.java
  Log:
  Bug fix: use proper key for error message
  'jsp.error.internal.filenotfound'
  
  Revision  ChangesPath
  1.2   +1 -1  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibrariesGlobal.java
  
  Index: TagLibrariesGlobal.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagLibrariesGlobal.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- TagLibrariesGlobal.java   2000/10/31 23:01:50 1.1
  +++ TagLibrariesGlobal.java   2000/11/02 00:43:20 1.2
  @@ -144,7 +144,7 @@
InputStream is = ctxt.getResourceAsStream(WEB_XML);
if (is == null) {
throw new JasperException(
  - Constants.getString("jsp.error.internal.file.not.found", 
  + Constants.getString("jsp.error.internal.filenotfound", 
new Object[]{WEB_XML}));
}
Document webtld =
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util SessionIdGenerator.java

2000-11-01 Thread nacho

nacho   00/11/01 16:42:58

  Modified:src/share/org/apache/tomcat/util SessionIdGenerator.java
  Log:
  XXX Fixing the build quick and dirty need review
  
  Revision  ChangesPath
  1.6   +4 -0  
jakarta-tomcat/src/share/org/apache/tomcat/util/SessionIdGenerator.java
  
  Index: SessionIdGenerator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/SessionIdGenerator.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- SessionIdGenerator.java   2000/11/01 21:43:28 1.5
  +++ SessionIdGenerator.java   2000/11/02 00:42:57 1.6
  @@ -189,4 +189,8 @@
   public static synchronized String generateId(Random randomSource) {
   return getIdentifier(randomSource, null);
   }
  +
  +public static synchronized String generateId() {
  +return getIdentifier(globalRandomSource, null);
  +}
   }
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat/src/facade22/org/apache/tomcat/modules/facade22 JspInterceptor.java

2000-11-01 Thread nacho

nacho   00/11/01 16:41:23

  Modified:src/facade22/org/apache/tomcat/modules/facade22
JspInterceptor.java
  Log:
  Adding some (little mangling) to packagename, bugs in the handling
  of pages in the root of the context.
  
  Revision  ChangesPath
  1.8   +64 -20
jakarta-tomcat/src/facade22/org/apache/tomcat/modules/facade22/JspInterceptor.java
  
  Index: JspInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/facade22/org/apache/tomcat/modules/facade22/JspInterceptor.java,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- JspInterceptor.java   2000/09/30 04:03:35 1.7
  +++ JspInterceptor.java   2000/11/02 00:41:23 1.8
  @@ -218,9 +218,12 @@
if( debug > 0 ) log( "Compiling " + jspInfo.realClassPath);
try {
// make sure we have the directories
  - File dir=new File( jspInfo.outputDir + "/" + jspInfo.pkgDir);
  +File dir;
  +if (jspInfo.pkgDir!=null)
  + dir=new File( jspInfo.outputDir + "/" + jspInfo.pkgDir);
  +else
  + dir=new File( jspInfo.outputDir);
dir.mkdirs();
  - 
JspMangler mangler= new JspMangler(jspInfo);
TomcatOptions options=new TomcatOptions();
JspEngineContext1 ctxt = new JspEngineContext1(req, mangler);
  @@ -346,7 +349,7 @@
   class JspInfo {
   Request request;
   
  -String uri; // path 
  +String uri; // path
   
   int version; // version
   
  @@ -371,7 +374,7 @@
   
   public String toString() {
return uri +" " + version;
  -}  
  +}
   
   /** Update compile time
*/
  @@ -389,26 +392,62 @@
   /** Update all paths that contain version number
*/
   void updateVersionedPaths() {
  - classN = baseClassN + "_" + version;
  - realClassPath = outputDir + "/" + pkgDir + "/" +
  - classN + ".class";
  - javaFilePath = outputDir + "/" + pkgDir + "/" +
  - classN + ".java";
  - fullClassN = pkg +"." + classN;
  - 
  +if( pkgDir!=null ) {
  +classN = baseClassN + "_" + version;
  +realClassPath = outputDir + "/" + pkgDir + "/" + classN + ".class";
  +javaFilePath = outputDir + "/" + pkgDir + "/" + classN + ".java";
  +fullClassN = pkg  + "." + classN;
  +} else {
  +classN = baseClassN + "_" + version;
  +realClassPath = outputDir + "/" +  classN + ".class";
  +javaFilePath = outputDir + "/" + classN + ".java";
  +fullClassN = classN;
  +}
  +
   //   log("ClassN=" + classN +
   //  " realClassPath=" + realClassPath +
   //  " javaFilePath=" + javaFilePath +
   //  " fullClassN =" + fullClassN);
writeVersion();
  - // save to mapFile 
  + // save to mapFile
   }
   
  +private static String [] keywords = {
  +"abstract", "boolean", "break", "byte",
  +"case", "catch", "char", "class",
  +"const", "continue", "default", "do",
  +"double", "else", "extends", "final",
  +"finally", "float", "for", "goto",
  +"if", "implements", "import",
  +"instanceof", "int", "interface",
  +"long", "native", "new", "package",
  +"private", "protected", "public",
  +"return", "short", "static", "super",
  +"switch", "synchronized", "this",
  +"throw", "throws", "transient",
  +"try", "void", "volatile", "while"
  +};
  +
  +/** Mangle Package names to avoid reserver words **/
  +private String manglePackage(String s){
  + for (int i = 0; i < keywords.length; i++) {
  +char fs = File.separatorChar;
  +int index = s.indexOf(keywords[i]);
  +if(index == -1 ) continue;
  +while (index != -1) {
  +String tmpathName = s.substring (0,index) + "__";
  +s = tmpathName + s.substring (index);
  +index = s.indexOf(keywords[i],index+3);
  +}
  +}
  +return(s);
  +}
  +
   /** Compute various names used
*/
   void init(Request req ) {
this.request = req;
  - //  String includeUri 
  + //  String includeUri
//  = (String) req.getAttribute(Constants.INC_SERVLET_PATH);
uri=req.getServletPath();
Context ctx=req.getContext();
  @@ -429,11 +468,13 @@
}
   
if( pkgDir!=null ) {
  +pkgDir=manglePackage(pkgDir);
pkgDir=pkgDir.replace('.', '_');
pkg=pkgDir.replace('/', '.');
//  pkgDir=pkgDir.replace('/', File.separator );
  +
}
  - 
  +
int extIdx=endUnproc.lastIndexOf( "." );
   
if( extIdx>=0 ) {
  @@ -443,8 +484,11 @@
baseClassN=endUnproc;
}

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/request JDBCRealm.java SimpleRealm.java

2000-11-01 Thread nacho

nacho   00/11/01 16:38:03

  Modified:src/share/org/apache/tomcat/request JDBCRealm.java
SimpleRealm.java
  Log:
  Adjusting Realms to the new startup order
  
  Revision  ChangesPath
  1.23  +22 -20
jakarta-tomcat/src/share/org/apache/tomcat/request/JDBCRealm.java
  
  Index: JDBCRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/request/JDBCRealm.java,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- JDBCRealm.java2000/10/23 15:17:57 1.22
  +++ JDBCRealm.java2000/11/02 00:38:02 1.23
  @@ -1,7 +1,7 @@
  -/* 
  - * $Header: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/request/JDBCRealm.java,v 1.22 
2000/10/23 15:17:57 nacho Exp $
  - * $Revision: 1.22 $
  - * $Date: 2000/10/23 15:17:57 $
  +/*
  + * $Header: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/request/JDBCRealm.java,v 1.23 
2000/11/02 00:38:02 nacho Exp $
  + * $Revision: 1.23 $
  + * $Date: 2000/11/02 00:38:02 $
*
* The Apache Software License, Version 1.1
*
  @@ -473,6 +473,7 @@
// Validate and update our current component state
 if (!started) {
 started = true;
  +  // set-up a per/container note for maps
 try {
   Class.forName(driverName);
   if ((connectionName == null || connectionName.equals("")) &&
  @@ -508,22 +509,6 @@
 }
   }
   
  -public void setContextManager( ContextManager cm ) {
  -  super.setContextManager( cm );
  -
  -  this.cm=cm;
  -  // set-up a per/container note for maps
  -  try {
  -  // XXX make the name a "global" static - after everything is stable!
  -  reqRolesNote = cm.getNoteId( ContextManager.REQUEST_NOTE
  -, "required.roles");
  -  reqRealmSignNote = cm.getNoteId( ContextManager.REQUEST_NOTE
  -, "realm.sign");
  -  } catch( TomcatException ex ) {
  -  log("setting up note for " + cm, ex);
  -  throw new RuntimeException( "Invalid state ");
  -  }
  -}
   
   public int authenticate( Request req, Response response ) {
   // Extract the credentials
  @@ -623,6 +608,23 @@
   }
   }
   
  +}
  +
  +/** Called when the ContextManger is started
  + */
  +public void engineInit(ContextManager cm) throws TomcatException {
  +//TODO:  Override this org.apache.tomcat.core.BaseInterceptor method
  +super.engineInit(cm);
  +try {
  +  // XXX make the name a "global" static - after everything is stable!
  +  reqRolesNote = cm.getNoteId( ContextManager.REQUEST_NOTE
  +, "required.roles");
  +  reqRealmSignNote = cm.getNoteId( ContextManager.REQUEST_NOTE
  +, "realm.sign");
  +} catch( TomcatException ex ) {
  +  log("setting up note for " + cm, ex);
  +  throw new RuntimeException( "Invalid state ");
  +}
   }
   
   
  
  
  
  1.11  +36 -39
jakarta-tomcat/src/share/org/apache/tomcat/request/SimpleRealm.java
  
  Index: SimpleRealm.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/request/SimpleRealm.java,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- SimpleRealm.java  2000/10/23 15:17:57 1.10
  +++ SimpleRealm.java  2000/11/02 00:38:02 1.11
  @@ -90,27 +90,7 @@
   public SimpleRealm() {
   }
   
  -/** Set the context manager. To keep it simple we don't support
  - *  dynamic add/remove for this interceptor.
  - */
  -public void setContextManager( ContextManager cm ) {
  - super.setContextManager( cm );
  -
  - this.cm=cm;
  - // set-up a per/container note for maps
  - try {
  - // XXX make the name a "global" static -
  - reqRolesNote = cm.getNoteId( ContextManager.REQUEST_NOTE,
  -  "required.roles");
  -reqRealmSignNote = cm.getNoteId( ContextManager.REQUEST_NOTE
  -   , "realm.sign");
  - } catch( TomcatException ex ) {
  - log("getting note for " + cm, ex);
  - throw new RuntimeException( "Invalid state ");
  - }
  -}
  -
  -public void contextInit( Context ctx)
  +public void contextInit(Context ctx)
throws TomcatException
   {
if( memoryRealm==null) {
  @@ -148,16 +128,16 @@
   
   public int authorize( Request req, Response response, String roles[] )
   {
  - if( roles==null || roles.length==0 ) {
  - // request doesn't need authentication
  - return 0;
  - }
  +if( roles==null || roles.length==0 ) {
  +// request doesn't need authentication
  +return 0;
  

Re: Can market-first/measure-later sustain TC growth?

2000-11-01 Thread Jason Brittain


Hi again Roy.

Roy Wilson wrote:
> 
> Jason,
> 
> A matter of small importance, and of philosophy, but ...
> 
> 
> 
> > The great thing about this is that
> > it gets some people jazzed about the project without making any
> > real, solid claims.
> 
> I think I'm ok on this.
> 
> > And, about the sentence that says "performs well under heavy
> > load, even compared to the native Apache web server"..  This
> > works the same way, since we're not saying which web server,
> > nor running on which operating system, nor under what conditions.
> > We're not even saying a major version number.  So why is it in
> > here?  Because, I heard through the grapevine that someone ran
> > some meaningful (but not necessarily bullet-proof) performance
> > tests and had this finding: that the version of Catalina that
> > was tested at the time performed about as well on most tests
> > as the version of their native Apache web server did on the same
> > tests.
> 
> But what if there happens to also be in the gv a story about someone who
> has run some meaningful performance tests and found the contrary? To mix
> metaphors, the can-o-worms that you don't want to open gets opened
> anyway, does it not?

So if someone else wants to dispute this claim, they'll first run
into the fact that we're not making any exact claims in the FAB,
only relative statements.  Then, if they want to try to make some
kind of exact claim that Catalina's web server doesn't perform well
in comparison to some version (that they choose) of the Apache web
server, then they'll first need to run some meaningful benchmarks
and publicly post the results.  Most people know that benchmarks
are often misleading, and are often swayed in favor of whoever runs
the benchmark.  So, that would only cause more talk about how the
benchmark should have been tuned, or which tests really should have
been run, etc..  And, I think that's all good because the result
is that more people are thinking and talking about Catalina.  :)
We learn more about how to tune it, how to test it, etc, all in
comparison to the native Apache web server.

The end result of it all is that it is our word against theirs,
and people will believe what they want to believe and what they
can prove on their own machine.  That's about it.
 
> > I personally don't want to spend time validating that,
> > nor would I want to be the one to try to defend the results
> > (it would likely turn into another "Java's not as fast as C"
> > arguement).
> 
> I agree with this, sort of.
> 
> > But, I believe it's possible, and I also believe
> > that Catalina's web server performs quite nicely.
> 
> I am too am inclined to think that Catalina's webserver will perform well
> enough to satisfy someone somewhere, but aren't you claiming more?

This is one thing I find awkward about marketing-speak: it sure
seems like it makes wild, solid claims, but in reality it doesn't.

> > Everyone should keep in mind that the purpose of our FAB is not
> > to prove any performance numbers or to help engineers to
> > understand Catalina's deep implementation details.  It's to make
> > some not-so-technically-saavy readers want to help the project,
> > promote the project, hire people to get it running and use it,
> > etc.  We were primarily thinking of people like:
> 
> >  - CEOs, CTOs, and other management personnel
> >  - Venture Capitalists
> >  - Marketing staff
> >  - [insert random Joe "Non-Technical" Businessman here]
> 
> I agree with the language used for the target audience, but see below.
> 
> > Reallly, people who don't know much about why their company
> > should be interested in this thing called Catalina who aren't
> > technically saavy enough to understand other docs that they
> > can find about it (like the User docs, or other technical docs
> > like the Classloader explanation doc or even the status doc..)
> > How else can we each get permission to work full-time on cool
> > projects like Catalina?  The better Catalina looks to both the
> > technical and non-technical population at large, the more support
> > the project will get overall, I think.
> 
> I think that the marketing-speak can't be broadcast until there is
> technical data to support it in some fashion. Otherwise, perhaps, some
> CEO/CTO/etc., asks a question that ultimately gets answered by a
> technically savvy person such as yourself who (in the absence of
> technical performance docs) might then be forced to reply "there's no
> !#%?! evidence!"

So then the Boss's next reply would be "Well then benchmark it and
have the results ready by friday.", and that means they'll download
it, install it, figure out some way of benchmarking it, and compare
with Apache.  If they get bad numbers, then they'll probably think
that we know something they don't.  And, we just might.

Also, having no "solid" numbers to back up a claim that's actually
a relative statement won't necessarily mean that we're just plain
wrong.

Besides, I think those who benchmark will 

Can market-first/measure-later sustain TC growth?

2000-11-01 Thread Roy Wilson

Jason,

A matter of small importance, and of philosophy, but ...




> The great thing about this is that
> it gets some people jazzed about the project without making any
> real, solid claims.

I think I'm ok on this.

> And, about the sentence that says "performs well under heavy
> load, even compared to the native Apache web server"..  This
> works the same way, since we're not saying which web server,
> nor running on which operating system, nor under what conditions.
> We're not even saying a major version number.  So why is it in
> here?  Because, I heard through the grapevine that someone ran
> some meaningful (but not necessarily bullet-proof) performance
> tests and had this finding: that the version of Catalina that
> was tested at the time performed about as well on most tests
> as the version of their native Apache web server did on the same
> tests.

But what if there happens to also be in the gv a story about someone who 
has run some meaningful performance tests and found the contrary? To mix 
metaphors, the can-o-worms that you don't want to open gets opened 
anyway, does it not?  

> I personally don't want to spend time validating that,
> nor would I want to be the one to try to defend the results
> (it would likely turn into another "Java's not as fast as C"
> arguement).  

I agree with this, sort of.

> But, I believe it's possible, and I also believe
> that Catalina's web server performs quite nicely.

I am too am inclined to think that Catalina's webserver will perform well 
enough to satisfy someone somewhere, but aren't you claiming more?  

> Everyone should keep in mind that the purpose of our FAB is not
> to prove any performance numbers or to help engineers to
> understand Catalina's deep implementation details.  It's to make
> some not-so-technically-saavy readers want to help the project,
> promote the project, hire people to get it running and use it,
> etc.  We were primarily thinking of people like:

>  - CEOs, CTOs, and other management personnel
>  - Venture Capitalists
>  - Marketing staff
>  - [insert random Joe "Non-Technical" Businessman here]

I agree with the language used for the target audience, but see below.

> Reallly, people who don't know much about why their company
> should be interested in this thing called Catalina who aren't
> technically saavy enough to understand other docs that they
> can find about it (like the User docs, or other technical docs
> like the Classloader explanation doc or even the status doc..)
> How else can we each get permission to work full-time on cool
> projects like Catalina?  The better Catalina looks to both the
> technical and non-technical population at large, the more support
> the project will get overall, I think.

I think that the marketing-speak can't be broadcast until there is 
technical data to support it in some fashion. Otherwise, perhaps, some 
CEO/CTO/etc., asks a question that ultimately gets answered by a 
technically savvy person such as yourself who (in the absence of 
technical performance docs) might then be forced to reply "there's no 
!#%?! evidence!" 

I don't see how a market-first/measure-later approach can sustain growth 
in Tomcat support. But, then, maybe you guys are simply getting the 
market-speak in place :-).

Roy

-- 
Roy Wilson
E-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/session StandardSessionInterceptor.java

2000-11-01 Thread costin

costin  00/11/01 15:36:16

  Modified:src/share/org/apache/tomcat/session
StandardSessionInterceptor.java
  Log:
  Added "randomClass" property.
  
  This config option is used by the session interceptor to generate session id.
  Instead of using a system property or a context manager option it's better
  to be able to configure the session interceptor directly ( we may want to use
  different random sources for different webapps )
  
  Revision  ChangesPath
  1.14  +7 -1  
jakarta-tomcat/src/share/org/apache/tomcat/session/StandardSessionInterceptor.java
  
  Index: StandardSessionInterceptor.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/session/StandardSessionInterceptor.java,v
  retrieving revision 1.13
  retrieving revision 1.14
  diff -u -r1.13 -r1.14
  --- StandardSessionInterceptor.java   2000/09/25 07:21:28 1.13
  +++ StandardSessionInterceptor.java   2000/11/01 23:36:16 1.14
  @@ -89,6 +89,7 @@
   
   int checkInterval = 60;
   int maxActiveSessions = -1;
  +String randomClass=null;
   
   public StandardSessionInterceptor() {
   }
  @@ -107,7 +108,12 @@
   public void setMaxActiveSessions( int count ) {
maxActiveSessions=count;
   }
  -
  +
  +public final void setRandomClass(String randomClass) {
  + this.randomClass=randomClass;
  + System.setProperty(ContextManager.RANDOM_CLASS_PROPERTY, randomClass);
  +}
  +
   
   //  Tomcat request events 
   public void engineInit( ContextManager cm ) throws TomcatException {
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Tomcat 4.0 FAB

2000-11-01 Thread Jason Brittain


Hi Roy.

Roy Wilson wrote:
> 
> Jason,
> 
> I am a geek aspiring to be a Catalina-performance-geek, but I know I
> appreciated your marketing-speak more than I'm supposed to. :-)

:)  We're glad you liked it.

> You mention that the built-in webserver performs well under heavy load. I
> don't doubt it, but would like to know the data source (ApacheCon
> Europe?) and see numbers. In particular, how was the load generated?
> ApacheBench?
> 
> Roy Wilson
> E-mail: [EMAIL PROTECTED]

Here's the paragraph from our Features and Benefits doc that you're
referring to:

snip--snip--

Built-in Multiplatform High Performance Web Server

Along with great servlet container features, Catalina comes with its
own high performance HTTP 1.1 web server built in. This new web server,
written entirely in Java, makes it easy to try Catalina without
having to configure a third-party web server. Users can thus deploy
Catalina as a functionally complete application server solution
(excluding database server) without a serious performance
penalty. The built-in web server performs well under heavy load,
even compared to the native Apache web server. And because Catalina
is written completely in Java, it's fully multiplatform, running
on Linux, Windows, Solaris or any other operating system that supports
the Java 2 Platform.

snip--snip--

Now, keep in mind that one property of marketing-speak is that
everything is relative, and that phrases that sound like exact
claims are nothing of the kind.  :)  "high performance" is a
relative term, just as "performs well under heavy load" is,
since the text makes no claims about what "high" or "well" or
"heavy" really means.  The reason why I think this kind of text
works so well on some folks is that they make the assumption
that "high" means what they (the reader) thinks it means, and
that the writer is making a claim about that kind of performance.
In reality, this text doesn't mean much, except that it means
to boast about Catalina.  :)  The great thing about this is that
it gets some people jazzed about the project without making any
real, solid claims.

And, about the sentence that says "performs well under heavy
load, even compared to the native Apache web server"..  This
works the same way, since we're not saying which web server,
nor running on which operating system, nor under what conditions.
We're not even saying a major version number.  So why is it in
here?  Because, I heard through the grapevine that someone ran
some meaningful (but not necessarily bullet-proof) performance
tests and had this finding: that the version of Catalina that
was tested at the time performed about as well on most tests
as the version of their native Apache web server did on the same
tests.  I personally don't want to spend time validating that,
nor would I want to be the one to try to defend the results
(it would likely turn into another "Java's not as fast as C"
arguement).  But, I believe it's possible, and I also believe
that Catalina's web server performs quite nicely.

Everyone should keep in mind that the purpose of our FAB is not
to prove any performance numbers or to help engineers to
understand Catalina's deep implementation details.  It's to make
some not-so-technically-saavy readers want to help the project,
promote the project, hire people to get it running and use it,
etc.  We were primarily thinking of people like:

 - CEOs, CTOs, and other management personnel
 - Venture Capitalists
 - Marketing staff
 - [insert random Joe "Non-Technical" Businessman here]

Reallly, people who don't know much about why their company
should be interested in this thing called Catalina who aren't
technically saavy enough to understand other docs that they
can find about it (like the User docs, or other technical docs
like the Classloader explanation doc or even the status doc..)
How else can we each get permission to work full-time on cool
projects like Catalina?  The better Catalina looks to both the
technical and non-technical population at large, the more support
the project will get overall, I think.

--
Jason Brittain  (415)354-6645
Software Engineer, Olliance Inc.http://www.Olliance.com
Current Maintainer, Locomotive Project  http://www.Locomotive.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/xml XmlMapper.java

2000-11-01 Thread craigmcc

craigmcc00/11/01 15:20:40

  Modified:catalina/src/share/org/apache/catalina/util/xml
XmlMapper.java
  Log:
  Suppress a couple of System.out.println() messages unless debugging detail
  is turned on.
  
  Revision  ChangesPath
  1.4   +6 -4  
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/xml/XmlMapper.java
  
  Index: XmlMapper.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/util/xml/XmlMapper.java,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- XmlMapper.java2000/10/03 18:57:45 1.3
  +++ XmlMapper.java2000/11/01 23:20:39 1.4
  @@ -456,8 +456,9 @@
  String publicId,
  String systemId)
   {
  - System.out.println("Notation: " + name + " " + publicId +
  -" " + systemId);
  +if (debug >= 1)
  +System.out.println("Notation: " + name + " " + publicId +
  +   " " + systemId);
   }
   
   public  void unparsedEntityDecl (String name,
  @@ -465,8 +466,9 @@
 String systemId,
 String notationName)
   {
  - System.out.println("Unparsed: " + name + " " + publicId +
  -" " + systemId + " " + notationName);
  +if (debug >= 1)
  +System.out.println("Unparsed: " + name + " " + publicId +
  +   " " + systemId + " " + notationName);
   }
   
   
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Builds/Releases

2000-11-01 Thread cmanolache

Mark Porter wrote:

> Why are the nightly builds broken (still!) and why is no-one answering
> questions about builds/releases?!?

Probably because there is so little free time... It's a volunteer project
-
if you have a nightly build system that works and you have the time to
maintain it - I guess everyone would be happy.

( same thing happened with the bug tracking system !)

Costin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Tomcat 3.3dev status

2000-11-01 Thread cmanolache

Glenn Nielsen wrote:

> I was wondering what the current status of the 3.3dev branch of Tomcat
> is.  I know Costin was doing a flurry of factoring changes and optimizations
> to the core Tomcat classes.  Has this work been completed?  Is 3.3dev
> ready for further testing and enhancements?

I was in a ( sort of ) vacation for last 2 weeks, and this month I have
some impossible deadlines ( again ), but I think we are close to
finishing with the core.

Right now I'm trying to split the code I did in the last 2 weeks so
I'll not check in ( again ) one big  commit.

The most important factor in finishing 3.3 is getting feedback on
the core - I added a lot of comments about various states of
ContextManager and Context ( based on how code works today
or how it was supposed to work ),  but it's important to get
more opinions.

I am hoping that after 3.3 the core will be frozen and we'll start
to maintain backward compatibility.  The core is small and simple
enough to achieve that, and I think we need to focus on modules
for the next releases. There are many modules that are waiting
to be written - starting with Servlet2.3 facades, and many more.

I'm also going to propose a new configuration mechanism,
some changes in the workdir handling ( i.e. add an option to
allow it to keep all files related with a web app in the same
directory ), etc.

Costin

( in other words - after 3.3 is final I'm not going to touch
tomcat.core anymore and I'll work only on modules and
mod_jk/JNI )




Costin


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




ContextManager loads incorrectly

2000-11-01 Thread Mark Lewis

I'm not a regular contributor to the devel mailing list, but I tracked
down a problem I've experienced to a quirk (bug?) in the Tomcat 3.2beta6
source code and I thought I would post it here so that the powers that
be can decide whether the code needs to be patched or not.

When loading the ContextManager configuration from the server.xml file,
the work directory may not be correctly loaded.  When the ContextManager
tag has the attributes in this order:



The XmlMapper calls ContextManager.setWorkDir() and then
ContextManager.setHome().  The problem is, workDir is supposed to be
based on the 'home' attribute.  Since the setWorkDir() method sets the
workDir as 'home' + param, if setHome() hasn't been called yet the work
directory will not reflect the home attribute.

Note that if you specify the attributes in the opposite order, the
functions are called in the correct order and everybody is happy.

The fix could be either:

1) Store the work dir specified in the config file in ContextManager,
and recalculate the workDir attribute any time home is set.

2) Recalculate workDir everytime you call getWorkDir()(I believe
this is what Tomcat 3.1 did, so it behaved correctly)

3) Specify that you need to put the "home" attribute first in the
ContextManager XML tag.

Hopefully this is useful, and I wasn't wasting your guys' time. :)

Mark Lewis
[EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Tomcat 3.3dev status

2000-11-01 Thread Glenn Nielsen

I was wondering what the current status of the 3.3dev branch of Tomcat
is.  I know Costin was doing a flurry of factoring changes and optimizations
to the core Tomcat classes.  Has this work been completed?  Is 3.3dev
ready for further testing and enhancements?
  
Glenn

--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: Tomcat 4.0 FAB

2000-11-01 Thread Roy Wilson

Jason,

I am a geek aspiring to be a Catalina-performance-geek, but I know I 
appreciated your marketing-speak more than I'm supposed to. :-) 

You mention that the built-in webserver performs well under heavy load. I 
don't doubt it, but would like to know the data source (ApacheCon 
Europe?) and see numbers. In particular, how was the load generated? 
ApacheBench?

Roy Wilson
E-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util MessageBytes.java MimeHeaders.java MimeMap.java SessionIdGenerator.java

2000-11-01 Thread costin

costin  00/11/01 13:43:29

  Modified:src/share/org/apache/tomcat/util MessageBytes.java
MimeHeaders.java MimeMap.java
SessionIdGenerator.java
  Log:
  - added indexOf( c, starting ) to MessageBytes
  
  - in SessionIdGenerator, allow the caller to pass a Random source.
  That will allow to configure the SessionInterceptor to use a certain
  random instead of making config decisions at tomcat.util level.
  
  Revision  ChangesPath
  1.12  +8 -4  
jakarta-tomcat/src/share/org/apache/tomcat/util/MessageBytes.java
  
  Index: MessageBytes.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/MessageBytes.java,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- MessageBytes.java 2000/10/08 21:28:59 1.11
  +++ MessageBytes.java 2000/11/01 21:43:28 1.12
  @@ -643,27 +643,31 @@
return code;
   }
   
  +public int indexOf(char c) {
  + return indexOf( c, 0);
  +}
  +
   /**
* Returns true if the message bytes starts with the specified string.
* @param s the string
*/
  -public int indexOf(char c) {
  +public int indexOf(char c, int starting) {
switch (type) {
case T_INT:
case T_DATE:
String s1=toString();
// continue with T_STR - it now have a strValue
case T_STR:
  - return strValue.indexOf( c );
  + return strValue.indexOf( c, starting );
case T_CHARS:
  - for (int i = charsOff; i < charsOff + charsLen; i++) {
  + for (int i = charsOff+starting; i < charsOff + charsLen; i++) {
if( c == chars[i] ) return i;
}
return -1;
case T_BYTES:
int max=bytesOff+bytesLen;
byte bb[]=bytes;
  - for (int i = bytesOff; i < max ; i++) {
  + for (int i = bytesOff+starting; i < max ; i++) {
if( (byte)c == bb[i]) return i;
}
return -1;
  
  
  
  1.16  +0 -3  jakarta-tomcat/src/share/org/apache/tomcat/util/MimeHeaders.java
  
  Index: MimeHeaders.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/MimeHeaders.java,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- MimeHeaders.java  2000/09/22 20:31:43 1.15
  +++ MimeHeaders.java  2000/11/01 21:43:28 1.16
  @@ -1,7 +1,4 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/MimeHeaders.java,v 1.15 
2000/09/22 20:31:43 nacho Exp $
  - * $Revision: 1.15 $
  - * $Date: 2000/09/22 20:31:43 $
* 
*
* The Apache Software License, Version 1.1
  
  
  
  1.6   +0 -4  jakarta-tomcat/src/share/org/apache/tomcat/util/MimeMap.java
  
  Index: MimeMap.java
  ===
  RCS file: /home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/MimeMap.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- MimeMap.java  2000/06/10 17:54:29 1.5
  +++ MimeMap.java  2000/11/01 21:43:28 1.6
  @@ -1,8 +1,4 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/MimeMap.java,v 1.5 
2000/06/10 17:54:29 costin Exp $
  - * $Revision: 1.5 $
  - * $Date: 2000/06/10 17:54:29 $
  - *
* 
*
* The Apache Software License, Version 1.1
  
  
  
  1.5   +24 -10
jakarta-tomcat/src/share/org/apache/tomcat/util/SessionIdGenerator.java
  
  Index: SessionIdGenerator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/SessionIdGenerator.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- SessionIdGenerator.java   2000/08/23 20:21:49 1.4
  +++ SessionIdGenerator.java   2000/11/01 21:43:28 1.5
  @@ -1,8 +1,4 @@
   /*
  - * $Header: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/SessionIdGenerator.java,v 
1.4 2000/08/23 20:21:49 jiricka Exp $
  - * $Revision: 1.4 $
  - * $Date: 2000/08/23 20:21:49 $
  - *
* 
*
* The Apache Software License, Version 1.1
  @@ -64,6 +60,8 @@
   
   package org.apache.tomcat.util;
   
  +import java.util.Random;
  +
   /**
* This class generates a unique 10+ character id. This is good
* for authenticating users or tracking users around.
  @@ -89,7 +87,7 @@
*/
   static private int session_count = 0;
   static private long lastTimeVal = 0;
  -static private java.util.Random randomSource;
  +st

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/xml SaxContext.java XmlMapper.java

2000-11-01 Thread costin

costin  00/11/01 13:39:38

  Modified:src/share/org/apache/tomcat/util/xml SaxContext.java
XmlMapper.java
  Log:
  Added few more helper methods to the xml mapper.
  - you can define "variables" ( a global Hashtable ) ( that will
   eliminate the need for intermediary objects )
  - shortcuts for common accesses to current and previous object
  
  Revision  ChangesPath
  1.2   +38 -7 
jakarta-tomcat/src/share/org/apache/tomcat/util/xml/SaxContext.java
  
  Index: SaxContext.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/xml/SaxContext.java,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- SaxContext.java   2000/02/08 20:13:32 1.1
  +++ SaxContext.java   2000/11/01 21:39:35 1.2
  @@ -16,32 +16,55 @@
   // XXX this interface is not final, but a prototype.
   
   /** SAX Context - used to match and perform actions 
  - *provide access to the current stack and XML elements.
  + *  provide access to the current stack and XML elements.
  + * 
  + *  We maintain a stack with all elements and their attributes.
  + *  We also support a stack of objects that can be used as in a
  + *  stack-based programming language.
*
* @author [EMAIL PROTECTED]
*/
   public interface SaxContext  {
   
  -//  Access to parsing context
  +//  Access to the element stack
   
  +/** Body of the last tag.
  + */
  +public String getBody();
  +
  +/** Attributes of the current tag
  + */
  +public AttributeList getCurrentAttributes();
  +
  +/** Current element
  + */
  +public String getCurrentElement();
  +
  +
   /** Depth of the tag stack.
  + *  XXX getElementDepth() ?
*/
   public int getTagCount();
   
  -/** Access attributes of a particular tag
  +/** Random access to attributes of a particular element.
*/
   public AttributeList getAttributeList( int pos );
   
  -/** Access a particular tag
  +/** Random Access a particular parent element
  + *  XXX getElement() is a better name
*/
   public String getTag( int pos );
   
  -/** Body of the last tag
  - */
  -public String getBody();
   
  +
   //  Object stack
   
  +public void pushObject(Object o);
  +public Object popObject();
  +
  +public Object currentObject();
  +public Object previousObject();
  +
   /**
  The root object is either set by caller before starting the parse
  or can be created using the first tag. It is used to set object in
  @@ -54,6 +77,7 @@
as result of parsing. You can either use the stack ( which is
very powerfull construct !), or use the root object
and navigation in the result tree.
  + @deprecated
   */
   public Stack getObjectStack();
   
  @@ -62,4 +86,11 @@
   public int getDebug();
   
   public void log( String s );
  +
  +public XmlMapper getMapper();
  +
  +//  Variables  
  +public void setVariable( String s, Object v );
  +
  +public Object getVariable( String s );
   }
  
  
  
  1.28  +142 -68   
jakarta-tomcat/src/share/org/apache/tomcat/util/xml/XmlMapper.java
  
  Index: XmlMapper.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat/src/share/org/apache/tomcat/util/xml/XmlMapper.java,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- XmlMapper.java2000/08/10 22:39:24 1.27
  +++ XmlMapper.java2000/11/01 21:39:35 1.28
  @@ -32,7 +32,8 @@
*/
   private Hashtable fileDTDs = new Hashtable();
   private Hashtable resDTDs = new Hashtable();
  -
  +private Hashtable variables = new Hashtable();
  +
   // Stack of elements
   Stack oStack=new Stack();
   Object root;
  @@ -144,6 +145,10 @@
return (AttributeList)attributeStack[pos];
   }
   
  +public AttributeList getCurrentAttributes() {
  + return (AttributeList)attributeStack[sp-1];
  +}
  +
   public int getTagCount() {
return sp;
   }
  @@ -152,6 +157,10 @@
return tagStack[pos];
   }
   
  +public String getCurrentElement() {
  + return tagStack[sp-1];
  +}
  +
   public String getBody() {
return body;
   }
  @@ -160,6 +169,25 @@
return oStack;
   }
   
  +public Object popObject() {
  + return oStack.pop();
  +}
  +
  +public Object currentObject() {
  + return oStack.peek();
  +}
  +
  +public Object previousObject() {
  + Object o=oStack.pop();
  + Object result=oStack.peek();
  + oStack.push( o );
  + return result;
  +}
  +
  +public void pushObject(Object o) {
  + oStack.

RE: missing page

2000-11-01 Thread Michael Percy

Try here:
http://jakarta.apache.org/builds/tomcat/release/v3.2-beta-6/bin/win32/i386/

> -Original Message-
> From: Alan Dix [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 01, 2000 12:26 PM
> To: '[EMAIL PROTECTED]'
> Subject: missing page
> 
> 
> On the web page
> http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/in-pro
> cess-howto.htm
> l
> 
> there is a reference to the files required for an in-process 
> operation:
> 
> "The in-process adapter is not part of the "official" build 
> of Jakarta, You
> can obtain the code and binaries needed for it by accessing
>
http://jakarta.apache.org/builds/tomcat/release/v3.1_beta_1/bin/win32/i386/.
> The adapter related file is jni_connect.dll."
> However, the link does not go anywhere.
> 
> Can you tell me where to find the required files (jni_connect.dll) ?
> Thanks,
> Alan Dix

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #328 has been filed.

2000-11-01 Thread BugRat Mail System

Bug report #328 has just been filed.

You can view the report at the following URL:

   

REPORT #328 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: 3.2b6
   JVM Release: -
   Operating System: -
   OS Release: -
   Platform: -

Synopsis: 
session ID does not encode worker name in URL

Description:
When working with mod_jk/mod_jserv and storing the session ID on the URL (i.e. not 
with cookies), the URL rewriting does not have access to jvmRoute and therefore the 
rewritten URL is not written correctly (i.e. does not contain the jvmRoute as does the 
cookie).



Title: 
BugRat Report #
328





BugRat Report #
328




Project:
Tomcat


Release:
3.2b6




Category:
Bug Report


SubCategory:
New Bug Report




Class:
swbug


State:
received




Priority:
high


Severity:
critical




Confidence:
public





Submitter:
Shai Fultheim ( [EMAIL PROTECTED] )

Date Submitted:
Nov 1 2000, 03:11:22 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

session ID does not encode worker name in URL


 Environment: (jvm, os, osrel, platform)

-, -, -, -



Additional Environment Description:





Report Description:

When working with mod_jk/mod_jserv and storing the session ID on the URL (i.e. not with cookies), the URL rewriting does not have access to jvmRoute and therefore the rewritten URL is not written correctly (i.e. does not contain the jvmRoute as does the cookie).





View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


missing page

2000-11-01 Thread Alan Dix

On the web page
http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/in-process-howto.htm
l

there is a reference to the files required for an in-process operation:

"The in-process adapter is not part of the "official" build of Jakarta, You
can obtain the code and binaries needed for it by accessing
http://jakarta.apache.org/builds/tomcat/release/v3.1_beta_1/bin/win32/i386/.
The adapter related file is jni_connect.dll."
However, the link does not go anywhere.

Can you tell me where to find the required files (jni_connect.dll) ?
Thanks,
Alan Dix

***
 Alan Dix, Development Engineer
 Gearworks, Inc.

3800 West 80th Street  - Suite 900
Minneapolis, MN  55431
612.857.2512
fax: 507.645.2763 

  REVOLUTIONARY WEB AND WIRELESS SOLUTIONS  
http://www.gearworks.comhttp://unwired.gearworks.com
***
"Nothing is fool-proof to a sufficiently talented fool."





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #271 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #271 was closed by Person #0

   Synopsis: POST variables unavailable when posted from a Phone.com WAP phone

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #274 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #274 was closed by Person #0

   Synopsis: Catalina: Null pointer exception in FormAuthenticator

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




cvs commit: jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler TagBeginGenerator.java TagEndGenerator.java TagGeneratorBase.java TagLibraryInfoImpl.java

2000-11-01 Thread pierred

pierred 00/11/01 12:25:52

  Modified:jasper/src/share/org/apache/jasper/compiler
TagBeginGenerator.java TagEndGenerator.java
TagGeneratorBase.java TagLibraryInfoImpl.java
  Log:
  Part 2 for the support of the following new JSP 1.2 feature:
  "Added elements to the TLD to avoid having to write TagExtraInfo
  classes in the most common cases"
  
  TagLibraryInfoImpl.java
  - proper handling of  element
  
  TagGeneratorBase.java
  TagBeginGenerator.java
  TagEndGenerator.java
  - Now supports TagVariableInfo as well as VariableInfo
  
  Revision  ChangesPath
  1.6   +9 -5  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagBeginGenerator.java
  
  Index: TagBeginGenerator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagBeginGenerator.java,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- TagBeginGenerator.java2000/10/17 22:59:01 1.5
  +++ TagBeginGenerator.java2000/11/01 20:25:07 1.6
  @@ -64,6 +64,7 @@
   import javax.servlet.jsp.tagext.TagInfo;
   import javax.servlet.jsp.tagext.TagAttributeInfo;
   import javax.servlet.jsp.tagext.VariableInfo;
  +import javax.servlet.jsp.tagext.TagVariableInfo;
   import javax.servlet.jsp.tagext.TagData;
   import javax.servlet.jsp.tagext.Tag;
   import javax.servlet.jsp.tagext.BodyTag;
  @@ -318,9 +319,10 @@
   generateSetters(writer, parent);
   
   VariableInfo[] vi = ti.getVariableInfo(tagData);
  + TagVariableInfo[] tvi = ti.getTagVariableInfos();
   
   // Just declare AT_BEGIN here...
  -declareVariables(writer, vi, true, false, VariableInfo.AT_BEGIN);
  +declareVariables(writer, vi, tvi, tagData, true, false, 
VariableInfo.AT_BEGIN);
   
writer.println("try {");
writer.pushIndent();
  @@ -330,10 +332,11 @@
   writer.println("int "+evalVar+" = "
  +thVarName+".doStartTag();");
   
  -boolean implementsBodyTag = 
BodyTag.class.isAssignableFrom(tc.getTagHandlerClass());
  +boolean implementsBodyTag = 
  + BodyTag.class.isAssignableFrom(tc.getTagHandlerClass());
   
   // Need to update AT_BEGIN variables here
  -declareVariables(writer, vi, false, true, VariableInfo.AT_BEGIN);
  +declareVariables(writer, vi, tvi, tagData, false, true, 
VariableInfo.AT_BEGIN);
   
   // FIXME: I'm not too sure if this is the right approach. I don't like
   //throwing English language strings into the generated servlet.
  @@ -376,9 +379,9 @@
writer.println("do {");
writer.pushIndent();
   // Need to declare and update NESTED variables here
  -declareVariables(writer, vi, true, true, VariableInfo.NESTED);
  +declareVariables(writer, vi, tvi, tagData, true, true, VariableInfo.NESTED);
   // Need to update AT_BEGIN variables here
  -declareVariables(writer, vi, false, true, VariableInfo.AT_BEGIN);
  +declareVariables(writer, vi, tvi, tagData, false, true, 
VariableInfo.AT_BEGIN);
   }
   
   public void generate(ServletWriter writer, Class phase)
  @@ -387,3 +390,4 @@
   generateServiceMethodStatements(writer);
   }
   }
  +
  
  
  
  1.5   +7 -4  
jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagEndGenerator.java
  
  Index: TagEndGenerator.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/jasper/src/share/org/apache/jasper/compiler/TagEndGenerator.java,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- TagEndGenerator.java  2000/11/01 00:53:59 1.4
  +++ TagEndGenerator.java  2000/11/01 20:25:08 1.5
  @@ -61,6 +61,7 @@
   import javax.servlet.jsp.tagext.TagLibraryInfo;
   import javax.servlet.jsp.tagext.TagInfo;
   import javax.servlet.jsp.tagext.VariableInfo;
  +import javax.servlet.jsp.tagext.TagVariableInfo;
   import javax.servlet.jsp.tagext.TagData;
   import javax.servlet.jsp.tagext.Tag;
   import javax.servlet.jsp.tagext.IterationTag;
  @@ -105,8 +106,10 @@
   String thVarName = tvd.tagHandlerInstanceName;
   String evalVarName = tvd.tagEvalVarName;
   
  -VariableInfo[] vi = ti.getVariableInfo(new TagData(
  -JspUtil.attrsToHashtable(attrs)));
  + TagData tagData = 
  + new TagData(JspUtil.attrsToHashtable(attrs));
  +VariableInfo[] vi = ti.getVariableInfo(tagData);
  + TagVariableInfo[] tvi = ti.getTagVariableInfos();
   
   Class tagHandlerClass =
libraries.getTagCache(prefix, shortTagName).getTagHandlerClass();
  @@ -124,7 +127,7 @@
   else
   writer.println("} while (false);");
   
  -declareVariables(writer, vi, false, true, VariableInfo.

Re: Tomcat 4.0 Milestone 4

2000-11-01 Thread Jason Brittain


In case you're interested, we've written a short document about
Catalina's Features And Benefits (FAB) that is more geared for
non-geeks (it's very marketingly-written :) that you may want to
include with the M4 docs.  I've attached it to this mail.  It's a
plain text version, but I'm sure it would look better as HTML.
Let us know if there's anything inaccurate about the details it
contains.  It was written by William Abernathy 
([EMAIL PROTECTED]) and myself.  Let us know what you think.

And, BTW, great work on making Catalina the first Servlet 2.3
compliant servlet container!

Cheers!

--
Jason Brittain
Software Engineer, Olliance Inc.http://www.Olliance.com
Current Maintainer, Locomotive Project  http://www.Locomotive.org


"Craig R. McClanahan" wrote:
> 
> Hey folks,
> 
> I'm planning on cutting a fourth milestone of Tomcat 4.0 tomorrow
> (Wednesday) evening.  This milestone will reflect all of the changes
> that occurred in the servlet 2.3 and JSP 1.2 specifications between
> public draft and proposed final draft (and there were a *bunch* of
> them), completion of the remaining new 2.3/1.2 functionality, and
> several bug fixes.
> 
> This will be the last big push of spec-related functionality additions
> for Tomcat 4.0.  Now, we can turn our attention more towards bug fixes
> and performance tuning.  You can help in that process by downloading and
> playing with the Tomcat 4.0 milestone.  I'd like to see us shake it out
> enough to be production quality by Christmas time.
> 
> Besides bug fixing and tuning, I know of several pieces of functionality
> yet to be added that are being worked on, including:
> 
> * Web connectors (using a new connector protocol
>   called mod_warp that is aware of webapp configuration
>   settings, so you will not have to configure things twice).
> 
> * JNDI context support (like that used in J2EE servers)
>   for the  and  configuration
>   parameters in the deployment descriptor.
> 
> If you are interested in contributing to Tomcat 4.0, there is a "wish
> list" document in file "catalina/STATUS.html" in the jakarta-tomcat-4.0
> source tree.  Feel free to propose new ideas, or to volunteer to work on
> one of these.
> 
> Craig McClanahan


Features and Benefits of the Catalina Servlet Container


Introduction
 
Catalina is a new open source servlet container from the makers of
Apache JServ, engineered to be the fastest, most flexible, and most
modular servlet container available. Hosted by the Apache Software
Foundation, the Catalina server software package project is SUN
Microsystems's next-generation Java Servlet Container Reference
Implementation. This text discusses Catalina's features and benefits.


Modularly-Designed Servlet Container Core

Open source servlet containers have not, historically, been designed
to be modular. Modularity allows much of the container's core
functionalities to be changed out seamlessly when different 
implementations are required. Catalina's servlet container core was
designed to be made of modules, each of which has a well defined
interface to the other core modules. Any module may be replaced at
runtime by new implementations that still adhere to the core's
interfaces. New implementations of these core modules support custom
and/or extended features, including:

-  Direct pluggable integration with legacy systems
-  Diverse implementations of free or proprietary core components
-  Modular embedding of the Catalina servlet container into larger
   applications.


Up to Date With the Latest Java Servlet Specification

New development invariably drives new specification revisions. In
addition to its full compliance with the featureful Java Servlet 2.2
Specification, Catalina's design is pushing servlet container
functionality to new heights. Catalina's development has driven the
Java Servlet 2.3 Specification, which is written to take advantage
of new features that were first implemented as part of the Catalina
servlet container. Catalina brings the enterprise the latest and
greatest servlet functionality -- first, and for free.


Full, Integrally-Designed Virtual Hosting Support

Engineered from the outset to support a complete set of virtual
hosting features, Catalina's core enjoys distinct advantages over
servlet containers that have had to add virtual hosting. Having these
features designed into the core makes the source code easier to
understand, and makes these features easy and efficient to
use. Catalina includes support for running multiple Web Applications
per vhost. Internet providers and web hosting companies need this
hard-to-find feature to help scale their servers to meet high demand
for less cost.


Featureful and Extensible Request Processing

Catalina supports request filtering on multiple levels and better
enables the separation of server and web application
functions. This makes it much easier for an administrator to track web
application usage, track server performance, and add custom request
and response fi

BugRat Report #327 has been filed.

2000-11-01 Thread BugRat Mail System

Bug report #327 has just been filed.

You can view the report at the following URL:

   

REPORT #327 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: docbug
State: received
Priority: high
Severity: non-critical
Confidence: public
Environment: 
   Release: 3.2 Beta 6
   JVM Release: 1.2
   Operating System: linux
   OS Release: Red Hat 6.2
   Platform: intel

Synopsis: 
WebApp - Sample build broken

Description:
1. chmod +x $TOMCAT_HOME/doc/appdev/sample/build
2. ed build, /xml/s//parser # parser replaces xml ?
3. Add CP for jaxp.jar
4. Add CP for tools.jar 
Note: #4 is a repeat of bug #30 point #2 (aug 22) 

Title: 
BugRat Report #
327





BugRat Report #
327




Project:
Tomcat


Release:
3.2 Beta 6




Category:
Bug Report


SubCategory:
New Bug Report




Class:
docbug


State:
received




Priority:
high


Severity:
non-critical




Confidence:
public





Submitter:
Paul Campbell ( [EMAIL PROTECTED] )

Date Submitted:
Nov 1 2000, 02:19:05 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

WebApp - Sample build broken


 Environment: (jvm, os, osrel, platform)

1.2, linux, Red Hat 6.2, intel



Additional Environment Description:





Report Description:

1. chmod +x $TOMCAT_HOME/doc/appdev/sample/build
2. ed build, /xml/s//parser # parser replaces xml ?
3. Add CP for jaxp.jar
4. Add CP for tools.jar 
Note: #4 is a repeat of bug #30 point #2 (aug 22) 



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


BugRat Report #52 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #52 was closed by Person #0

   Synopsis: Network timeout first time accessing secure page

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #216 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #216 was closed by Person #0

   Synopsis: Parameter value does not acquired when the value is mult-byte characters 
and when used in HTML anchor tag

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




[BUG] jsp:plugin tag

2000-11-01 Thread Robert Gretta



i've noticed a html formating bug in the way jsp:plugin is interpreted and
expanded in the latest version of tomcat. 
it causes both netscape and mozillia browser to fail in parsing the html
tags... 
jsp code... 
 
 
 
 
interpretation... 
 
http://java.sun.com/products/plugin/1.2.2/jinstall-> 
1_2_2-win.cab#Version=1,2,2,0"> 
 
 
 
 
http://java.sun.com/products/plugin/> 
java_code="swingApplet.class" java_codebase="." > 
 
 
 unable to start plug-in  
 
 
 
notice the placement of the COMMENT tags releative to the NOEMBED and EMBED
tags they are not properly scoped. 
this causes the html parsing to fail for certain browsers... mozzilla. 




Robert E. Gretta, Jr.
platform developer
@hand corporation
voice: 512.231.9993fax: 512.231.9994
  |  



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #324 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #324 was closed by Person #0

   Synopsis: After init, getOutputStream fails.

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #318 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #318 was closed by Person #0

   Synopsis: doPost() not invoked just after init()

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




BugRat Report #326 has been filed.

2000-11-01 Thread BugRat Mail System

Bug report #326 has just been filed.

You can view the report at the following URL:

   

REPORT #326 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: docbug
State: received
Priority: high
Severity: cosmetic
Confidence: public
Environment: 
   Release: 3.2 Beta 6
   JVM Release: 1.2
   Operating System: linux
   OS Release: Red Hat 6.2
   Platform: Intel

Synopsis: 
Error on index.html

Description:
ERROR:
The README file, which can be 
found at /README, 

CORRECT:
The readme file, which can be 
found  at $TOMCAT_HOME/doc/readme.



 

Title: 
BugRat Report #
326





BugRat Report #
326




Project:
Tomcat


Release:
3.2 Beta 6




Category:
Bug Report


SubCategory:
New Bug Report




Class:
docbug


State:
received




Priority:
high


Severity:
cosmetic




Confidence:
public





Submitter:
Paul Campbell ( [EMAIL PROTECTED] )

Date Submitted:
Nov 1 2000, 01:09:36 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Error on index.html


 Environment: (jvm, os, osrel, platform)

1.2, linux, Red Hat 6.2, Intel



Additional Environment Description:





Report Description:

ERROR:
The README file, which can be 
found at /README, 

CORRECT:
The readme file, which can be 
found  at $TOMCAT_HOME/doc/readme.



 



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


BugRat Report #242 was closed (apparently by: Craig R. McClanahan)

2000-11-01 Thread BugRat Mail System

Report #242 was closed by Person #0

   Synopsis: Problem including HTML files with 4.0 M2

 (logged in as: Craig R. McClanahan)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: BugRat Report #323 has been filed.

2000-11-01 Thread Rick Beaubien

Please note that the problem I am reporting does not pertain to UTF-8
encoding in URLs, but to UTF-8 encoded values above the ascii range in the
CONTENT of the HTML pages prepared by my servlet.  The content of my pages
includes UTF-8 encode unicode values in the CJK range.   For example, see
the following test page delivered by my servlet under the early, correctly
functioning version of Tomcat 3.1 (I recommend using IE to view this page;
if you have Chinese font support installed you will be able to see Chinese
characters in the lefthand frames.  But even if the Chinese characters show
up as boxes for lack of the proper font, you can tell by looking at the
page source that the 3-byte UTF-8 encodings for the Chinese characters are
being delivered to the browser):

http://sunsite.berkeley.edu/xdlib/servlet/archobj?DOCCHOICE=misc/sprintatest
2.xml

Under the newest release of Tomcat 3.1, the Chinese characters in question
all get translated to question marks by Tomcat before being delivered to
the browser.

The patches that I see cited at the address provided by Kim below all seem
to pertain to UTF-8 encoding in URLs, not in page content.  Stefan van den
Oord and I are reporting problems with the handling of UTF-8 encoding in
the  of the HTML pages prepared by our servlets.

Thanks,

Rick Beaubien


At 12:31 PM 11/01/2000 +0900, you wrote:
>Please check
>
>http://www.javaclue.org/tomcat/
>
>Kim
>
>
>On Tue, 31 Oct 2000, BugRat Mail System wrote:
>
>> Bug report #323 has just been filed.
>> 
>> You can view the report at the following URL:
>> 
>>
>> 
>> REPORT #323 Details.
>> 
>> Project: Tomcat
>> Category: Bug Report
>> SubCategory: New Bug Report
>> Class: swbug
>> State: received
>> Priority: high
>> Severity: critical
>> Confidence: public
>> Environment: 
>>Release: 3.1
>>JVM Release: jdk1.2.2
>>Operating System: Solaris
>>OS Release: 2.6
>>Platform: Unix
>> 
>> Synopsis: 
>> Tomcat 3.1 mishandles UTF-8 encoded text above the ascii range
>> 
>> Description:
>> My servlet produces UTF-8 encoded HTML pages that 
>> include encoded Unicode character values in the CJK range; 
>> I set the HttpServletResponse.ContentType in these cases to
>> "text/html;charset=utf-8".  Under an early issue of 
>> Tomcat 3.1, the UTF-8 encoded CJK characters got submitted 
>> to the browser properly; IE5 with the proper fonts 
>> installed was able to display theses characters just fine.  
>> Under the newest issue of Tomcat 3.1, however, the CJK 
>> characters in the HTML pages are replaced with "?"s before 
>> they are submitted to the browser! 
>> 
>> For another report of the same problem, see 
>> Stefan van den Oord's memo to the developers list on
>> May 4, 2000:
>> 
>> http://www.metronet.com/~wjm/tomcat/FromFeb11/msg01988.html )
>> 
>> 
>
>
>-
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

-
Rick Beaubien 

Software Engineer: Research and Development
Library Systems Office
Rm 386 Doe Library
University of California
Berkeley, CA 94720-6000
510-643-9776

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Hello? Anybody?

2000-11-01 Thread Ethan Wallwork


Can someone PLEASE respond on this?  Even if only to tell me I have no idea
what I'm talking about? I really would like to find out what the proper
behaviour for Tomcat in this situation is.

Thank you,

Ethan

-Original Message-
From: Ethan Wallwork [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 30, 2000 10:31 AM
To: [EMAIL PROTECTED]
Subject: RE: BugRat Report #213 has been filed.



Has anyone looked at this?  It is a real problem for us, and if others agree it
should be changed I will get started on a fix.

--
Ethan

-Original Message-
From: BugRat Mail System [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 04, 2000 2:13 PM
To: [EMAIL PROTECTED]
Subject: BugRat Report #213 has been filed.


Bug report #213 has just been filed.

You can view the report at the following URL:

   

REPORT #213 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: medium
Severity: serious
Confidence: public
Environment:
   Release: 3.1, 3.2
   JVM Release: any
   Operating System: any
   OS Release: any
   Platform: any

Synopsis:
RequestDispatcher does not propagate errors

Description:
If a servlet uses a RequestDispatcher to forward or include a second servlet
(or JSP), and the second servlet throws and exception from it's service method,
that exception is not propagated to the first servlet.

This is a problem if you have a setup (like ours) where a single "master"
servlet includes a particular JSP depending on thing other than just the
request URI, and you want it to be able to handle the errors.  As it is, the
error gets handled by Tomcat (using default error page, or whatever error page
you've configured in the JSP or web.xml file) and the main servlet never knows
anything went wrong.

In Tomcat 3.2, the RequestDispatcher forward/include methods call the Handler
service method.  This service method never throws an exception.  In Tomcat 3.1
it calls the ServletWrapper handleRequest method, which also never throws and
exception.

The reason I think exceptions should be propagated is because of section 8.5 of
the servlet spec, which strongly implies it:

8.5 ERROR HANDLING
Only runtime exceptions and checked exceptions of type ServletException or
IOException should be propagated to the calling servlet if thrown by the target
of a request dispatcher.  All other exceptions should be wrapped as a
ServletException and the root cause of the exception set to the original
exception.




-
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: java.security.policy problems with EmbededTomcat

2000-11-01 Thread Stefán F. Stefánsson

I found out what the problem was and I want to post it here if it could
help someone else.

The bug wasn't with tomcat it was the JDK.  It wasn't finding the policy
file I specified which is very strange since I did put it in
{java_home}/jre/lib/security and I even added a line in the
java.security file specifying that the tomcat.policy file should be
used.

As soon as I typed in the full path to the file on the command line like
so:
java
-Djava.security.policy==c:/jdk1.3/jre/lib/security/tomcat.policy
NameOfClass
It started working!

So this is obviously a bug with the JDK and not Tomcat... of course...
;o)

Regards, Stefan.

-Original Message-
From: Stefán F. Stefánsson [mailto:[EMAIL PROTECTED]]
Sent: 30. október 2000 11:52
To: Tomcat-Dev
Subject: java.security.policy problems with EmbededTomcat


Hi.

I'm having HUGE problems with EmbededTomcat and the Java 2 security
manager.

I'm trying to start up Tomcat through the EmbededTomcat class and adding
one context for the root.

Here is the code I'm using:
try
{
EmbededTomcat tc=new EmbededTomcat();
tc.setWorkDir( "c:/jakarta/build/tomcat/work");
ServletContext sctx;
sctx=tc.addContext("", new java.net.URL
( "file:/C:/ips"));
tc.initContext( sctx );
tc.addEndpoint( 8080, null, null);
tc.start();

while(true)
{
Thread.sleep(100);
}
}
catch (Throwable t )
{
t.printStackTrace();
}

And here is the output I'm getting from Tomcat:
ContextManager: Adding context Ctx(  ) 
cannot process configuration web service using " /C:/ips" 
Security init for Context /C:/ips failed 
java.security.AccessControlException: access denied
(java.lang.RuntimePermission createClassLoader)
at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:272) 
at
java.security.AccessController.checkPermission(AccessController.java:399
) 
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:545) 
at
java.lang.SecurityManager.checkCreateClassLoader(SecurityManager.java:61
0) 
at java.lang.ClassLoader.(ClassLoader.java:234) 
at
org.apache.tomcat.loader.AdaptiveClassLoader.(AdaptiveClassLoader.
java:213) 
at
org.apache.tomcat.loader.AdaptiveServletLoader.(AdaptiveServletLoa
der.java:88) 
at
org.apache.tomcat.context.LoaderInterceptor.contextInit(LoaderIntercepto
r.java:93) 
at
org.apache.tomcat.core.ContextManager.initContext(ContextManager.java:48
0) 
at
org.apache.tomcat.startup.EmbededTomcat.initContext(EmbededTomcat.java:2
37) 
at TestRun.main(TestRun.java:30)
java.security.AccessControlException: access denied
(java.net.SocketPermission localhost:8080 listen,resolve) 
at
java.security.AccessControlContext.checkPermission(AccessControlContext.
java:272) 
at
java.security.AccessController.checkPermission(AccessController.java:399
) 
at
java.lang.SecurityManager.checkPermission(SecurityManager.java:545) 
at
java.lang.SecurityManager.checkListen(SecurityManager.java:1127) 
at java.net.ServerSocket.(ServerSocket.java:163) 
at java.net.ServerSocket.(ServerSocket.java:121) 
at
org.apache.tomcat.net.DefaultServerSocketFactory.createSocket(DefaultSer
verSocketFactory.java:97) 
at
org.apache.tomcat.service.PoolTcpEndpoint.startEndpoint(PoolTcpEndpoint.
java:239) 
at
org.apache.tomcat.service.PoolTcpConnector.start(PoolTcpConnector.java:1
88) 
at
org.apache.tomcat.core.ContextManager.start(ContextManager.java:516) 
at
org.apache.tomcat.startup.EmbededTomcat.start(EmbededTomcat.java:267) 
at TestRun.main(TestRun.java:32) 

The weird thing is that I'm running the java machine with the parameters
"-Djava.security.policy==tomcat.policy" where the tomcat.policy file
resides in {JAVA_HOME}\jre\lib\security and looks like this:

grant {
permission java.security.AllPermission;
};



This is really starting to get annoying and has taken up alot of time so
please help if you can.

Kind regards, Stefan Freyr


Stefan Freyr Stefansson
Software Developer
deCODE Genetics, Inc.

Phone: (+354) 570 2854
GSM:   (+354) 861 1718
Fax:   (+354) 491 3782
 <> 


 winmail.dat

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


BugRat Report #325 has been filed.

2000-11-01 Thread BugRat Mail System

Bug report #325 has just been filed.

You can view the report at the following URL:

   

REPORT #325 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: webbug
State: received
Priority: high
Severity: serious
Confidence: public
Environment: 
   Release: tomcat 3.1
   JVM Release: sun1.3.0-C
   Operating System: win98
   OS Release: fe
   Platform: win32

Synopsis: 
Apache + Tomcat bad link handling

Description:
I ran Tomcat standalone and it works fine.
On the other hand, Tomcat configured as an add-on to Apache (who serves the static 
files), with the .dll module loaded has this behaviour:

When I access /testj/hello it works fine with a test servlet.
When I acces /testj/index.html which has a link in it to /testj/hello I receive a 404 
HTTP error.

The same servlet works fine if I put it in the /examples context.

So, if it would have been me, I think it shouldn't work at all, therefor I report it 
as a bug.

Title: 
BugRat Report #
325





BugRat Report #
325




Project:
Tomcat


Release:
tomcat 3.1




Category:
Bug Report


SubCategory:
New Bug Report




Class:
webbug


State:
received




Priority:
high


Severity:
serious




Confidence:
public





Submitter:
_Anonymous ( [EMAIL PROTECTED] )

Date Submitted:
Nov 1 2000, 09:33:38 CST

Responsible:
Z_Tomcat Alias ( [EMAIL PROTECTED] )


Synopsis:

Apache + Tomcat bad link handling


 Environment: (jvm, os, osrel, platform)

sun1.3.0-C, win98, fe, win32



Additional Environment Description:

I set up Tomcat with several contexts:
- those provided by default (in %TOMCAT%/webapps);
- my test context c:\www\testj apjmounted as /testj.



Report Description:

I ran Tomcat standalone and it works fine.
On the other hand, Tomcat configured as an add-on to Apache (who serves the static files), with the .dll module loaded has this behaviour:

When I access /testj/hello it works fine with a test servlet.
When I acces /testj/index.html which has a link in it to /testj/hello I receive a 404 HTTP error.

The same servlet works fine if I put it in the /examples context.

So, if it would have been me, I think it shouldn't work at all, therefor I report it as a bug.



How To Reproduce:

null



Workaround:

null



View this report online...






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Source files not being copied into {jakarta.home}build/tomcat/src/

2000-11-01 Thread Stefán F. Stefánsson


Hi... this is more of a pointer than a bug...

Isn't it true that in earlier releases of Tomcat 3.2 the source files
got copied to the src directory when you performed build?

This doesn't happen now when you run build...  it does however happen
when you run build dist...

Is this intentional or a slip?

Regards, Stefan.


Stefan Freyr Stefansson
Software Developer
deCODE Genetics, Inc.

Phone: (+354) 570 2854
GSM:   (+354) 861 1718
Fax:   (+354) 491 3782
 <> 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]