Mike Duan/Toronto/CA/eFunds is out of the office.

2004-08-16 Thread Mike_Duan
I will be out of the office starting  08/16/2004 and will not return until
09/07/2004.

I'll be away from office from August 16 to September 3, 2004, please
contact my manager Shawn Lipman for any urgent issues and I'll return your
email when I come back. Thanks.



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



DO NOT REPLY [Bug 30687] - Session Replication fails with IBM JDK 1.4.2

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30687.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30687

Session Replication fails with IBM JDK 1.4.2





--- Additional Comments From [EMAIL PROTECTED]  2004-08-16 06:57 ---
Start up OK but I still get errors when I shutdown Tomcat:

Aug 16, 2004 2:53:05 PM org.apache.coyote.http11.Http11Protocol pause
INFO: Pausing Coyote HTTP/1.1 on http-9080
Aug 16, 2004 2:53:05 PM org.apache.coyote.tomcat5.CoyoteConnector pause
SEVERE: Protocol handler pause failed
java.net.UnknownHostException: 172.16.168.97: 172.16.168.97
at java.net.InetAddress.getLocalHost(InetAddress.java:1214)
at org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:458)
at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:272)
at org.apache.jk.server.JkMain.pause(JkMain.java:657)
at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:202)
at
org.apache.coyote.tomcat5.CoyoteConnector.pause(CoyoteConnector.java:1444)
at org.apache.catalina.core.StandardService.stop(StandardService.java:521)
at org.apache.catalina.core.StandardServer.stop(StandardServer.java:2347)
at org.apache.catalina.startup.Catalina.stop(Catalina.java:605)
at org.apache.catalina.startup.Catalina.start(Catalina.java:580)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled
Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)
Aug 16, 2004 2:53:06 PM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina

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



DO NOT REPLY [Bug 30689] New: - System.out and System.err in a Listener is not swallowed by swallowOutput=true

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30689.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30689

System.out and System.err in a Listener is not swallowed by swallowOutput=true

   Summary: System.out and System.err in a Listener is not swallowed
by swallowOutput=true
   Product: Tomcat 5
   Version: 5.0.19
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Output to System.out and System.err in a Listener (in my case a
HttpSessionListener) is not swallowed by swallowOutput=true (server.xml, Context
element).

Regards,

Andreas

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



DO NOT REPLY [Bug 30690] New: - Provide an Option so Swallowed System.out/System.err Output is not formatted

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30690.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30690

Provide an Option so Swallowed System.out/System.err Output is not formatted

   Summary: Provide an Option so Swallowed System.out/System.err
Output is not formatted
   Product: Tomcat 5
   Version: 5.0.27
  Platform: All
OS/Version: All
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Catalina
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


I'm using the swallowOutput=true option of the Context element in server.xml to
redirect output via java.util.logging to the servlet log. The problem is,
swallowed ouput is formatted (again), so essentially I've got two timestamps and
an extra newline every some java.util.log messages.

I'd like to propose an option so swallowed output is copied over to the servlet
log as-is, without any formatting.

Regards,

Andreas

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



DO NOT REPLY [Bug 30691] New: - Unreadable Tomcat error messages in Japanese locale

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30691.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30691

Unreadable Tomcat error messages in Japanese locale

   Summary: Unreadable Tomcat error messages in Japanese locale
   Product: Tomcat 5
   Version: 5.0.27
  Platform: PC
   URL: http://www.fk.urban.ne.jp/home/kishida/kouza/tomerr.html
OS/Version: Windows XP
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Servlet  JSP API
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


When encountering server-side errors in a Japanese locale (ja_JP) JVM, Tomcat
returns strings of question marks instead of sensible error messages.  A
Japanese explanation, screen-shot, and work-around exist here:
http://www.fk.urban.ne.jp/home/kishida/kouza/tomerr.html; I am not certain why
this has not been submitted as a bug.  This still exists in 5.0.27.  

Thanks.  Yoroshiku onegaiitashimasu.

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



DO NOT REPLY [Bug 30692] New: - Tomcat hangs for 60sec on startup if Session Replication is enabled

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30692.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30692

Tomcat hangs for 60sec on startup if Session Replication is enabled

   Summary: Tomcat hangs for 60sec on startup if Session Replication
is enabled
   Product: Tomcat 5
   Version: 5.0.27
  Platform: Other
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina:Cluster
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


catalina.out:

Creating ClusterManager for context  using class
org.apache.catalina.cluster.session.DeltaManager




Aug 16, 2004 4:23:33 PM org.apache.catalina.cluster.session.DeltaManager start
INFO: Starting clustering manager...:
Aug 16, 2004 4:23:33 PM org.apache.catalina.cluster.session.DeltaManager start
WARNING: Manager[], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[tcp://172.16.168.97:4002,172.16.168.97,4002,
alive=5481181]. This operation will timeout if no session state has been
received within 60 seconds
Aug 16, 2004 4:24:33 PM org.apache.catalina.cluster.session.DeltaManager start
SEVERE: Manager[], No session state received, timing out.

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



cvs commit: jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/loader WebappLoader.java

2004-08-16 Thread remm
remm2004/08/16 02:31:09

  Modified:catalina/src/share/org/apache/catalina/session
ManagerBase.java
   catalina/src/share/org/apache/catalina/core
StandardEngine.java StandardServer.java
StandardContext.java StandardHost.java
   catalina/src/share/org/apache/catalina Loader.java Host.java
Manager.java Engine.java
   catalina/src/share/org/apache/catalina/mbeans
DefaultContextMBean.java MBeanFactory.java
ServerLifecycleListener.java MBeanUtils.java
   catalina/src/share/org/apache/catalina/loader
WebappLoader.java
  Removed: catalina/src/share/org/apache/catalina/core
StandardDefaultContext.java
   catalina/src/share/org/apache/catalina DefaultContext.java
  Log:
  - Remove DefaultContext.
  - This will need cleanups.
  - For management, I think we should register dummy Context objects with special JMX 
names.
  
  Revision  ChangesPath
  1.31  +1 -32 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/ManagerBase.java
  
  Index: ManagerBase.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/session/ManagerBase.java,v
  retrieving revision 1.30
  retrieving revision 1.31
  diff -u -r1.30 -r1.31
  --- ManagerBase.java  15 Jul 2004 19:12:45 -  1.30
  +++ ManagerBase.java  16 Aug 2004 09:31:05 -  1.31
  @@ -38,7 +38,6 @@
   import javax.management.ObjectName;
   
   import org.apache.catalina.Container;
  -import org.apache.catalina.DefaultContext;
   import org.apache.catalina.Engine;
   import org.apache.catalina.Manager;
   import org.apache.catalina.Session;
  @@ -89,12 +88,6 @@
   
   
   /**
  - * The DefaultContext with which this Manager is associated.
  - */
  -protected DefaultContext defaultContext = null;
  -
  -
  -/**
* Return the MessageDigest implementation to be used when
* creating session identifiers.
*/
  @@ -251,30 +244,6 @@
   }
   
   
  -/**
  - * Return the DefaultContext with which this Manager is associated.
  - */
  -public DefaultContext getDefaultContext() {
  -
  -return (this.defaultContext);
  -
  -}
  -
  -
  -/**
  - * Set the DefaultContext with which this Manager is associated.
  - *
  - * @param defaultContext The newly associated DefaultContext
  - */
  -public void setDefaultContext(DefaultContext defaultContext) {
  -
  -DefaultContext oldDefaultContext = this.defaultContext;
  -this.defaultContext = defaultContext;
  -support.firePropertyChange(defaultContext, oldDefaultContext, 
this.defaultContext);
  -
  -}
  -
  -
   /** Returns the name of the implementation class.
*/
   public String getClassName() {
  
  
  
  1.25  +5 -63 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardEngine.java
  
  Index: StandardEngine.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/core/StandardEngine.java,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- StandardEngine.java   27 Feb 2004 14:58:42 -  1.24
  +++ StandardEngine.java   16 Aug 2004 09:31:05 -  1.25
  @@ -18,12 +18,14 @@
   package org.apache.catalina.core;
   
   
  +import java.io.File;
  +import java.util.List;
  +
   import javax.management.MBeanServer;
   import javax.management.MalformedObjectNameException;
   import javax.management.ObjectName;
  +
   import org.apache.catalina.Container;
  -import org.apache.catalina.Context;
  -import org.apache.catalina.DefaultContext;
   import org.apache.catalina.Engine;
   import org.apache.catalina.Host;
   import org.apache.catalina.LifecycleException;
  @@ -35,8 +37,6 @@
   import org.apache.commons.logging.LogFactory;
   import org.apache.commons.modeler.Registry;
   import org.apache.commons.modeler.modules.MbeansSource;
  -import java.io.File;
  -import java.util.List;
   
   /**
* Standard implementation of the bEngine/b interface.  Each
  @@ -115,11 +115,6 @@
*/ 
   private List mbeans;
   
  -/**
  - * DefaultContext config
  - */
  -private DefaultContext defaultContext;
  -
   
   /**
* The JVM Route ID for this Tomcat instance. All Route ID's must be unique
  @@ -208,30 +203,6 @@
   
   
   /**
  - * Set the DefaultContext
  - * for new web applications.
  - *
  - * @param defaultContext The new DefaultContext
  - */
  -public void addDefaultContext(DefaultContext defaultContext) {
  -
  -DefaultContext 

Mike Duan/Toronto/CA/eFunds is out of the office.

2004-08-16 Thread Mike_Duan
I will be out of the office starting  08/16/2004 and will not return until
09/07/2004.

I'll be away from office from August 16 to September 3, 2004, please
contact my manager Shawn Lipman for any urgent issues and I'll return your
email when I come back. Thanks.



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



Re: [proxy] New implementation ready for testing

2004-08-16 Thread Pier Fumagalli
On 11 Aug 2004, at 17:14, Mladen Turk wrote:
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
3. Added new module proxy_balancer
What's wrong with:
ProxyPassReverse / http://localhost:/
ProxyPreserveHost On
RewriteMap hosts rnd:/opt/apache/conf/tables/hosts.map
RewriteRule ^/(.*) ${hosts:live}/$1 [P,L]
It's in there already, and it works great (I even have a couple of CGIs 
reading and building up that table, enabling, disabling and 
prioritizing hosts).

http://wiki.apache.org/cocoon/ApacheModProxy
http://wiki.apache.org/cocoon/LoadBalancingWithModProxy
	Pier


smime.p7s
Description: S/MIME cryptographic signature


Re: [proxy] New implementation ready for testing

2004-08-16 Thread Remy Maucherat
Pier Fumagalli wrote:
On 11 Aug 2004, at 17:14, Mladen Turk wrote:
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
3. Added new module proxy_balancer

What's wrong with:
ProxyPassReverse / http://localhost:/
ProxyPreserveHost On
RewriteMap hosts rnd:/opt/apache/conf/tables/hosts.map
RewriteRule ^/(.*) ${hosts:live}/$1 [P,L]
It's in there already, and it works great (I even have a couple of 
CGIs reading and building up that table, enabling, disabling and 
prioritizing hosts).

http://wiki.apache.org/cocoon/ApacheModProxy
http://wiki.apache.org/cocoon/LoadBalancingWithModProxy
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/balancer-howto.html#Using%20Apache%202%20with%20mod_proxy%20and%20mod_rewrite
Performance is very bad (much worse than mod_jk, according to testing), 
failover is questionable, and load balancing policies are not available.
So this is definitely a great hack, and it's likely very useful for some 
people but it's not generic enough, and definitely isn't a marketable 
solution.

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


Vacation

2004-08-16 Thread Remy Maucherat
Hi,
I'll be on vacation this week. I'll see if I have time to come up with 
the JDT support in Jasper (I'm stealing some Cocoon code to do it).

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


Mike Duan/Toronto/CA/eFunds is out of the office.

2004-08-16 Thread Mike_Duan
I will be out of the office starting  08/16/2004 and will not return until
09/07/2004.

I'll be away from office from August 16 to September 3, 2004, please
contact my manager Shawn Lipman for any urgent issues and I'll return your
email when I come back. Thanks.



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



Re: [proxy] New implementation ready for testing

2004-08-16 Thread Graham Leggett
Pier Fumagalli wrote:
What's wrong with:
ProxyPassReverse / http://localhost:/
ProxyPreserveHost On
RewriteMap hosts rnd:/opt/apache/conf/tables/hosts.map
RewriteRule ^/(.*) ${hosts:live}/$1 [P,L]
It isn't very elegant though. Someone who is well versed in mod_rewrite 
and regular expressions might find it really easy, but the rest of us 
mortals won't. :(

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


RE: Vacation

2004-08-16 Thread Shapira, Yoav
Hola,
Have fun ;)

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: Monday, August 16, 2004 7:57 AM
To: [EMAIL PROTECTED]
Subject: Vacation

Hi,

I'll be on vacation this week. I'll see if I have time to come up with
the JDT support in Jasper (I'm stealing some Cocoon code to do it).

Rémy


-
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]



{Filename?} Delivery failed

2004-08-16 Thread remm
Warning: This message has had one or more attachments removed
Warning: (okrzod.zip).
Warning: Please read the VirusWarning.txt attachment(s) for more information.

The original message was received at Mon, 16 Aug 2004 19:07:25 +0530 from apache.org 
[97.73.106.194]

- The following addresses had permanent fatal errors -
[EMAIL PROTECTED]



This is a message from the ACL Wireless Ltd MailScanner E-Mail Virus Protection Service
--
The original e-mail attachment okrzod.zip
is on the list of unacceptable attachments for this site and has been
replaced by this warning message.

If you wish to receive a copy of the original attachment, please
e-mail helpdesk and include the whole of this message
in your request. Alternatively, you can call them, with
the contents of this message to hand when you call.

At Mon Aug 16 18:53:03 2004 the virus scanner said:
   MailScanner: DOS/Windows ZIP programs are dangerous in email (okrzod.zip)

Note to Help Desk: Look on ACL Wierless Ltd in 
/var/spool/MailScanner/quarantine/20040816 (message i7GDMrXA019259).
-- 
ACL Wireless Limited
Mail Scanner

Please Contact Network Administrator [EMAIL PROTECTED]


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

DO NOT REPLY [Bug 30654] - web.xml included with servlets-examples contains an error

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30654.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30654

web.xml included with servlets-examples contains an error





--- Additional Comments From [EMAIL PROTECTED]  2004-08-16 13:44 ---
In my installation, the tablib element is the last element in the XML file.

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



DO NOT REPLY [Bug 29485] - Undeploy considered dangerous

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29485.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29485

Undeploy considered dangerous

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Additional Comments From [EMAIL PROTECTED]  2004-08-16 14:48 ---
This javascript confirmatino should only be on the html interface so this should
not effect the ant interface (i.e., calling the undeploy command directly). 
Rather, the html interface should intercept the click and confirm that you
really want to do this (and you realize that it's about to delete all of your
files) before it sends the GET back to tomcat with the undeploy command.

I'll do this one (it's easy enough :)

Daniel

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



DO NOT REPLY [Bug 29485] - Undeploy considered dangerous

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=29485.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29485

Undeploy considered dangerous

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]
 OS/Version|Other   |All
   Priority|Other   |Medium
   Platform|Other   |All
Version|Unknown |5.0.27

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



DO NOT REPLY [Bug 30697] New: - Conformance of clustering to the spec

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30697.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30697

Conformance of clustering to the spec

   Summary: Conformance of clustering to the spec
   Product: Tomcat 5
   Version: 5.0.27
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Catalina:Cluster
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


Dear Sirs,

in the tomcat docs I found the following:

Distributed locking and pages using frames 
Tomcat does not keep session instances in sync across the cluster. The 
implementation of such logic would be to much overhead and cause all kinds of 
problems. If your client accesses the same session simultanously using multiple 
requests, then the last request will override the other sessions in the cluster.

The spec says the following:

Within an application marked as distributable, all requests that are part of a 
session
must be handled by one Java Virtual Machine1 (“JVM”) at a time.

and

These restrictions mean that the Developer is ensured that there are no
additional concurrency issues beyond those encountered in a non-distributed
container.

May be that I misunderstand the tomcat docs but for it seems that the 
implementation of Tomcat's clustering may not be conformant to the spec for 
this point. 

Best regards

Thomas

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



Mike Duan/Toronto/CA/eFunds is out of the office.

2004-08-16 Thread Mike_Duan
I will be out of the office starting  08/16/2004 and will not return until
09/07/2004.

I'll be away from office from August 16 to September 3, 2004, please
contact my manager Shawn Lipman for any urgent issues and I'll return your
email when I come back. Thanks.



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



Re: Tomcat 5.0.28 release

2004-08-16 Thread Jeanfrancois Arcand
[back from vacation :-)]
Costin Manolache wrote:
Shapira, Yoav wrote:
Hi,
I have a couple of only-slightly-related comments, but related
nonetheless so I'll put them here.
Re: endorsed directories.  Do we still want to support JDK 1.3 in Tomcat
5.1?  Since we're gearing up for JDK 1.5, we might want to make 1.4 the
minimum.  I'm +0.5 on this.

First, endorsed directories are _not_ for 1.3, but for 1.4 ( to 
override the build-in parser and the check they do on load ).
1.3 works fine with just having the parser in classpath, or in 
/jre/lib/ext, and it's quite simple to add code to the loader to add 
the parser packages only if 1.3 is detected.
Except if you turn validation on, which will not works since XML schema 
is not supported in Crimson or early version of Xerces (remember the 
nightmare)


I'm using JDK1.3 most of the time, and I think a lot of other people 
and companies are still using it. I don't mind having the default 
distribution built for 1.4+ ( no xerces ), with instructions on how to 
get the additional jars for 1.3. But I think it would be very bad to 
not be able to run in 1.3 - and I don't see any good reason to justify 
forcing the users to upgrade.
One question we should explore is do we really wants to have a 
dependencies on Xerces? Like you already said, a pull parser might be 
better, smaller and more stable than having to rely on Xerces. Not sure 
if pull parser supports schema yet...

+1 of dropping Xerces ;-)
-- Jeanfrancois




them. I prefer the latter approach, also because of the multi-user use
case: if a single Tomcat installation (CATALINA_HOME) is used by
multiple users (each having their own CATALINA_BASE), then the former
approach does not work if each user has a different version of the JDK.

How about stopping support for that scenario?  I mean drop the
CATALINA_BASE versus CATALINA_HOME feature, (or set them to always equal
each other, if we want to leave them in the code base), and don't allow
users to share installations except by the user home directory valve.
The disk space benefits aren't worth it.  The central administration
benefits might be, but I wonder how many people use this.  Maybe an
informal survey on the user list is worth doing?

How about the other way around - stop support for the combined tomcat, 
and default to multi-user ( or multi-config ).

I would be very happy to see the server layout change to support 
multiple configurations.

Something like:
/bin
/lib - with manifest/properties file used to select what goes to 
common, server, shared :-)

/servers
/servers/all
/servers/minimal
With conf/ and webapps/ under each server.
Costin
-
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]


DO NOT REPLY [Bug 30698] New: - apache - tomcat 5 connection

2004-08-16 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30698.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30698

apache -  tomcat 5  connection

   Summary: apache -  tomcat 5  connection
   Product: Tomcat 5
   Version: 5.0.25
  Platform: PC
OS/Version: Linux
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Connector:AJP
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]


I have used  the  unix  socket connection   style to have apache2 connect to 
tomcat to   run jsp. 
###
I get below errors in   my  apache error_log 
[Mon Aug 16 11:23:13 2004] [notice] Apache/2.0.49 (Unix) mod_jk2/2.0.4 
configured -- resuming normal operations
[Mon Aug 16 11:23:13 2004] [error] ajp13.init(): No channel /usr/local/jakarta-
tomcat-5.0.25/work/jk2.socket
[Mon Aug 16 11:28:21 2004] [error] ajp13.init(): No channel /usr/local/jakarta-
tomcat-5.0.25/work/jk2.socket
###

I  tried chaning permissions of this  File .. but it does not help. 
I  have made sure this  File gets recreated  every time tom cat starts. 

I could not find a good tutorial or documentation which explains the 
communication between apache and  tomcat that can help me solve this.

thanks and regards
Anand

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



Mike Duan/Toronto/CA/eFunds is out of the office.

2004-08-16 Thread Mike_Duan
I will be out of the office starting  08/16/2004 and will not return until
09/07/2004.

I'll be away from office from August 16 to September 3, 2004, please
contact my manager Shawn Lipman for any urgent issues and I'll return your
email when I come back. Thanks.



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



Re: [proxy] New implementation ready for testing

2004-08-16 Thread Graham Leggett
Theo Schlossnagle wrote:
I haven't had the time lately, but you (all) are welcome to dissect the 
mod_backhand (Apache 1.3) module and pull the resource collection and 
decision making framework out and put in into mod_proxy for Apache 2.  
I have been watching the commits to proxy, but haven't yet had time to 
go into them in detail yet, so this may or may not be already possible: 
The balancer module should be replaceable, so if you had a java 
application server backend the current balancer with session stickiness 
would probably work for you. Then in other environments, one of the 
mod_backhand components could be switched in to have balancing work 
entirely differently.

Regards,
Graham
--


smime.p7s
Description: S/MIME Cryptographic Signature


cvs commit: jakarta-tomcat-catalina/webapps/docs cgi-howto.xml

2004-08-16 Thread markt
markt   2004/08/16 15:26:50

  Modified:catalina/src/conf web.xml
   catalina/src/share/org/apache/catalina/servlets
CGIServlet.java
   webapps/docs cgi-howto.xml
  Log:
  
  
  Revision  ChangesPath
  1.40  +0 -8  jakarta-tomcat-catalina/catalina/src/conf/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v
  retrieving revision 1.39
  retrieving revision 1.40
  diff -u -r1.39 -r1.40
  --- web.xml   20 Apr 2004 22:22:04 -  1.39
  +++ web.xml   16 Aug 2004 22:26:49 -  1.40
  @@ -262,10 +262,6 @@
 !--   webAppRootDir + File.separator + this prefix.  --
 !--   [WEB-INF/cgi]  --
 !--  --
  -  !--   clientInputTimeout  The time (in milliseconds) to wait for input   --
  -  !--   from the browser before assuming that there--
  -  !--   is none.  [100]--
  -  !--  --
 !--   debug   Debugging detail level for messages logged --
 !--   by this servlet.  [0]  --
 !--  --
  @@ -284,10 +280,6 @@
   servlet
   servlet-namecgi/servlet-name
   servlet-classorg.apache.catalina.servlets.CGIServlet/servlet-class
  -init-param
  -  param-nameclientInputTimeout/param-name
  -  param-value100/param-value
  -/init-param
   init-param
 param-namedebug/param-name
 param-value6/param-value
  
  
  
  1.23  +5 -23 
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/CGIServlet.java
  
  Index: CGIServlet.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/servlets/CGIServlet.java,v
  retrieving revision 1.22
  retrieving revision 1.23
  diff -u -r1.22 -r1.23
  --- CGIServlet.java   16 Jun 2004 18:22:20 -  1.22
  +++ CGIServlet.java   16 Aug 2004 22:26:50 -  1.23
  @@ -247,21 +247,12 @@
   
   /* some vars below copied from Craig R. McClanahan's InvokerServlet */
   
  -/** the string manager for this package. */
  -/* YAGNI
  -private static StringManager sm =
  -StringManager.getManager(Constants.Package);
  -*/
  -
   /** the Context container associated with our web application. */
   private ServletContext context = null;
   
   /** the debugging detail level for this servlet. */
   private int debug = 0;
   
  -/** the time in ms to wait for the client to send us CGI input data */
  -private int iClientInputTimeout = 100;
  -
   /**
*  The CGI search path will start at
*webAppRootDir + File.separator + cgiPathPrefix
  @@ -314,9 +305,6 @@
   debug = Integer.parseInt(value);
   cgiPathPrefix =
   getServletConfig().getInitParameter(cgiPathPrefix);
  -value =
  -getServletConfig().getInitParameter(iClientInputTimeout);
  -iClientInputTimeout = Integer.parseInt(value);
   } catch (Throwable t) {
   //NOOP
   }
  @@ -328,13 +316,7 @@
   }
   
   // Identify the internal container resources we need
  -//Wrapper wrapper = (Wrapper) getServletConfig();
  -//context = (Context) wrapper.getParent();
  -
   context = config.getServletContext();
  -if (debug = 1) {
  -//log(init: Associated with Context ' + context.getPath() + ');
  -}
   
   }
   
  
  
  
  1.5   +0 -3  jakarta-tomcat-catalina/webapps/docs/cgi-howto.xml
  
  Index: cgi-howto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/docs/cgi-howto.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- cgi-howto.xml 19 Feb 2004 21:37:27 -  1.4
  +++ cgi-howto.xml 16 Aug 2004 22:26:50 -  1.5
  @@ -56,9 +56,6 @@
   listrongcgiPathPrefix/strong - The CGI search path will start at
   the web application root directory + File.separator + this prefix.
   The default cgiPathPrefix is code/WEB-INF/cgi/code/li
  -listrongclientInputTimeout/strong - The time (in milliseconds) to
  -wait for input from the browser before assuming that there is none.
  -Default is code100/code seconds./li
   listrongdebug/strong - Debugging detail level for messages logged
   by this servlet. Default 0./li
   listrongexecutable/strong - The of the 

cvs commit: jakarta-tomcat-4.0/webapps/tomcat-docs cgi-howto.xml

2004-08-16 Thread markt
markt   2004/08/16 15:29:34

  Modified:catalina/src/conf web.xml
   catalina/src/share/org/apache/catalina/servlets
CGIServlet.java
   webapps/tomcat-docs cgi-howto.xml
  Log:
  Housekeeping in CGI servlet
  
  Revision  ChangesPath
  1.57  +0 -8  jakarta-tomcat-4.0/catalina/src/conf/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v
  retrieving revision 1.56
  retrieving revision 1.57
  diff -u -r1.56 -r1.57
  --- web.xml   20 Apr 2004 22:21:09 -  1.56
  +++ web.xml   16 Aug 2004 22:29:33 -  1.57
  @@ -230,10 +230,6 @@
 !--   webAppRootDir + File.separator + this prefix.  --
 !--   [WEB-INF/cgi]  --
 !--  --
  -  !--   clientInputTimeout  The time (in milliseconds) to wait for input   --
  -  !--   from the browser before assuming that there--
  -  !--   is none.  [100]--
  -  !--  --
 !--   debug   Debugging detail level for messages logged --
 !--   by this servlet.  [0]  --
 !--  --
  @@ -252,10 +248,6 @@
   servlet
   servlet-namecgi/servlet-name
   servlet-classorg.apache.catalina.servlets.CGIServlet/servlet-class
  -init-param
  -  param-nameclientInputTimeout/param-name
  -  param-value100/param-value
  -/init-param
   init-param
 param-namedebug/param-name
 param-value6/param-value
  
  
  
  1.25  +7 -25 
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/CGIServlet.java
  
  Index: CGIServlet.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets/CGIServlet.java,v
  retrieving revision 1.24
  retrieving revision 1.25
  diff -u -r1.24 -r1.25
  --- CGIServlet.java   16 Jun 2004 18:21:54 -  1.24
  +++ CGIServlet.java   16 Aug 2004 22:29:33 -  1.25
  @@ -291,21 +291,12 @@
   
   /* some vars below copied from Craig R. McClanahan's InvokerServlet */
   
  -/** the string manager for this package. */
  -/* YAGNI
  -private static StringManager sm =
  -StringManager.getManager(Constants.Package);
  -*/
  -
   /** the Context container associated with our web application. */
   private ServletContext context = null;
   
   /** the debugging detail level for this servlet. */
   private int debug = 0;
   
  -/** the time in ms to wait for the client to send us CGI input data */
  -private int iClientInputTimeout = 100;
  -
   /**
*  The CGI search path will start at
*webAppRootDir + File.separator + cgiPathPrefix
  @@ -359,9 +350,6 @@
   debug = Integer.parseInt(value);
   cgiPathPrefix =
   getServletConfig().getInitParameter(cgiPathPrefix);
  -value =
  -getServletConfig().getInitParameter(iClientInputTimeout);
  -iClientInputTimeout = Integer.parseInt(value);
   } catch (Throwable t) {
   //NOOP
   }
  @@ -373,13 +361,7 @@
   }
   
   // Identify the internal container resources we need
  -//Wrapper wrapper = (Wrapper) getServletConfig();
  -//context = (Context) wrapper.getParent();
  -
   context = config.getServletContext();
  -if (debug = 1) {
  -//log(init: Associated with Context ' + context.getPath() + ');
  -}
   
   }
   
  
  
  
  1.4   +0 -3  jakarta-tomcat-4.0/webapps/tomcat-docs/cgi-howto.xml
  
  Index: cgi-howto.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/tomcat-docs/cgi-howto.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- cgi-howto.xml 19 Feb 2004 21:38:50 -  1.3
  +++ cgi-howto.xml 16 Aug 2004 22:29:34 -  1.4
  @@ -52,9 +52,6 @@
   listrongcgiPathPrefix/strong - The CGI search path will start at
   the web application root directory + File.separator + this prefix.
   The default cgiPathPrefix is code/WEB-INF/cgi/code/li
  -listrongclientInputTimeout/strong - The time (in milliseconds) to
  -wait for input from the browser before assuming that there is none.
  -Default is code100/code seconds./li
   listrongdebug/strong - Debugging detail level for messages logged
   by this servlet. Default 0./li
   listrongexecutable/strong - The 

RE: cvs commit: jakarta-tomcat-catalina/webapps/docs cgi-howto.xml

2004-08-16 Thread Mark Thomas
Sorry. Finger trouble. Comment for this should have been:

Housekeeping in CGI servlet. 

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
 Sent: Monday, August 16, 2004 11:27 PM
 To: [EMAIL PROTECTED]
 Subject: cvs commit: jakarta-tomcat-catalina/webapps/docs 
 cgi-howto.xml
 
 markt   2004/08/16 15:26:50
 
   Modified:catalina/src/conf web.xml
catalina/src/share/org/apache/catalina/servlets
 CGIServlet.java
webapps/docs cgi-howto.xml
   Log:
   
   
   Revision  ChangesPath
   1.40  +0 -8  
 jakarta-tomcat-catalina/catalina/src/conf/web.xml
   
   Index: web.xml
   ===
   RCS file: 
 /home/cvs/jakarta-tomcat-catalina/catalina/src/conf/web.xml,v
   retrieving revision 1.39
   retrieving revision 1.40
   diff -u -r1.39 -r1.40
   --- web.xml 20 Apr 2004 22:22:04 -  1.39
   +++ web.xml 16 Aug 2004 22:26:49 -  1.40
   @@ -262,10 +262,6 @@
  !--   webAppRootDir + 
 File.separator + this prefix.  --
  !--   [WEB-INF/cgi] 
  --
  !-- 
  --
   -  !--   clientInputTimeout  The time (in milliseconds) to 
 wait for input   --
   -  !--   from the browser before 
 assuming that there--
   -  !--   is none.  [100]   
  --
   -  !-- 
  --
  !--   debug   Debugging detail level for 
 messages logged --
  !--   by this servlet.  [0] 
  --
  !-- 
  --
   @@ -284,10 +280,6 @@
servlet
servlet-namecgi/servlet-name

 servlet-classorg.apache.catalina.servlets.CGIServlet/servlet-class
   -init-param
   -  param-nameclientInputTimeout/param-name
   -  param-value100/param-value
   -/init-param
init-param
  param-namedebug/param-name
  param-value6/param-value
   
   
   
   1.23  +5 -23 
 jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina
 /servlets/CGIServlet.java
   
   Index: CGIServlet.java
   ===
   RCS file: 
 /home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apach
 e/catalina/servlets/CGIServlet.java,v
   retrieving revision 1.22
   retrieving revision 1.23
   diff -u -r1.22 -r1.23
   --- CGIServlet.java 16 Jun 2004 18:22:20 -  1.22
   +++ CGIServlet.java 16 Aug 2004 22:26:50 -  1.23
   @@ -247,21 +247,12 @@

/* some vars below copied from Craig R. McClanahan's 
 InvokerServlet */

   -/** the string manager for this package. */
   -/* YAGNI
   -private static StringManager sm =
   -StringManager.getManager(Constants.Package);
   -*/
   -
/** the Context container associated with our web 
 application. */
private ServletContext context = null;

/** the debugging detail level for this servlet. */
private int debug = 0;

   -/** the time in ms to wait for the client to send us 
 CGI input data */
   -private int iClientInputTimeout = 100;
   -
/**
 *  The CGI search path will start at
 *webAppRootDir + File.separator + cgiPathPrefix
   @@ -314,9 +305,6 @@
debug = Integer.parseInt(value);
cgiPathPrefix =

 getServletConfig().getInitParameter(cgiPathPrefix);
   -value =
   -
 getServletConfig().getInitParameter(iClientInputTimeout);
   -iClientInputTimeout = Integer.parseInt(value);
} catch (Throwable t) {
//NOOP
}
   @@ -328,13 +316,7 @@
}

// Identify the internal container resources we need
   -//Wrapper wrapper = (Wrapper) getServletConfig();
   -//context = (Context) wrapper.getParent();
   -
context = config.getServletContext();
   -if (debug = 1) {
   -//log(init: Associated with Context ' + 
 context.getPath() + ');
   -}

}

   
   
   
   1.5   +0 -3  
 jakarta-tomcat-catalina/webapps/docs/cgi-howto.xml
   
   Index: cgi-howto.xml
   ===
   RCS file: 
 /home/cvs/jakarta-tomcat-catalina/webapps/docs/cgi-howto.xml,v
   retrieving revision 1.4
   retrieving revision 1.5
   diff -u -r1.4 -r1.5
   --- cgi-howto.xml   19 Feb 2004 21:37:27 -  1.4
   +++ cgi-howto.xml   16 Aug 2004 22:26:50 -  1.5
   @@ -56,9 +56,6 @@
listrongcgiPathPrefix/strong - The CGI search path 
 

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler JspDocumentParser.java ParserController.java

2004-08-16 Thread kinman
kinman  2004/08/16 15:35:38

  Modified:jasper2/src/share/org/apache/jasper/compiler
JspDocumentParser.java ParserController.java
  Log:
  - Close any InputStream open in JspDocumentParser.
  
  Revision  ChangesPath
  1.83  +24 -37
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java
  
  Index: JspDocumentParser.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/JspDocumentParser.java,v
  retrieving revision 1.82
  retrieving revision 1.83
  diff -u -r1.82 -r1.83
  --- JspDocumentParser.java13 Jul 2004 20:38:56 -  1.82
  +++ JspDocumentParser.java16 Aug 2004 22:35:37 -  1.83
  @@ -18,6 +18,8 @@
   import java.io.CharArrayWriter;
   import java.io.FileNotFoundException;
   import java.io.IOException;
  +import java.io.InputStream;
  +
   import java.util.Iterator;
   import java.util.List;
   import java.util.jar.JarFile;
  @@ -166,24 +168,32 @@
   
   // Parse the input
   SAXParser saxParser = getSAXParser(false, jspDocParser);
  +InputStream inStream = null;
   try {
  -saxParser.parse(
  -jspDocParser.getInputSource(
  -path,
  -jarFile,
  -jspDocParser.ctxt,
  -jspDocParser.err),
  -jspDocParser);
  +inStream = JspUtil.getInputStream(path, jarFile,
  +  jspDocParser.ctxt,
  +  jspDocParser.err);
  +saxParser.parse(new InputSource(inStream), jspDocParser);
   } catch (EnableDTDValidationException e) {
   saxParser = getSAXParser(true, jspDocParser);
   jspDocParser.isValidating = true;
  -saxParser.parse(
  -jspDocParser.getInputSource(
  -path,
  -jarFile,
  -jspDocParser.ctxt,
  -jspDocParser.err),
  -jspDocParser);
  +if (inStream != null) {
  +try {
  +inStream.close();
  +} catch (Exception any) {
  +}
  +}
  +inStream = JspUtil.getInputStream(path, jarFile,
  +  jspDocParser.ctxt,
  +  jspDocParser.err);
  +saxParser.parse(new InputSource(inStream), jspDocParser);
  +} finally {
  +if (inStream != null) {
  +try {
  +inStream.close();
  +} catch (Exception any) {
  +}
  +}
   }
   
   if (parent == null) {
  @@ -1369,29 +1379,6 @@
   xmlReader.setErrorHandler(jspDocParser);
   
   return saxParser;
  -}
  -
  -/*
  - * Gets an InputSource to the JSP document or tag file to be parsed.
  - *
  - * @param path The path to the JSP document or tag file to be parsed
  - * @param jarFile The JAR file from which to read the JSP document or tag
  - * file, or null if the JSP document or tag file is to be read from the
  - * filesystem
  - * @param ctxt The JSP compilation context
  - * @param err The error dispatcher
  - *
  - * @return An InputSource to the requested JSP document or tag file
  - */
  -private InputSource getInputSource(
  -String path,
  -JarFile jarFile,
  -JspCompilationContext ctxt,
  -ErrorDispatcher err)
  -throws Exception {
  -
  -return new InputSource(
  -JspUtil.getInputStream(path, jarFile, ctxt, err));
   }
   
   /*
  
  
  
  1.54  +8 -16 
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ParserController.java
  
  Index: ParserController.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ParserController.java,v
  retrieving revision 1.53
  retrieving revision 1.54
  diff -u -r1.53 -r1.54
  --- ParserController.java 12 Jul 2004 22:54:33 -  1.53
  +++ ParserController.java 16 Aug 2004 22:35:37 -  1.54
  @@ -192,22 +192,14 @@
// Dispatch to the appropriate parser
if (isXml) {
// JSP document (XML syntax)
  - InputStream inStream = null;
  - try {
  - parsedPage = JspDocumentParser.parse(this, absFileName,
  -  jarFile, parent,
  - 

Re: Tomcat 5.0.28 release

2004-08-16 Thread Vic Cekvenich
Costin Manolache wrote:


- jdk1.3 - it'll work if you add your own parser in common/lib or 
jre/lib/ext or classpath

- jdk1.4 - because the parser in jdk1.4 is an old xerces, xml schema 
validation might fail, everything else should work.

- jdk1.5 - AFAIK everything should work.
The reason endorsed was added is JDK1.4, where we had to add newer 
org.apache.xerces and javax.xml ( replacing what's in rt.jar ).

Costin

Why not only support JDK 1.4 and above?
.V
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


cvs commit: jakarta-tomcat-catalina/webapps/admin/WEB-INF web.xml

2004-08-16 Thread remm
remm2004/08/16 16:31:26

  Modified:webapps/admin login.jsp build.xml
   webapps/admin/WEB-INF web.xml
  Log:
  - Implement Costin's trick to avoid having to load-on-startup the admin webapp.
  
  Revision  ChangesPath
  1.5   +4 -0  jakarta-tomcat-catalina/webapps/admin/login.jsp
  
  Index: login.jsp
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/admin/login.jsp,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- login.jsp 27 Aug 2003 23:32:30 -  1.4
  +++ login.jsp 16 Aug 2004 23:31:25 -  1.5
  @@ -5,6 +5,10 @@
   %@ taglib uri=/WEB-INF/struts-html.tld prefix=html %
   %@ taglib uri=/WEB-INF/struts-logic.tld prefix=logic %
   
  +% // Force the initialization of action servlet
  +   getServletContext().getNamedDispatcher(action).include(request,response);
  +% 
  +
   html:html locale=true
   
   !-- Make sure window is not in a frame --
  
  
  
  1.13  +2 -1  jakarta-tomcat-catalina/webapps/admin/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/admin/build.xml,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -u -r1.12 -r1.13
  --- build.xml 10 Aug 2004 22:42:37 -  1.12
  +++ build.xml 16 Aug 2004 23:31:25 -  1.13
  @@ -186,7 +186,8 @@
 !--  BUILD: Copy Static Files == --
 target name=build-static 
depends=flags,flags.display,build-prepare,copy-struts.jar
   copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib 
file=${commons-beanutils.jar}/
  -copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib 
file=${commons-collections.jar}/
  +copy 
tofile=${webapps.build}/${webapp.name}/WEB-INF/lib/commons-collections.jar 
  + file=${commons-collections.jar}/
   copy todir=${webapps.build}/${webapp.name}/WEB-INF/lib 
file=${commons-digester.jar}/
   copy todir=${webapps.build}/${webapp.name}
 fileset dir=.
  
  
  
  1.11  +0 -2  jakarta-tomcat-catalina/webapps/admin/WEB-INF/web.xml
  
  Index: web.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-catalina/webapps/admin/WEB-INF/web.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- web.xml   23 Jul 2004 14:02:17 -  1.10
  +++ web.xml   16 Aug 2004 23:31:26 -  1.11
  @@ -99,8 +99,6 @@
 param-namedomain/param-name
 param-valueCatalina/param-value
   /init-param
  -
  -load-on-startup2/load-on-startup
 /servlet
   
 !-- Action Servlet Mapping --
  
  
  

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



cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspCompilationContext.java

2004-08-16 Thread remm
remm2004/08/16 16:48:36

  Modified:jasper2/src/share/org/apache/jasper/compiler
ErrorDispatcher.java Compiler.java
   jasper2/src/share/org/apache/jasper
JspCompilationContext.java
  Added:   jasper2/src/share/org/apache/jasper/compiler
AntCompiler.java JDTCompiler.java
  Log:
  - Add JDT support.
  - The plugin system is quite bad but works (I did this on the train, which was very 
late, but still not late enough
for me to come up with something better): if JDT isn't there, use Ant.
  - Error mapping is implemented with JDT.
  - JDT is about twice as fast as javac, while being less than 1MB, and loading source 
dependencies from the
context classloader (this should help a lot for servers with disk trashing during 
compilation; of course, the code
generation is a very expensive step as well). This will allow Tomcat to run on a 
JRE only as well.
  - I didn't test the speed of the generated bytecode yet against the javac generated 
bytecode for the same class
(Jikes used to be bad at that).
  - The code was stolen from Cocoon (which removed their author tags so I can't credit 
anyone for the good code :( ).
  
  Revision  ChangesPath
  1.22  +72 -56
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java
  
  Index: ErrorDispatcher.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -r1.21 -r1.22
  --- ErrorDispatcher.java  13 Jul 2004 18:40:08 -  1.21
  +++ ErrorDispatcher.java  16 Aug 2004 23:48:35 -  1.22
  @@ -432,13 +432,13 @@
   String errMsg, String fname, Node.Nodes page)
throws IOException, JasperException {
   
  - Vector errVec = new Vector();
  - StringBuffer errMsgBuf = null;
  - int lineNum = -1;
  +Vector errVec = new Vector();
  +StringBuffer errMsgBuf = null;
  +int lineNum = -1;
   JavacErrorDetail javacError = null;
  -
  +
   BufferedReader reader = new BufferedReader(new StringReader(errMsg));
  -
  +
   /*
* Parse compilation errors. Each compilation error consists of a file
* path and error line number, followed by a number of lines describing
  @@ -446,82 +446,98 @@
*/
   String line = null;
   while ((line = reader.readLine()) != null) {
  -
  +
   /*
  -  * Error line number is delimited by set of colons.
  -  * Ignore colon following drive letter on Windows (fromIndex = 2).
  -  * XXX Handle deprecation warnings that don't have line info
  -  */
  + * Error line number is delimited by set of colons.
  + * Ignore colon following drive letter on Windows (fromIndex = 2).
  + * XXX Handle deprecation warnings that don't have line info
  + */
   int beginColon = line.indexOf(':', 2); 
   int endColon = line.indexOf(':', beginColon + 1);
   if ((beginColon = 0)  (endColon = 0)) {
   if (javacError != null) {
   // add previous error to error vector
   errVec.add(javacError);
  - }
  -
  - String lineNumStr = line.substring(beginColon + 1, endColon);
  +}
  +
  +String lineNumStr = line.substring(beginColon + 1, endColon);
   try {
   lineNum = Integer.parseInt(lineNumStr);
   } catch (NumberFormatException e) {
   // XXX
   }
  -
  +
   errMsgBuf = new StringBuffer();
  -
  -// Attempt to map javac error line number to line in JSP page
  - ErrorVisitor errVisitor = new ErrorVisitor(lineNum);
  - page.visit(errVisitor);
  -Node errNode = errVisitor.getJspSourceNode();
  -if ((errNode != null)  (errNode.getStart() != null)) {
  -javacError = new JavacErrorDetail(
  -fname,
  -lineNum,
  -errNode.getStart().getFile(),
  -errNode.getStart().getLineNumber(),
  -errMsgBuf);
  -} else {
  -/*
  - * javac error line number cannot be mapped to JSP page
  - * line number. For example, this is the case if a 
  - * scriptlet is missing a closing brace, which causes
  

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

2004-08-16 Thread remm
remm2004/08/16 16:48:59

  Modified:catalina/src/share/org/apache/catalina/startup
Bootstrap.java
  Log:
  - New error message when JMX isn't there.
  
  Revision  ChangesPath
  1.20  +5 -8  
jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Bootstrap.java
  
  Index: Bootstrap.java
  ===
  RCS file: 
/home/cvs/jakarta-tomcat-catalina/catalina/src/share/org/apache/catalina/startup/Bootstrap.java,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- Bootstrap.java23 Jun 2004 16:59:41 -  1.19
  +++ Bootstrap.java16 Aug 2004 23:48:59 -  1.20
  @@ -63,13 +63,10 @@
   
   
   private static final String JMX_ERROR_MESSAGE =
  -Due to new licensing guidelines mandated by the Apache Software\n
  -+ Foundation Board of Directors, a JMX implementation can no longer\n
  -+ be distributed with the Apache Tomcat binaries. As a result, you \n
  -+ must download a JMX 1.2 implementation (such as the Sun Reference\n
  -+ Implementation) and copy the JAR containing the API and \n
  -+ implementation of the JMX specification to: \n 
  -+ ${catalina.home}/bin/jmx.jar;
  +This release of Apache Tomcat was packaged to run on J2SE 5.0 \n
  ++ or later. It can be run on earlier JVMs by downloading and \n
  ++ installing a compatibility package from the Apache Tomcat \n
  ++ binary download page.;
   
   
   /**
  
  
  

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



cvs commit: jakarta-tomcat-catalina/catalina build.xml

2004-08-16 Thread remm
remm2004/08/16 16:52:11

  Modified:.build.xml build.properties.default tomcat.nsi
   jasper2  build.xml
   catalina/src/share/org/apache/catalina/startup
TldConfig.java
   catalina build.xml
  Log:
  - Move dependencies and stuff around.
  - Add download for JDT (the poor server is going to suffer ...), with repackaging 
(the JDT JAR is quite big, and
we only need a fraction of it). The JDT packaging isn't very good overall, and 
unfortunately there's a 14MB download
to end up with a 900KB JAR in the end.
  - Move JMX and Xerces to the compat bundle.
  
  Revision  ChangesPath
  1.197 +39 -9 jakarta-tomcat-5/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-5/build.xml,v
  retrieving revision 1.196
  retrieving revision 1.197
  diff -u -r1.196 -r1.197
  --- build.xml 13 Aug 2004 07:22:22 -  1.196
  +++ build.xml 16 Aug 2004 23:52:11 -  1.197
  @@ -57,7 +57,10 @@
 property name=webapps.dist value=${catalina.home}/webapps/dist/
 property name=tomcat-dbcp.home value=${base.path}/tomcat-deps /
 property name=tomcat-dbcp.jar 
  -   value=${tomcat-dbcp.home}/naming-factory-dbcp-${commons-dbcp.version}.jar/
  +   value=${tomcat-dbcp.home}/naming-factory-dbcp.jar/
  +  property name=jasper-compiler-jdt.home value=${base.path}/tomcat-deps /
  +  property name=jasper-compiler-jdt.jar 
  +   value=${jasper-compiler-jdt.home}/jasper-compiler-jdt.jar/
 
 !-- Some compilers will disable debugging if true. And it doesn't do anything 
  in most cases --
  @@ -140,7 +143,6 @@
   
   copy todir=${tomcat.build}/bin 
  file=${commons-logging-api.jar} /
  -copy tofile=${tomcat.build}/bin/jmx.jar file=${jmx.jar} /
   
   copy todir=${tomcat.build}/server/lib file=${commons-modeler.jar} /
   
  @@ -148,8 +150,9 @@
   copy todir=${tomcat.build}/bin file=${commons-daemon.jsvc.tar.gz} 
   failonerror=false /
   
  -copy todir=${tomcat.build}/common/lib file=${ant.jar}/
  -copy todir=${tomcat.build}/common/lib file=${ant-launcher.jar}/
  +!-- copy todir=${tomcat.build}/common/lib file=${ant.jar}/
  +copy todir=${tomcat.build}/common/lib file=${ant-launcher.jar}/ --
  + copy todir=${tomcat.build}/common/lib file=${jasper-compiler-jdt.jar}/
 /target
   
 !-- == Build all components === --
  @@ -514,7 +517,14 @@
 param name=destfile value=${tomcat-dbcp.jar} /
   /antcall
   
  -   antcall target=build-tomcat-dbcp /
  +antcall target=build-tomcat-dbcp /
  +
  +antcall target=downloadzip
  +  param name=sourcefile value=${jdt.loc}/
  +  param name=destfile value=${jdt.jar}/
  +  param name=destdir value=${base.path}/
  +/antcall
  +antcall target=build-jasper-compiler-jdt /
 /target
   
 target name=build-tomcat-dbcp
  @@ -573,6 +583,24 @@
   /jar
 /target
   
  +   target name=build-jasper-compiler-jdt
  +mkdir dir=${jasper-compiler-jdt.home}/
  +antcall target=-build-jasper-compiler-jdt
  +   param name=basedir value=${jasper-compiler-jdt.home} /
  +/antcall
  +   /target
  +
  +   target name=-build-jasper-compiler-jdt
  + unjar src=${jdt.jar} dest=${jasper-compiler-jdt.home} /
  + jar destfile=${jasper-compiler-jdt.jar} index=true
  + fileset dir=${jasper-compiler-jdt.home}
  + include name=org/eclipse/jdt/core/compiler/**/
  + include name=org/eclipse/jdt/internal/compiler/**/
  + include 
name=org/eclipse/jdt/internal/core/util/CommentRecorder*/
  + /fileset
  + /jar
  +   /target
  + 
 target name=build-webapps depends=init
 description=build  webapps
   
  @@ -714,8 +742,7 @@
   copy todir=embed/lib file=${jmx.jar}/
   copy todir=embed/lib file=${regexp.jar}/
   
  -copy todir=embed/lib file=${ant.jar}/
  -copy todir=embed/lib file=${ant-launcher.jar}/ 
  +copy todir=embed/lib file=${jdt.jar}/
   
   copy todir=embed/lib
 fileset dir=build/server/lib
  @@ -849,8 +876,10 @@
  /fileset
   /jar
   
  + !--
   copy todir=${tomcat.deployer}/lib file=${xercesImpl.jar}/
   copy todir=${tomcat.deployer}/lib file=${xml-apis.jar}/
  +--
   
   copy todir=${tomcat.deployer}
 fileset dir=${basedir}/resources/deployer /
  @@ -870,10 +899,11 @@
   
 !-- == Compat target === --
   
  -  target name=compat description=Create compatibility binaries for JREs before 
1.4 
  +  target name=compat description=Create compatibility binaries for JREs before 
1.5 
   
   copy todir=${tomcat.compat}/common/endorsed 

Document

2004-08-16 Thread mikeb
--  Virus Warning Message (on uusnwa0p)  --

Found virus WORM_NETSKY.Z in file Bill.txt 
   
 .exe (in Bill.zip)
The uncleanable file is deleted.

-
Important bill!


--  Virus Warning Message (on uusnwa0p)  --

Bill.zip is removed from here because it contains a virus.

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

Re: cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper JspCompilationContext.java

2004-08-16 Thread Bill Barker
   -jspCompiler = new Compiler(this, jsw);
   +jspCompiler = null;
   +try {
   +jspCompiler =
   +(Compiler)
Class.forName(org.apache.jasper.compiler.JDTCompiler).newInstance();
   +} catch (Throwable t) {
   +// Log ?
   +// FIXME: log
   +}
   +try {
   +jspCompiler =
   +(Compiler)
Class.forName(org.apache.jasper.compiler.AntCompiler).newInstance();
   +} catch (Throwable t) {
   +// Log ?
   +// FIXME: log
   +}
   +jspCompiler.init(this, jsw);
return jspCompiler;
}


This will always give you an AntCompiler.


This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

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

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

2004-08-16 Thread billbarker
billbarker2004/08/16 20:16:59

  Modified:coyote   build.xml
  Log:
  Splitting the adapter jars from the shared jar in the build.
  
  This is so I can inch the Tomcat Gump builds a bit closer to sanity, and it won't 
take so long to test changes to the project files.
  
  Revision  ChangesPath
  1.29  +21 -12jakarta-tomcat-connectors/coyote/build.xml
  
  Index: build.xml
  ===
  RCS file: /home/cvs/jakarta-tomcat-connectors/coyote/build.xml,v
  retrieving revision 1.28
  retrieving revision 1.29
  diff -u -r1.28 -r1.29
  --- build.xml 16 Mar 2004 19:48:38 -  1.28
  +++ build.xml 17 Aug 2004 03:16:59 -  1.29
  @@ -271,13 +271,9 @@
   /copy
 /target
   
  -  target name=compile 
  -   depends=static,report,compile.shared,compile.tomcat4,compile.tomcat33
  -   description=Compile Coyote and its Adapters
  +  target name=shared.jar depends=static,compile.shared
  +   description=Build shared Coyote jar 
   property name=tomcat-coyote.jar 
value=${build.home}/lib/tomcat-${component.name}.jar /
  -property name=tomcat33-coyote.jar 
value=${build.home}/lib/tomcat33-${component.name}.jar /
  -property name=tomcat4-coyote.jar 
value=${build.home}/lib/tomcat4-${component.name}.jar /
  -
   jarjarfile=${tomcat-coyote.jar}
   index=true
   manifest=${build.home}/conf/MANIFEST.MF
  @@ -288,18 +284,31 @@
   include name=org/apache/coyote/**/
 /fileset
   /jar
  -
  -jar jarfile=${tomcat33-coyote.jar}
  +  /target
  + 
  +  target name=tomcat4.jar depends=static,compile.shared,compile.tomcat4
  +   description=Build Tomcat 4 Adapter jar if=tomcat4.detect
  +property name=tomcat4-coyote.jar 
value=${build.home}/lib/tomcat4-${component.name}.jar /
  +jar jarfile=${tomcat4-coyote.jar}
index=true
basedir=${build.home}/classes
manifest=${build.home}/conf/MANIFEST.MF
  - includes=org/apache/coyote/tomcat3/** / 
  + includes=org/apache/coyote/tomcat4/** /
  +  /target
   
  -jar jarfile=${tomcat4-coyote.jar}
  +  target name=tomcat33.jar depends=static,compile.shared,compile.tomcat33
  +   description=Build Tomcat 3.3 Adapter jar if=tomcat33.detect
  +property name=tomcat33-coyote.jar 
value=${build.home}/lib/tomcat33-${component.name}.jar /
  +jar jarfile=${tomcat33-coyote.jar}
index=true
basedir=${build.home}/classes
manifest=${build.home}/conf/MANIFEST.MF
  - includes=org/apache/coyote/tomcat4/** /
  + includes=org/apache/coyote/tomcat3/** / 
  +  /target
  +
  +  target name=compile 
  +   depends=static,report,shared.jar,tomcat4.jar,tomcat33.jar
  +   description=Compile Coyote and its Adapters
 /target
   
 target name=compile.tests depends=compile
  
  
  

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



Re: Tomcat 5.0.28 release

2004-08-16 Thread Costin Manolache
Jeanfrancois Arcand wrote:
Shapira, Yoav wrote:
Hi,
I have a couple of only-slightly-related comments, but related
nonetheless so I'll put them here.
Re: endorsed directories.  Do we still want to support JDK 1.3 in Tomcat
5.1?  Since we're gearing up for JDK 1.5, we might want to make 1.4 the
minimum.  I'm +0.5 on this.

First, endorsed directories are _not_ for 1.3, but for 1.4 ( to 
override the build-in parser and the check they do on load ).
1.3 works fine with just having the parser in classpath, or in 
/jre/lib/ext, and it's quite simple to add code to the loader to add 
the parser packages only if 1.3 is detected.

Except if you turn validation on, which will not works since XML schema 
is not supported in Crimson or early version of Xerces (remember the 
nightmare)

Yes, schema validation on JDK1.4 is lost because the parser doesn't 
support it well enough.

I think it may be better to just check if the parser supports schema 
validation, and if not just display a warning that schema validation is 
disabled on parser that don't support it. It's easy to detect what 
version of xerces or if crimson is used.

Fact is a lot of parsers don't support schema validation, and it is 
better to allow tomcat to work with any parser than try to force a 
specific version of parser.

Well, the right solution is to just remove the option to turn schema 
validation on at startup - it is a huge waste of time at startup, it 
should be done only at deploy time by deploy tools :-)



I'm using JDK1.3 most of the time, and I think a lot of other people 
and companies are still using it. I don't mind having the default 
distribution built for 1.4+ ( no xerces ), with instructions on how to 
get the additional jars for 1.3. But I think it would be very bad to 
not be able to run in 1.3 - and I don't see any good reason to justify 
forcing the users to upgrade.

One question we should explore is do we really wants to have a 
dependencies on Xerces? Like you already said, a pull parser might be 
better, smaller and more stable than having to rely on Xerces. Not sure 
if pull parser supports schema yet...

+1 of dropping Xerces ;-)
I don't think many pull parsers support schema, they are supposed to be 
faster and simpler :-)

It's not about dropping xerces - we will still use the xerces inside 
jdk1.4 and jdk1.5 - we just shouldn't force a specific version and take 
all the pain for endorsed.dir - but let the user use whatever Jaxp 
parser he wants and disable schema validation if the parser doesn't 
support it.

Costin

-- Jeanfrancois




them. I prefer the latter approach, also because of the multi-user use
case: if a single Tomcat installation (CATALINA_HOME) is used by
multiple users (each having their own CATALINA_BASE), then the former
approach does not work if each user has a different version of the JDK.


How about stopping support for that scenario?  I mean drop the
CATALINA_BASE versus CATALINA_HOME feature, (or set them to always equal
each other, if we want to leave them in the code base), and don't allow
users to share installations except by the user home directory valve.
The disk space benefits aren't worth it.  The central administration
benefits might be, but I wonder how many people use this.  Maybe an
informal survey on the user list is worth doing?

How about the other way around - stop support for the combined tomcat, 
and default to multi-user ( or multi-config ).

I would be very happy to see the server layout change to support 
multiple configurations.

Something like:
/bin
/lib - with manifest/properties file used to select what goes to 
common, server, shared :-)

/servers
/servers/all
/servers/minimal
With conf/ and webapps/ under each server.
Costin
-
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]