AW: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Hi I miss the following fix in there: Configuration: Bug No. Description 7520 Tomcat starts with title 3.3 instead of 3.3.1. Insert version string during build. Cheers, Hans -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 17. Mai 2002 07:15 An: [EMAIL PROTECTED] Betreff: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt billbarker02/05/16 22:15:29 Modified:.RELEASE-NOTES-3.3.2.txt Log: Document fix for #9165 Revision ChangesPath 1.7 +3 -1 jakarta-tomcat/RELEASE-NOTES-3.3.2.txt Index: RELEASE-NOTES-3.3.2.txt === RCS file: /home/cvs/jakarta-tomcat/RELEASE-NOTES-3.3.2.txt,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- RELEASE-NOTES-3.3.2.txt 30 Apr 2002 05:25:22 - 1.6 +++ RELEASE-NOTES-3.3.2.txt 17 May 2002 05:15:29 - 1.7 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-3.3.2.txt,v 1.6 2002/04/30 05:25:22 billbarker Exp $ +$Id: RELEASE-NOTES-3.3.2.txt,v 1.7 2002/05/17 05:15:29 billbarker Exp $ This document describes the changes that have been made since the @@ -36,6 +36,8 @@ 7770Fixed thread race problem in accessing the Hooks. 8092Fixed JSP source exposure proplem. + +9165Fix auto-detection of tomcat.install for certain 1.1.x JDKs. Jasper: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat-connectors/jk/conf workers2.properties
Good, now we've got a config example.
The works on autoconf stuff goes farther.
I could now generate build.properties from a
build.properties.autoconf (I keep .sample
untouched).
The autoconf is more modularized, thanks to
Doctor M4 Pier ;)
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 2:35 AM
To: [EMAIL PROTECTED]
Subject: cvs commit: jakarta-tomcat-connectors/jk/conf
workers2.properties
costin 02/05/16 17:35:18
Modified:jk/conf workers2.properties
Log:
Update the worker.properties.
We use a special property 'info' for comments, that allows
jk_config.c to
preserve them when saving. Any # comment will be lost.
I'll start working on docs and the jmx wrapper, most of the code
should be stable and working fine.
Revision ChangesPath
1.12 +67 -101
jakarta-tomcat-connectors/jk/conf/workers2.properties
Index: workers2.properties
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/conf/workers2.properties,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- workers2.properties 6 May 2002 22:48:56 - 1.11
+++ workers2.properties 17 May 2002 00:35:18 - 1.12
@@ -1,142 +1,108 @@
-# Comments will be lost when protocol-based config will be used
-# ( at least in the first version ). In a future version we'll save
-# the comments before every section and property and save ( maybe )
-
-# Global options ( in addition to the pre-defined fs, ps, java_home
-[config]
-## TOMCAT_HOME, CATALINA_HOME, JAVA_HOME and LD_LIBRARY_PATH
-# must be set for the jni worker to operate.
-debugEnv=0
-
-
-# Logger options. For apache2 only level can be set ( it
logs to apache's error.log )
[logger]
level=DEBUG
-# File property is not used on Apache2 or if a 'native'
logger is available
-# The Apache2 ( or native ) log file is used instead
-# For apache1 the file must be specified if you want logging.
-# file=logs/mod_jk.log
-[shm]
-file=${serverRoot}/logs/jk2.shm
-size=100
+[config:]
+file=${serverRoot}/conf/workers2.properties
+debug=0
+debugEnv=0
-[uriMap]
+[uriMap:]
+info=Maps the requests. Options: debug
debug=0
-[workerEnv]
+[shm:]
+info=Scoreboard. Required for reconfiguration and status
with multiprocess servers
+file=${serverRoot}/logs/jk2.shm
+size=100
debug=0
+disabled=0
- Channels
-# Each channel defines a communication mechanism to a
tomcat instance.
-# Each channel is associated with a ajp13:NAME, with the
same local name
+[workerEnv:]
+info=Global server options
+timing=1
+debug=0
+[lb:lb]
+info=Default load balancer.
+debug=0
-# Default channel
-#[channel.socket:localhost:8009]
-#lb_factor=1
-#tomcatId=localhost:8009
+[lb:lb_1]
+info=A second load balancer.
+debug=0
+[channel.socket:localhost:8009]
+info=Ajp13 forwarding over socket
+debug=0
+tomcatId=localhost:8009
-# Example additional socket channel. The location is in the
name ( URL-style
[channel.socket:localhost:8019]
+info=A second tomcat instance.
+debug=0
tomcatId=localhost:8019
lb_factor=1
-group=lb_1
group=lb
+group=lb_1
+disabled=0
+[channel.un:/opt/33/work/jk2.socket]
+info=A second channel connecting to localhost:8019 via unix socket
+tomcatId=localhost:8019
+lb_factor=1
+debug=0
-
-# Example unix socket.
-# XXX We must use an explicit setting to use substitution -
resolve this
-[channel.apr:${TOMCAT_HOME}/work/jk2.socket]
-tomcatId=localhost:8009
-lb_factor=0
-
-
-#
-# The JNI channel is enabled and configured automatically
-# if a VM is detected and tomcat started.
[channel.jni:jni]
+info=The jni channel, used if tomcat is started inprocess
- Workers
-# All non-ajp13 workers or workers with special configurations
-# There is no configuration for ajp13 workers - you just configure
-# channels
-
-# The status worker.
-[worker.status]
-
+[status:]
+info=Status worker, displays runtime informations
-# Requirements: libjvm.so MUST BE INCLUDED in
LD_LIBRARY_PATH for this
-# to work reliably and on all platforms. Same for other java libs.
-# java script is a good example, Sun needs it to start
java and we need it to.
-# JAVA_HOME and TOMCAT_HOME can be set as environment variables
-[vm]
-# That will work with both 3.x and 4.x.
+[vm:]
+info=Parameters used to load a JVM in the server process
OPT=-Djava.class.path=${TOMCAT_HOME}/bin/tomcat-jni.jar
How can I redirect only JSP pages to Tomcat?
Hello everybody! I have installed Tomcat 4 as servlet/JSP container fo IIS 5 but I haven't understood how to redirect to Tomcat only requests for JSP pages or servlets. I have found only the way to redirect entire sites but I would like to redirect only JSP pages and servlets and not html pages for example. Is it possible to redirect only a specified directory of a Web site? For example if I defined a site in /mysite folder is it possible to redirect to Tomcat only the request for the code present in /mysite/jsp ??? Thanks everybody in advance! Luca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9197] New: - Virtual Host not included in manager Application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9197. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9197 Virtual Host not included in manager Application Summary: Virtual Host not included in manager Application Product: Tomcat 4 Version: 4.0.4 Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Webapps:Administration AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If we have 2(or more) virtual hosts with the same context (ie. www.host.pl/some and www2.host.pl/some) is not possible to manage both contexts. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Conncurency issue with tomcat???
Hi Remy, 1. Sometimes we see that the same session is started in two threads concurrently. That, I can imagine it could happen. I don't think it would, but at least I can imagine there could be a bug somewhere with the manager which would cause this. May be!But this happens only when there is enough load on the server.If I run the same test whiout processing anything on the server then it works fine. 2. Sometimes one of the request for the user is processed two times. I don't think this can happen. (single request, being parsed once, and being processed twice) Ya I do happen..But do'nt know the real cause.I can even reproduce this...:-) You can test with Coyote 1.0b8 to see what happens. If it works fine with that, then it is a problem with the HTTP connector. If it still doesn't work (especially the second point, which would be a problem with the connector), then it's a bug with the client. I never heard Coyote before I would explore this..Thanx. Next is this step on my agenda.What about using a different JVM implementation(currently I am using one from the sun) You should also use some other HTTP clients to see what happens (commons HTTPClient, or the HTTP client Peter Lin mentioned). Ya I would try this today!! cheers Raj -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
i want to create a file by beans on tomcat server
i am try to create a file through jsp beans. and try to put into webapps/ROOT but my program create the file some where else. So, give me some suggession ,from that i can create a file at my location = asim pandey __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[Kin-Man] Jasper compiling wrong stuff in the wrong place...
When I touch the clsr.jsp jsp example with Tomcat 4.0.4 (and before), Jasper tries to compile also the bean associated with it (although it wasn't modified)... My only problem is that it tries to compile it in the /WEB-INF/ directory of the application (and it doesn't have permissions to write there), so, at the end, it's just throwing me a 500 error... Any clue on why Jasper should be trying to compile a .java into the WEB-INF/classes directory? I mean, even if it is javac trying to do that, giving it the -d parameter, it should always write anything in the work directory, right? Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: How can I redirect only JSP pages to Tomcat?
Which connector are you using, with mod_jk you can simply issue a JkMount /mysite/* ajp13 to forward all requests under /mysite to Tomcat. Regards. - Original Message - From: Luca Ventura [EMAIL PROTECTED] To: tomcat-user [EMAIL PROTECTED]; tomcat-dev [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:44 AM Subject: How can I redirect only JSP pages to Tomcat? Hello everybody! I have installed Tomcat 4 as servlet/JSP container fo IIS 5 but I haven't understood how to redirect to Tomcat only requests for JSP pages or servlets. I have found only the way to redirect entire sites but I would like to redirect only JSP pages and servlets and not html pages for example. Is it possible to redirect only a specified directory of a Web site? For example if I defined a site in /mysite folder is it possible to redirect to Tomcat only the request for the code present in /mysite/jsp ??? Thanks everybody in advance! Luca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: How can I redirect only JSP pages to Tomcat?
Ooops, should have read more carefully. The Tomcat-IIS howto contains the appropriate instructions on how to setup IIS to redirect a url to Tomcat. You need to look for this document under Tomcat 3.2.4 (should still be applicable to Tomcat 4 as you are using ajp12).. Regards. - Original Message - From: Arshad Mahmood [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED]; tomcat-user [EMAIL PROTECTED] Sent: Friday, May 17, 2002 10:30 AM Subject: Re: How can I redirect only JSP pages to Tomcat? Which connector are you using, with mod_jk you can simply issue a JkMount /mysite/* ajp13 to forward all requests under /mysite to Tomcat. Regards. - Original Message - From: Luca Ventura [EMAIL PROTECTED] To: tomcat-user [EMAIL PROTECTED]; tomcat-dev [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:44 AM Subject: How can I redirect only JSP pages to Tomcat? Hello everybody! I have installed Tomcat 4 as servlet/JSP container fo IIS 5 but I haven't understood how to redirect to Tomcat only requests for JSP pages or servlets. I have found only the way to redirect entire sites but I would like to redirect only JSP pages and servlets and not html pages for example. Is it possible to redirect only a specified directory of a Web site? For example if I defined a site in /mysite folder is it possible to redirect to Tomcat only the request for the code present in /mysite/jsp ??? Thanks everybody in advance! Luca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Where must I put the code of my application?
Hello! I have installed Tomcat 4 as servlet/jsp container and IIS as Web Server. I developed a Web application and I want to put it not in /webapps/examples folder of Tomcat but in another folder, for example /webapps/myproject. The problem is that when I try to connect to it IIS redirects corretly my request to Tomcat 4 (I have set the Web Server in this way) but Tomcat says The requested resource (/myproject/demo.jsp) is not available.. Why? I have read that I have to modify the file server.xml file when I develop a new application and add a new context...but in which way? Can someone give me a working example please? I tried to do it but unsuccessful :-( I hope someone can help me. Thanks in advance. Luca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
keith 02/05/17 06:03:46 Modified:.RELEASE-NOTES-3.3.2.txt Log: Make a note of the new Ant code Revision ChangesPath 1.8 +6 -1 jakarta-tomcat/RELEASE-NOTES-3.3.2.txt Index: RELEASE-NOTES-3.3.2.txt === RCS file: /home/cvs/jakarta-tomcat/RELEASE-NOTES-3.3.2.txt,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- RELEASE-NOTES-3.3.2.txt 17 May 2002 05:15:29 - 1.7 +++ RELEASE-NOTES-3.3.2.txt 17 May 2002 13:03:46 - 1.8 @@ -3,7 +3,7 @@ Release Notes = -$Id: RELEASE-NOTES-3.3.2.txt,v 1.7 2002/05/17 05:15:29 billbarker Exp $ +$Id: RELEASE-NOTES-3.3.2.txt,v 1.8 2002/05/17 13:03:46 keith Exp $ This document describes the changes that have been made since the @@ -25,6 +25,11 @@ (Re-) Open the log files with append, so that log rotation can be configured to be other than daily. + + Package an Ant compiler adapter that compiles JSPs with the correct + naming convention and an Ant task which creates .ver files. These + tasks allow the Tomcat work directory to be pre-populated with + compiled JSPs. Server: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
(Re-) Open the log files with append, so that log rotation can be configured to be other than daily. + + Package an Ant compiler adapter that compiles JSPs with the correct + naming convention and an Ant task which creates .ver files. These + tasks allow the Tomcat work directory to be pre-populated with + compiled JSPs. Great, Do you have a task parm with the work directory location ? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
R: How can I redirect only JSP pages to Tomcat?
Maybe I solved the problemI modified uriworkermap.properties in this way: # # Default worker to be used through our mappings # default.worker=ajp13 # # Sites to be redirected to Tomcat # /examples/*.jsp=$(default.worker) I obtained the effect to redirect to Tomcat only the .jsp pages of examples application. I hope this can help somebody else. Regards, Luca -Messaggio originale- Da: Arshad Mahmood [mailto:[EMAIL PROTECTED]] Inviato: venerdì 17 maggio 2002 11.51 A: Tomcat Developers List; tomcat-user Oggetto: Re: How can I redirect only JSP pages to Tomcat? Ooops, should have read more carefully. The Tomcat-IIS howto contains the appropriate instructions on how to setup IIS to redirect a url to Tomcat. You need to look for this document under Tomcat 3.2.4 (should still be applicable to Tomcat 4 as you are using ajp12).. Regards. - Original Message - From: Arshad Mahmood [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED]; tomcat-user [EMAIL PROTECTED] Sent: Friday, May 17, 2002 10:30 AM Subject: Re: How can I redirect only JSP pages to Tomcat? Which connector are you using, with mod_jk you can simply issue a JkMount /mysite/* ajp13 to forward all requests under /mysite to Tomcat. Regards. - Original Message - From: Luca Ventura [EMAIL PROTECTED] To: tomcat-user [EMAIL PROTECTED]; tomcat-dev [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:44 AM Subject: How can I redirect only JSP pages to Tomcat? Hello everybody! I have installed Tomcat 4 as servlet/JSP container fo IIS 5 but I haven't understood how to redirect to Tomcat only requests for JSP pages or servlets. I have found only the way to redirect entire sites but I would like to redirect only JSP pages and servlets and not html pages for example. Is it possible to redirect only a specified directory of a Web site? For example if I defined a site in /mysite folder is it possible to redirect to Tomcat only the request for the code present in /mysite/jsp ??? Thanks everybody in advance! Luca -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Yes, put build/tomcat/ant/tomcat-ant.jar in your classpath
and do something like:
property name=jspc value=org.apache.tomcat.ant.Tomcat3Precompiler /
taskdef resource=ant.properties /
target name=jsp
jspc srcdir=/foo/jsps
destdir=tomcat_work_path/webapps/foo
uriroot=/foo/jsps compiler=${jspc}
include name=**/*.jsp /
classpath refid=appropriate_classpath /
/jspc
javac srcdir=tomcat_work_path/webapps/foo
classpath refid=another_appropriate_classpath /
/javac
jspversion srcdir=tomcat_work_path/webapps/foo /
!-- one can also delete the .javas from the work dir if desired --
/target
The 'Tomcat3Precompiler' wraps the standards jspc, but
mangles the names with a version number (foo_1).
The 'jspversion' task a creates .ver file for every class
file of the form name_number.class
Keith
| -Original Message-
| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 8:06 AM
| To: Tomcat Developers List
| Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
|
|
| (Re-) Open the log files with append, so that log
| rotation can
| be configured to be other than daily.
| +
| + Package an Ant compiler adapter that compiles JSPs
| with the correct
| + naming convention and an Ant task which creates
| .ver files. These
| + tasks allow the Tomcat work directory to be
| pre-populated with
| + compiled JSPs.
|
|
| Great, Do you have a task parm with the work directory location ?
|
| --
| To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
| For additional commands, e-mail: mailto:[EMAIL PROTECTED]
|
|
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Did you have a preliminary version available ?
-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 4:22 PM
To: Tomcat Developers List
Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Yes, put build/tomcat/ant/tomcat-ant.jar in your classpath
and do something like:
property name=jspc
value=org.apache.tomcat.ant.Tomcat3Precompiler /
taskdef resource=ant.properties /
target name=jsp
jspc srcdir=/foo/jsps
destdir=tomcat_work_path/webapps/foo
uriroot=/foo/jsps compiler=${jspc}
include name=**/*.jsp /
classpath refid=appropriate_classpath /
/jspc
javac srcdir=tomcat_work_path/webapps/foo
classpath refid=another_appropriate_classpath /
/javac
jspversion srcdir=tomcat_work_path/webapps/foo /
!-- one can also delete the .javas from the work dir if desired --
/target
The 'Tomcat3Precompiler' wraps the standards jspc, but
mangles the names with a version number (foo_1).
The 'jspversion' task a creates .ver file for every class
file of the form name_number.class
Keith
| -Original Message-
| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 8:06 AM
| To: Tomcat Developers List
| Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
|
|
| (Re-) Open the log files with append, so that log
| rotation can
| be configured to be other than daily.
| +
| + Package an Ant compiler adapter that compiles JSPs
| with the correct
| + naming convention and an Ant task which creates
| .ver files. These
| + tasks allow the Tomcat work directory to be
| pre-populated with
| + compiled JSPs.
|
|
| Great, Do you have a task parm with the work directory location ?
|
| --
| To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
| For additional commands, e-mail: mailto:[EMAIL PROTECTED]
|
|
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
It's already checked in to Tomcat, so the jar is created when you do a build. Keith | -Original Message- | From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 8:26 AM | To: Tomcat Developers List | Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt | | | Did you have a preliminary version available ? | | - | Henri Gomez ___[_] | EMAIL : [EMAIL PROTECTED](. .) | PGP KEY : 697ECEDD...oOOo..(_)..oOOo... | PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Communication cross classloaders
Is there anyway for one webapplication to get visablity to classes from a class loader in another web application? Thanks, John Trollinger -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Excellent news ;) When is planned 3.3.2 release ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Keith Wannamaker [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 4:41 PM To: Tomcat Developers List Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt It's already checked in to Tomcat, so the jar is created when you do a build. Keith | -Original Message- | From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 8:26 AM | To: Tomcat Developers List | Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt | | | Did you have a preliminary version available ? | | - | Henri Gomez ___[_] | EMAIL : [EMAIL PROTECTED](. .) | PGP KEY : 697ECEDD...oOOo..(_)..oOOo... | PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9120] - JSPs hang for a short period
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9120. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9120 JSPs hang for a short period --- Additional Comments From [EMAIL PROTECTED] 2002-05-17 13:55 --- OK, I believe this to be the same issue as in bug 8290. I did not test 4.1.x for the fix, but rather did something I wanted to do for a long time: I wrote a standalone JSP compiler capable of using taglibs to precompile all the JSPs. As I took care to not overuse try .. catch .. finally blocks, the issue went away. Thanks for pointing me into the right direction! -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Kin-Man] Jasper compiling wrong stuff in the wrong place...
Pier Fumagalli wrote: When I touch the clsr.jsp jsp example with Tomcat 4.0.4 (and before), Jasper tries to compile also the bean associated with it (although it wasn't modified)... My only problem is that it tries to compile it in the /WEB-INF/ directory of the application (and it doesn't have permissions to write there), so, at the end, it's just throwing me a 500 error... Any clue on why Jasper should be trying to compile a .java into the WEB-INF/classes directory? I mean, even if it is javac trying to do that, giving it the -d parameter, it should always write anything in the work directory, right? Should not it write the *.java files in tmpdir? Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
ant tools for 3.3 and dtomcat3/rc script
Would it be possible to take Keith's tomcat3 JSP precompiler and add it as an option to dtomcat3 (and rc script for the RPM)? What I'm thinking of is being able to run: /etc/rc.d/init.d/tomcat3 precompile /etc/rc.d/init.d/tomcat3 start Henri you've probably already thought about this for the 3.3.2 release RPM; were you planning on trying to implement? Jason Corley, UNIX/Linux System Administrator TogetherSoft Corporation 900 Main Campus Drive, Suite 500 Raleigh, NC 27606 o: 1-919-833-5550 x1531, m: 1-919-795-3703 [EMAIL PROTECTED] TogetherSoft's mission is improving the ways people work together. Our flagship product, Together ControlCenter, is the Model-Build-Deploy Platform. http://www.togethersoft.com/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: ant tools for 3.3 and dtomcat3/rc script
No, for a Tomcat which has already been installed, you should use the JspC tomcat option to precompile JSPs. What I did is to create an Ant task with the same functionality as the already-present JspC option, for use in build environments. Keith | -Original Message- | From: Jason Corley [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 9:26 AM | To: [EMAIL PROTECTED] | Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] | Subject: ant tools for 3.3 and dtomcat3/rc script | | | | Would it be possible to take Keith's tomcat3 JSP precompiler and add | it as an option to dtomcat3 (and rc script for the RPM)? What I'm | thinking of is being able to run: | /etc/rc.d/init.d/tomcat3 precompile | /etc/rc.d/init.d/tomcat3 start | Henri you've probably already thought about this for the 3.3.2 | release RPM; were you planning on trying to implement? | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: ant tools for 3.3 and dtomcat3/rc script
No, for a Tomcat which has already been installed, you should use the JspC tomcat option to precompile JSPs. What I did is to create an Ant task with the same functionality as the already-present JspC option, for use in build environments. From my experience in production deployement having jspc in ant is much better than just using tomcat recompile. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: ant tools for 3.3 and dtomcat3/rc script
Hmm, perhaps I'm a little confused (not that difficult to believe :-) but I thought jspc didn't create files with the proper naming scheme for tomcat. I thought the ant task was a wrapper around jspc that solves that problem (along with the other ant task you posted that creates the appropriate .class/.ver files). Jason -Original Message- From: Keith Wannamaker [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 11:36 AM To: Tomcat Developers List Subject: RE: ant tools for 3.3 and dtomcat3/rc script No, for a Tomcat which has already been installed, you should use the JspC tomcat option to precompile JSPs. What I did is to create an Ant task with the same functionality as the already-present JspC option, for use in build environments. Keith | -Original Message- | From: Jason Corley [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 9:26 AM | To: [EMAIL PROTECTED] | Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] | Subject: ant tools for 3.3 and dtomcat3/rc script | | | | Would it be possible to take Keith's tomcat3 JSP precompiler and add | it as an option to dtomcat3 (and rc script for the RPM)? What I'm | thinking of is being able to run: | /etc/rc.d/init.d/tomcat3 precompile | /etc/rc.d/init.d/tomcat3 start | Henri you've probably already thought about this for the 3.3.2 | release RPM; were you planning on trying to implement? | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: ant tools for 3.3 and dtomcat3/rc script
I agree that's why I wrote the task :-) Maybe I misuderstood Jason,.. thought he wanted to use the ant tool post-installation-- tomcat recompile would be a better option in that case, IMO. But, of course, the ant tool can be used, if ant is available. Keith | -Original Message- | From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 9:47 AM | To: Tomcat Developers List | Subject: RE: ant tools for 3.3 and dtomcat3/rc script | | | No, for a Tomcat which has already been installed, | you should use the JspC tomcat option to precompile | JSPs. | | What I did is to create an Ant task with the same | functionality as the already-present JspC option, | for use in build environments. | | From my experience in production deployement having | jspc in ant is much better than just using tomcat recompile. | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomca 4.1.2 startup problem
Hello! I am trying to start and test the latest tomcat 4.1.2, but I get the following exception in loading the admin web app. 2002-05-17 16:56:29 ContextConfig[/admin] Exception processing JAR at resource path /WEB-INF/lib/struts.jar javax.servlet.ServletException: Exception processing JAR at resource path /WEB-INF/lib/struts.jar at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java: 913) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:851 ) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:642) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.j ava:243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3445 ) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja va:821) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeplo yer.java:528) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:2 16) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:830) at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1536) at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500) at org.apache.crimson.parser.Parser2.parse(Parser2.java:305) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442) at org.apache.commons.digester.Digester.parse(Digester.java:1302) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeploy er.java:335) at org.apache.catalina.core.StandardHost.install(StandardHost.java:804) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java :452) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:409) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:882) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:36 8) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu pport.java:166) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1198) at org.apache.catalina.core.StandardHost.start(StandardHost.java:739) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1190) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:499) at org.apache.catalina.core.StandardServer.start(StandardServer.java:707) at org.apache.catalina.startup.Catalina.start(Catalina.java:504) at org.apache.catalina.startup.Catalina.execute(Catalina.java:399) at org.apache.catalina.startup.Catalina.process(Catalina.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) - Root Cause - java.io.IOException: The system cannot find the path specified at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1294) at java.io.File.createTempFile(File.java:1382) at java.io.File.createTempFile(File.java:1419) at sun.net.www.protocol.jar.URLJarFile$1.run(URLJarFile.java:169) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.jar.URLJarFile.retrieve(URLJarFile.java:164) at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:42) at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:78) at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java: 85) at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.ja va:69) at org.apache.catalina.startup.ContextConfig.tldScanJar(ContextConfig.java: 889) at org.apache.catalina.startup.ContextConfig.tldScan(ContextConfig.java:851 ) at
RE: ant tools for 3.3 and dtomcat3/rc script
You've got it. I thought you were talking post-install, but, again, if Ant's available you can use the task whenever you wanted to. Keith | -Original Message- | From: Jason Corley [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 9:50 AM | To: Tomcat Developers List | Subject: RE: ant tools for 3.3 and dtomcat3/rc script | | | | Hmm, perhaps I'm a little confused (not that difficult to believe :-) | but I thought jspc didn't create files with the proper naming scheme | for tomcat. I thought the ant task was a wrapper around jspc that | solves that problem (along with the other ant task you posted that | creates the appropriate .class/.ver files). | Jason | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
(Known) Problems with WebappClassLoader
Hi all, I have come across two problems with the o.a.c.loader.WebappClassLoader (TC 4.03) that are currently major obstacles for me: 1) Sealed jars are not handled correctly. Cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8611. Is there any chance of the fix being ported to 4.0x? (I am not likely to be able to move to 4.1x for quite some time. Under no circumstances before the official release.) 2) Class.getSigners () returns null instead of the signers. This is probably http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7578. I have verified that this is a problem with WebappClassLoader by removing all overridden methods of URLClassLoader and adding the jars from WEB-INF/lib with super.addURL in a constructor. This crippled version loads the signers correctly. Any fix at all? (The bug-report from 2002-03-28 has had no response so far.) Regards, Michael Eriksson -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 4023] - exceptions that terminate engine should be saved in a log
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4023. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4023 exceptions that terminate engine should be saved in a log [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2002-05-17 15:56 --- This still happens to me in version 4.1.0 alpha. (Windows 2000) When Tomcat is started, a stack trace is displayed and then the console window closes, before you get a chance to read the error message. The error is not logged. (I had to modify the startup script to be able to read the output.) The cause was a Context element in server.xml that was closed twice, like this: context / stuff /context -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
jk/native2 autoconf
Hi to all, I'm still working on cleaning the jk2 autoconf and I plan to drop (for now) the static build for Apache 1.3/2.0. This add unneeded complexity but the code will moved in a m4 macro file (jk_static_apache.m4). Thanks for your feedback - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9204] New: - Can't run Tomcat on IBM JRE 1.3.1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9204. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9204 Can't run Tomcat on IBM JRE 1.3.1 Summary: Can't run Tomcat on IBM JRE 1.3.1 Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Catalina won't run on any IBM JREs from 1.3.1 and beyond. This is because the IBM JREs throw a ZIPException when you try to create a ZipFile pointing to an invalid location, while earlier IBM JREs and Sun's JREs do not. This occurs during the bootstrapping, when a /classes directory is added to the classloader's path. Since the exception is not caught, the server fails to start. See the stack trace below. This exception does seem fairly reasonable, since it is not pointing to a zip file. Can the StandardClassLoader catch the exception as it tries to add each path to the repository, or verify that it is a zip file before it tried to load it? java.util.zip.ZipException: Access is denied at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.init(ZipFile.java:127) at java.util.jar.JarFile.init(JarFile.java:138) at java.util.jar.JarFile.init(JarFile.java:80) at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal (StandardClassLoader.java:1216) at org.apache.catalina.loader.StandardClassLoader.init (StandardClassLoader.java:200) at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader (ClassLoaderFactory.java:261) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:138) Bootstrap: Class loader creation threw exception java.lang.IllegalArgumentException: addRepositoryInternal: java.util.zip.ZipException: Access is denied at org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal (StandardClassLoader.java:1246) at org.apache.catalina.loader.StandardClassLoader.init (StandardClassLoader.java:200) at org.apache.catalina.startup.ClassLoaderFactory.createClassLoader (ClassLoaderFactory.java:261) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:138) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
DO NOT REPLY [Bug 9197] - Virtual Host not included in manager Application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9197. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9197 Virtual Host not included in manager Application [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME Summary|Virtual Host not included in|Virtual Host not included in |manager Application |manager Application --- Additional Comments From [EMAIL PROTECTED] 2002-05-17 16:24 --- You need to have one manager webapp per host. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt
Hi Henri, I haven't thought that far. I'm pretty swamped at the moment. Soon I expect to have nightly builds working on a regular basis. Hopefully, in the not too distant future I can review what is appropriate to do and submit a plan. Cheers, Larry -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 9:52 AM To: Tomcat Developers List Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt Excellent news ;) When is planned 3.3.2 release ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Keith Wannamaker [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 4:41 PM To: Tomcat Developers List Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt It's already checked in to Tomcat, so the jar is created when you do a build. Keith | -Original Message- | From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] | Sent: Friday, May 17, 2002 8:26 AM | To: Tomcat Developers List | Subject: RE: cvs commit: jakarta-tomcat RELEASE-NOTES-3.3.2.txt | | | Did you have a preliminary version available ? | | - | Henri Gomez ___[_] | EMAIL : [EMAIL PROTECTED](. .) | PGP KEY : 697ECEDD...oOOo..(_)..oOOo... | PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 | -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-dev- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: (Known) Problems with WebappClassLoader
1) Sealed jars are not handled correctly. Cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8611. I'm inclined to port the latest CL changes to 4.0.x now, but it will be at the expense of an addtional TC 4.0.4 beta. 2) Class.getSigners () returns null instead of the signers. This is probably http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7578. Any fix at all? (The bug-report from 2002-03-28 has had no response so far.) I'd like this bug to be fixed. I don't know why it doesn't work, and I didn't try to fix it yet. If you have some time, maybe you can look into it ? Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 4.0.3, WebdavServlet and Konqueror
Hello, I'm having a problem Tomcat's built-in WebdavServlet /webdav from Konqueror. basically, konq is just hanging trying to hit the base /webdav URL. I stepped through the WebdavServlet code and noticed it was hanging trying to parse XML data over a call to req.getInputStream(). My theory is that the input stream is not returning EOF. I uncommented the RequestDumperValve and notice the following: The initial /webdav request has the following characterstics: 1. No Content-Length header 2. HTTP/1.1 3. No Connection header It almost looks as though Konq is NOT closing the connection after the request (when maybe it should?) Is the InputStream returned just assuming since it has no persistent connection indication and no content-length that socket-close means EOF. Thanks for any help, russ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Switching javac for jasper 2
See below. Date: Thu, 16 May 2002 14:07:36 -0700 (PDT) From: [EMAIL PROTECTED] Subject: Re: Switching javac for jasper 2 X-X-Sender: [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED], Kin-Man Chung [EMAIL PROTECTED] MIME-version: 1.0 Delivered-to: mailing list [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Authentication-warning: costinm.sfo.covalent.net: costin owned process doing -bs List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Id: Tomcat Developers List tomcat-dev.jakarta.apache.org com.sun.tools.javac.Main doesn't seem to be in JDK1.2.x, and that's the target platform, isn't it ? I believe for 4.1.x, it should be 1.3.1 and above. Like I said, 1.2 javac is currently unsupported and deprecated in 1.3 and 1.4, and contain bugs that are hard to work around. Can't image people currently using jdk1.2 wouldn't want to upgrade. I think the best solution for javac is to just bundle ant.jar and use it programmatically ( i.e. new Javac(), etc ). The introspection and hacks required to support multiple compilers are just too ugly - and they already have good solutions in ant. I'll look into that. But even if ant.jar is used programmatically, eventually it still start another process to invoke javac, right? Plus it's yet another jar to be bundled with tomcat; do we really want that? What do others think? We already have enough complexity to support jikes. Costin - Kin-man On Thu, 16 May 2002, Kin-Man Chung wrote: Tomcat has been using sun.tools.javac.Main as the default java compiler for compiling the java files generated by Jasper. This compiler is essentially a JDK1.2 compiler, current deprecated and unsupported. The warning message Note: sun.tools.javac.Main has been deprecated is probably familiar to a lot of people. The compiler to use is com.sun.tools.javac.Main. The only thing that prevented us from switching over to this one is the fact that it does not allow a PrintWriter to be specified for error messages that it may produce, which essentially force tomcat to synchronize all compilation processes, a big performance hit. I believe that J2sdk1.4.1, currently targetted for FCS in fall 2002, will provide a javac.Main which allows us to specify a PrintWriter, essentially removing the need for synchronizing the compilation. We definitely will use that when it becomes available. However, I recently runs into problem with sun.tools.javac.Main which surfaces when a jsp page gets large. Sometimes it produces bogus errors, and somteitmes it even produces bad class files that cannot be loaded by VM. I am contemplating switching over to using com.sun.tools.javac.Main now, for 4.1 (jasper2). If there are objections, please let me know. BTW, anyone know the best way to capture javac error messages written to standard err stream? I want to avoid calling Runtime.getRuntime().exec if there is a way. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Kin-Man] Jasper compiling wrong stuff in the wrong place...
Pier, Long time no see/talk/eamil. How are you? Haven't seen that before, and no idea why it's so. You'll need to give me a test case. Why aren't you using jasper2 instead? Glenn's recompilation stuff works great! - Kin-man Date: Fri, 17 May 2002 11:54:38 +0100 From: Pier Fumagalli [EMAIL PROTECTED] Subject: [Kin-Man] Jasper compiling wrong stuff in the wrong place... To: Tomcat Developers List [EMAIL PROTECTED] MIME-version: 1.0 Content-transfer-encoding: 7bit Delivered-to: mailing list [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm User-Agent: Microsoft-Entourage/10.0.0.1331 X-Antivirus: nagoya (v4198 created Apr 24 2002) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N List-Post: mailto:[EMAIL PROTECTED] List-Subscribe: mailto:[EMAIL PROTECTED] List-Unsubscribe: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Id: Tomcat Developers List tomcat-dev.jakarta.apache.org When I touch the clsr.jsp jsp example with Tomcat 4.0.4 (and before), Jasper tries to compile also the bean associated with it (although it wasn't modified)... My only problem is that it tries to compile it in the /WEB-INF/ directory of the application (and it doesn't have permissions to write there), so, at the end, it's just throwing me a 500 error... Any clue on why Jasper should be trying to compile a .java into the WEB-INF/classes directory? I mean, even if it is javac trying to do that, giving it the -d parameter, it should always write anything in the work directory, right? Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Switching javac for jasper 2
On Fri, 17 May 2002, Kin-Man Chung wrote: com.sun.tools.javac.Main doesn't seem to be in JDK1.2.x, and that's the target platform, isn't it ? I believe for 4.1.x, it should be 1.3.1 and above. Like I said, 1.2 javac is currently unsupported and deprecated in 1.3 and 1.4, and contain bugs that are hard to work around. Can't image people currently using jdk1.2 wouldn't want to upgrade. I believe the target platform is 1.2, not 1.3.1 ( at least acording to RUNNING.txt ). I don't remember any vote that changed that. There are still platforms without a JDK1.3.1 or above. Most free VMs are still strugling to support JDK1.2 fully ( gcc or kaffe for example ). Many productions sites can't upgrade at will. I think the best solution for javac is to just bundle ant.jar and use it programmatically ( i.e. new Javac(), etc ). The introspection and hacks required to support multiple compilers are just too ugly - and they already have good solutions in ant. I'll look into that. But even if ant.jar is used programmatically, eventually it still start another process to invoke javac, right? Plus it's yet another jar to be bundled with tomcat; do we really want that? Ant doesn't start another process to invoke javac unless you explicitely ask for it ( by fork=true ) or use jikes or another native compiler. Between including 'another jar' that supports most javac compilers and changing the code to support only JDK1.3.1 and JDK1.4 compilers - I think the choice is pretty simple. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory Constants.java DbcpDataSourceFactory.java
remm02/05/17 10:39:27 Modified:catalina/src/share/org/apache/naming/factory Constants.java Removed: catalina/src/share/org/apache/naming/factory DbcpDataSourceFactory.java Log: - As suggested by Craig, use the DBCP factory from the commons package. This avoids code duplication. - Glenn, feel free to complain about this commit ;-) I couldn't find a problem with what Craig suggested. Revision ChangesPath 1.5 +4 -4 jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory/Constants.java Index: Constants.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory/Constants.java,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- Constants.java24 Feb 2002 05:09:58 - 1.4 +++ Constants.java17 May 2002 17:39:27 - 1.5 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory/Constants.java,v 1.4 2002/02/24 05:09:58 remm Exp $ - * $Revision: 1.4 $ - * $Date: 2002/02/24 05:09:58 $ + * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/naming/factory/Constants.java,v 1.5 2002/05/17 17:39:27 remm Exp $ + * $Revision: 1.5 $ + * $Date: 2002/05/17 17:39:27 $ * * * @@ -89,7 +89,7 @@ Package + .EjbFactory; public static final String DBCP_DATASOURCE_FACTORY = -Package + .DbcpDataSourceFactory; +org.apache.commons.dbcp.BasicDataSourceFactory; public static final String TYREX_DATASOURCE_FACTORY = Package + .TyrexDataSourceFactory; -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Kin-Man] Jasper compiling wrong stuff in the wrong place...
Kin-Man Chung [EMAIL PROTECTED] wrote: Long time no see/talk/eamil. How are you? I'm on this mailing list posting almost every day :) Haven't seen that before, and no idea why it's so. You'll need to give me a test case. Test case: touch $CATALINA_HOME/webapps/examples/jsp/colors/colrs.jsp So that Jasper will have to recompile it, and it will try (the first time) to recompile also: $CATALINA_HOME/webapps/examples/WEB-INF/classes/colors/ColorGameBean.java But putting its class back into $CATALINA_HOME/webapps/examples/WEB-INF/classes/colors/ColorGameBean.class Not into $CATALINA_HOME/work/.. That's pretty nasty, as the user under which the Tomcat process is running is not (and can not) write into $CATALINA_HOME/webapps/. (call it security) Why aren't you using jasper2 instead? Glenn's recompilation stuff works great! Because I'm in production, and I don't trust the code (yet)... I have to serve an average of 400/500 thousand JSP pages a day out of that server, and seriously, I'm not going to run my entire site over a JSP compiler which came out less than one month ago :) Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Kin-Man] Jasper compiling wrong stuff in the wrong place...
Kin-Man Chung [EMAIL PROTECTED] wrote: Long time no see/talk/eamil. How are you? I'm on this mailing list posting almost every day :) Haven't seen that before, and no idea why it's so. You'll need to give me a test case. Test case: touch $CATALINA_HOME/webapps/examples/jsp/colors/colrs.jsp So that Jasper will have to recompile it, and it will try (the first time) to recompile also: $CATALINA_HOME/webapps/examples/WEB-INF/classes/colors/ColorGameBean.java But putting its class back into $CATALINA_HOME/webapps/examples/WEB-INF/classes/colors/ColorGameBean.class Not into $CATALINA_HOME/work/.. That's pretty nasty, as the user under which the Tomcat process is running is not (and can not) write into $CATALINA_HOME/webapps/. (call it security) Why aren't you using jasper2 instead? Glenn's recompilation stuff works great! Because I'm in production, and I don't trust the code (yet)... I have to serve an average of 400/500 thousand JSP pages a day out of that server, and seriously, I'm not going to run my entire site over a JSP compiler which came out less than one month ago :) Thanks for the report Pier. I had been wondering for AGES why the CL would reload the webapp randomly after accessing a JSP, telling that a bean class had been modified. I couldn't find a reason why it was a bug (the logging I added to investigate this displayed different dates which didn't appear bogus), but I failed to undestand why it happened. Jasper 2 has some big advantages in production, like being able to disable reloading checks altogether, as well as various other optimizations, which makes the JSP overhead over a servlet almost zero. Obviously, the fix for bug 8290 is also a huge improvement if you're using a lot of tags. Lately, I have found some incompatibilities with JSTL (their examples WAR doesn't really like Jasper 2); the admin webapp (big Struts webapp which is painfully slow with Jasper 1 - and that's with one user on an Athlon XP 1700+ ;-) ) and Watchdog both run very well, though. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[Coyote] 1.0 Final release ?
I think there are no remaining issues with the core API, the TC 4 adapter and the HTTP/1.1 protocol handler. The last issue that needed to be addressed was the incompatibility with the daemon and some small behavior differences with the old HTTP/1.1 connector. I'd like to get this release out before releasing 4.0.4 Final which would include it. 4.1.x could try to stick to Coyote 1.0 for some time, also. I don't know about the status of the Java parts of JK 2 and the Tomcat 3 adapter. I didn't see big changes there, so I assume they're ok. Please let me know. I'll start the final release process with a RC 1 release. ballot [ ] +1 [ ] -1 /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Switching javac for jasper 2
On Fri, 17 May 2002, Kin-Man Chung wrote: I think the best solution for javac is to just bundle ant.jar and use it programmatically ( i.e. new Javac(), etc ). The introspection and hacks required to support multiple compilers are just too ugly - and they already have good solutions in ant. I'll look into that. But even if ant.jar is used programmatically, eventually it still start another process to invoke javac, right? Plus it's yet another jar to be bundled with tomcat; do we really want that? Ant doesn't start another process to invoke javac unless you explicitely ask for it ( by fork=true ) or use jikes or another native compiler. Between including 'another jar' that supports most javac compilers and changing the code to support only JDK1.3.1 and JDK1.4 compilers - I think the choice is pretty simple. I like Costin's solution. Using an abstraction layer for the compiler looks to me like a really good idea, as it would allow maximum platform support while removing a good chunk of the complexity in Jasper. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Coyote] 1.0 Final release ?
On Fri, 17 May 2002, Remy Maucherat wrote: I think there are no remaining issues with the core API, the TC 4 adapter and the HTTP/1.1 protocol handler. The last issue that needed to be addressed was the incompatibility with the daemon and some small behavior differences with the old HTTP/1.1 connector. I'd like to get this release out before releasing 4.0.4 Final which would include it. 4.1.x could try to stick to Coyote 1.0 for some time, also. I don't know about the status of the Java parts of JK 2 and the Tomcat 3 adapter. I didn't see big changes there, so I assume they're ok. Please let me know. I'll start the final release process with a RC 1 release. +1 I have one small change - adding a new ActionCode for CLIENT_FLUSH - to notify jk layer that flush() was called explicitely by the user. It doesn't change any of the existing code, just add a field and a method. Let me know if I can quickly check it in. Costin ballot [ ] +1 [ ] -1 /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Coyote] 1.0 Final release ?
I have one small change - adding a new ActionCode for CLIENT_FLUSH - to notify jk layer that flush() was called explicitely by the user. It doesn't change any of the existing code, just add a field and a method. Let me know if I can quickly check it in. No problem, go ahead. After 1.0, we can refactor the ActionCode/Hook, and also remove the deprecated interfaces. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PATCH] Re: [PROPOSAL] Modification of the code generated byJasper2
Denis,
Glad that you agree. About the timing for the patch, I think now is OK.
Jasper 2 is fairly stable and the only bug that may interact with our
fix is 4964 and I already have a fix for it; but am hold off committing
it because struts depends on this bug, and my fix would break it! :-(
Now down to details. :-)
Since a popBody is always followed by a release, it would be simpler
to have each stack element consists of two entries:
1. the tag, and
2. the state: 0 - release only
1 - popBody and release.
That way we only need to do one push per tag handler. Of course, all
tags would get state 0 first, and some of them would change to state 1
later.
For efficiency we can use two separate arrays for implementing the
stack: one for holding the tags, the other for keeping track of the state.
The code generated would be like:
stackIndex = -1;
...
++stackIndex; // Entering a tag
MyTag mt = new MyTag();
tagStack[stackIndex] = mt;
stateStack[stackIndex] = 0; // state 0
if (_jspx_eval_myTag != EVAL_BODY_INCLUDE) {
stateStack[stackIndex] = 1;
...
}
...
--currentIndex; // Exiting a tag
This way, the size of the stack is the maximum number of nesting of the
tags, which should much smaller than the number of tags in the page.
Such information is easy to collect in Jasper 2, which can be
done either in Validator.java, or we have a separate pass whose sole
purpose is to collect info such as this.
- Kin-man
Date: Thu, 16 May 2002 23:16:15 -0400 (EDT)
From: Denis Benoit [EMAIL PROTECTED]
Subject: Re: [PATCH] Re: [PROPOSAL] Modification of the code generated by
Jasper2
To: Kin-Man Chung [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
MIME-version: 1.0
Now you mentioned the use of an array to hold tag objects, I have
another idea. Why don't we use a stack to simulate the runtime state?
Each stack entry would have a tag object and a state. State 0 means
call release() only, and state 1 means call popBody() and then release().
We push an entry onto the stack when we enter a tag body, and pop it
when we exit the body. We change the state on the stack top when we do
a pushBody. When an exception is thrown, we just need to pop the entries
from the stack to decide what to do. For efficiency, we can use an
array to simulate the stack, and its size would be the number of nesting
of the tags.
I think this is quite simple and faster. What do you think?
Yes! Yes!
In my last e-mail, I mentionned that there is only two actions that we need
to do in the finallies. This is:
1) do a release() on a Tag
2) do a popBody()
We could push on the stack in this order:
Either:
1- A tag
2- The Action identifier for release (a Constant representing
release())
Or:
1- The Action identifier for popBody (a Constant representing
popBody())
Now the finallies code look like this:
While stack is not empty:
Pop an action
If action is RELEASE then
pop a Tag
Do a Tag.release()
Otherwise /* Action is assumed to be POPBODY */
do a popBody()
So the finallies could very well be inlined because it would be short.
The other modification would be when we begin the pseudo finally block. At
that point we have to remove from the stack what was pushed at the begin of
the pseudo try block. If we do a popBody() in the finally, then we must
pop one element. If we do a release(), we will pop two elements.
In the event of an exception anywhere in the page, the stack would contain
only the actions that must be performed in the order to be performed. Your
solution is clean, efficient and simple!
The stack could very well be an Object[], but if we must rely on arrayCopy(),
to extend the array periodically, would it be really much more efficient than
using a plain Stack object? After all, this is the way a Stack is implemented
by the JDK itself. On the other hand, we know the lower and upper bounds of
the
stack. Each tag will need to be pushed at least once for the release() and
the action identifier will need to be pushed too (so we push two times the
number of Tags in the page). And maybe we will need to push once more for a
popBody() (so one more time to indicate the action).
This would give us an array of size 2 to 3 times the number of tags in the
page.
I think it would be more efficient to allocate an array of 3 times the number
of
tags and save us the occasional overhead of arrayCopy() calls to extend the
array.
Now, I see two ways to determine the size of the array. Either, after
generating the _jsp_service() method, the class Generator could produce the
declaration of
Re: [Coyote] 1.0 Final release ?
ballot [X] +1 [ ] -1 /ballot Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Kin-Man] Jasper compiling wrong stuff in the wrong place...
Remy Maucherat [EMAIL PROTECTED] wrote: Thanks for the report Pier. I had been wondering for AGES why the CL would reload the webapp randomly after accessing a JSP, telling that a bean class had been modified. I couldn't find a reason why it was a bug (the logging I added to investigate this displayed different dates which didn't appear bogus), but I failed to undestand why it happened. Yeah, I wonder why noone actually noticed this before... Am I the only idiot using TC4 in a secure production environment? (Meaning, chrooted JVM and suid execution, with access only to the work directory)? Jasper 2 has some big advantages in production, like being able to disable reloading checks altogether, as well as various other optimizations, which makes the JSP overhead over a servlet almost zero. Obviously, the fix for bug 8290 is also a huge improvement if you're using a lot of tags. Lately, I have found some incompatibilities with JSTL (their examples WAR doesn't really like Jasper 2); the admin webapp (big Struts webapp which is painfully slow with Jasper 1 - and that's with one user on an Athlon XP 1700+ ;-) ) and Watchdog both run very well, though. Yeah, I'm not going to start using it for http://www.vnunet.com/ anyway for another while anyway... We've got some beefy hardware behind that site, so speed is not an issue, but if one page goes wild, my salary starts going down. No thanks, I'll wait... Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3 Tomcat3Response.java
costin 02/05/17 12:49:03
Modified:coyote/src/java/org/apache/coyote ActionCode.java
coyote/src/java/org/apache/coyote/tomcat3
Tomcat3Response.java
Log:
Added 2 ActionCodes ( not used for much at this moment except for experimentation ).
One will allow tomcat to signal to the coyote layer that the user has
called flush() on the response and a response must be sent imediately.
( jk may delay sending some messages - it's better to send fewer big messages).
The other one will signal that a new webapp has been deployed.
Revision ChangesPath
1.7 +7 -0
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/ActionCode.java
Index: ActionCode.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/ActionCode.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- ActionCode.java 9 Apr 2002 09:23:40 - 1.6
+++ ActionCode.java 17 May 2002 19:49:03 - 1.7
@@ -79,6 +79,11 @@
public static final ActionCode ACTION_COMMIT = new ActionCode();
+/* A flush() operation originated by the client
+ */
+public static final ActionCode ACTION_CLIENT_FLUSH = new ActionCode();
+
+
public static final ActionCode ACTION_CUSTOM = new ActionCode();
@@ -90,6 +95,8 @@
public static final ActionCode ACTION_STOP = new ActionCode();
+
+public static final ActionCode ACTION_WEBAPP = new ActionCode();
/**
* Callback for lazy evaluation - extract the remote host address.
1.5 +5 -0
jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/Tomcat3Response.java
Index: Tomcat3Response.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/coyote/src/java/org/apache/coyote/tomcat3/Tomcat3Response.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Tomcat3Response.java 2 May 2002 04:19:03 - 1.4
+++ Tomcat3Response.java 17 May 2002 19:49:03 - 1.5
@@ -72,6 +72,7 @@
import org.apache.tomcat.util.net.ServerSocketFactory;
import org.apache.tomcat.util.log.*;
+import org.apache.coyote.ActionCode;
/** The Response to connect with Coyote.
* This class mostly handles the I/O between Tomcat and Coyte.
@@ -129,6 +130,10 @@
coyoteResponse.sendHeaders();
}
+public void clientFlush() throws IOException {
+coyoteResponse.action( ActionCode.ACTION_CLIENT_FLUSH, coyoteResponse );
+}
+
public void doWrite( byte buffer[], int pos, int count)
throws IOException
{
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [Coyote] 1.0 Final release ?
+1 Amy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
On Fri, 17 May 2002, Anthony W. Marino wrote: Costin, If you can give me an idea what I need to do to get it built/running with apache2/TC4.1.2/SuSE7.3 I would be more than happy to do some testing if not more. cvs co jakarta-tomcat-connectors cd jakarta-tomcat-connectors/jk Copy build.properties.sample to build.properties and edit to fit your paths. There are 2 big options: configure and ant. I typically use ant - if you have libtool and gcc installed it should work fine. $ cd native2 $ ant or $ configure ; make This should compile j-t-c/jk/build/jk2/apache2/mod_jk.so. Add a LoadModule to apache's httpd.conf, copy j-t-c/jk/conf/workers2.properties to APACHE_HOME/conf - and start apache. You should be able to see http://localhost/jkstatus - that's the first page to try. Then start tomcat, play with examples, etc. If all this works - please write a nice doc with what you actually did and send it as a patch :-) Note that for tomcat you can use either the old connector ( in 3.2, 3.3, 4.0.x ) or the new coyote-jk connector ( 3.3, 4.x ). Costin Thank You, Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: I'm now running TC4.1.2 and want to use mod_jk2/apache2 for the early stages of my project however I'm not certain what the issues are or when it might become production quality or what I see the empty download areas set up for the various connectors which I hope is an indication of precompiled drops soon to be available. Jk2 is pretty close - I am running all kind of tests, Henri is finishing the configure, Nacho got it running on IIS. Except for iPlanet support, most of the features are ready or pretty close. I'm only doing 'cosmetic' and bug-fixes now - plus documentations for the new config, auto-generation of config from web.xml, etc. I think the release of jk2 depends only on the ammount of help we can get with the build/testing/docs. After we're in a decent state with the docs and the build we can release betas/milestones. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-connectors/jk/java/org/apache/jk/config GeneratorApache2.java GeneratorJk2.java
costin 02/05/17 14:38:12
Modified:jk/java/org/apache/jk/config GeneratorApache2.java
GeneratorJk2.java
Log:
Few fixes to the configs.
Revision ChangesPath
1.3 +10 -4
jakarta-tomcat-connectors/jk/java/org/apache/jk/config/GeneratorApache2.java
Index: GeneratorApache2.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/config/GeneratorApache2.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- GeneratorApache2.java 2 May 2002 03:18:11 - 1.2
+++ GeneratorApache2.java 17 May 2002 21:38:12 - 1.3
@@ -174,6 +174,8 @@
out.println( SetHandler jakarta-servlet2 );
out.println( JkUriSet group + worker );
out.println( JkUriSet servlet + servlet);
+out.println( JkUriSet host + vhost );
+out.println( JkUriSet context + cpath );
out.println( /Location);
out.println();
}
@@ -183,6 +185,8 @@
out.println( SetHandler jakarta-servlet2 );
out.println( JkUriSet group + worker );
out.println( JkUriSet servlet + servlet);
+out.println( JkUriSet host + vhost );
+out.println( JkUriSet context + cpath );
out.println( /Location);
out.println();
}
@@ -192,6 +196,8 @@
out.println( Location \ + cpath + loginPage + \ );
out.println( SetHandler jakarta-servlet2 );
out.println( JkUriSet group + worker );
+out.println( JkUriSet host + vhost );
+out.println( JkUriSet context + cpath );
out.println( /Location);
out.println();
}
@@ -208,7 +214,7 @@
out.println( Location \ + cpath + url + \ );
if( methods.size() 0 ) {
-out.print(Limit );
+out.print( Limit );
for( int j=0; jmethods.size(); j++ ) {
String m=(String)methods.elementAt(j);
out.print( + m);
@@ -216,8 +222,8 @@
out.println();
}
-out.println( AuthType basic );
-out.print( Require group );
+out.println( AuthType basic );
+out.print( Require group );
for( int j=0; jroles.size(); j++ ) {
String role=(String)roles.elementAt(j);
out.print( + role);
@@ -225,7 +231,7 @@
out.println();
if( methods.size() 0 ) {
-out.println(/Limit);
+out.println( /Limit);
}
out.println( /Location);
1.3 +11 -1
jakarta-tomcat-connectors/jk/java/org/apache/jk/config/GeneratorJk2.java
Index: GeneratorJk2.java
===
RCS file:
/home/cvs/jakarta-tomcat-connectors/jk/java/org/apache/jk/config/GeneratorJk2.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- GeneratorJk2.java 1 May 2002 19:55:45 - 1.2
+++ GeneratorJk2.java 17 May 2002 21:38:12 - 1.3
@@ -125,9 +125,11 @@
}
public void generateServletMapping( String servlet, String url ) {
-out.println( [url: + vhost + cpath + url + ]);
+out.println( [uri: + vhost + cpath + url + ]);
out.println( group= + worker );
out.println( servlet= + servlet);
+out.println( host= + vhost);
+out.println( context= + cpath);
out.println();
}
@@ -135,6 +137,8 @@
out.println( [url: + vhost + cpath + url + ]);
out.println( group= + worker );
out.println( filter= + servlet);
+out.println( host= + vhost);
+out.println( context= + cpath);
out.println();
}
@@ -142,9 +146,13 @@
String errPage, String authM ) {
out.println([url: + vhost + cpath + loginPage + ] );
out.println( group= + worker );
+out.println( host= + vhost);
+out.println( context= + cpath);
out.println();
out.println([url: + vhost + cpath + errPage + ] );
out.println( group= + worker );
+out.println( host= + vhost);
+out.println( context= + cpath);
out.println();
}
@@ -167,6 +175,8 @@
out.println([url: + vhost + cpath + url + ]);
out.println( group= + worker );
+out.println( host= + vhost);
+out.println( context= + cpath);
for( int j=0; jroles.size(); j++ ) {
String
Re: Status of JK2
This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? Thanks, Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: Costin, If you can give me an idea what I need to do to get it built/running with apache2/TC4.1.2/SuSE7.3 I would be more than happy to do some testing if not more. cvs co jakarta-tomcat-connectors cd jakarta-tomcat-connectors/jk Copy build.properties.sample to build.properties and edit to fit your paths. There are 2 big options: configure and ant. I typically use ant - if you have libtool and gcc installed it should work fine. $ cd native2 $ ant or $ configure ; make This should compile j-t-c/jk/build/jk2/apache2/mod_jk.so. Add a LoadModule to apache's httpd.conf, copy j-t-c/jk/conf/workers2.properties to APACHE_HOME/conf - and start apache. You should be able to see http://localhost/jkstatus - that's the first page to try. Then start tomcat, play with examples, etc. If all this works - please write a nice doc with what you actually did and send it as a patch :-) Note that for tomcat you can use either the old connector ( in 3.2, 3.3, 4.0.x ) or the new coyote-jk connector ( 3.3, 4.x ). Costin Thank You, Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: I'm now running TC4.1.2 and want to use mod_jk2/apache2 for the early stages of my project however I'm not certain what the issues are or when it might become production quality or what I see the empty download areas set up for the various connectors which I hope is an indication of precompiled drops soon to be available. Jk2 is pretty close - I am running all kind of tests, Henri is finishing the configure, Nacho got it running on IIS. Except for iPlanet support, most of the features are ready or pretty close. I'm only doing 'cosmetic' and bug-fixes now - plus documentations for the new config, auto-generation of config from web.xml, etc. I think the release of jk2 depends only on the ammount of help we can get with the build/testing/docs. After we're in a decent state with the docs and the build we can release betas/milestones. Costin -- Anthony W. Marino Pres./CTO, AWM Objects email: [EMAIL PROTECTED] phone: (732) 610-2441 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2 build.xml
remm02/05/17 15:12:07
Modified:jasper2 build.xml
Log:
- Copy ant.jar in the Tomcat binary, to be used by Jasper for compiling.
Revision ChangesPath
1.4 +4 -0 jakarta-tomcat-jasper/jasper2/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-jasper/jasper2/build.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- build.xml 1 May 2002 01:33:42 - 1.3
+++ build.xml 17 May 2002 22:12:07 - 1.4
@@ -18,6 +18,7 @@
property name=test.failonerror value=true/
property name=test.runner value=junit.textui.TestRunner/
property name=tools.jar value=${java.home}/lib/tools.jar/
+ property name=ant.jar value=${ant.home}/lib/ant.jar/
!-- Construct Jasper classpath --
path id=jasper.classpath
@@ -203,6 +204,9 @@
include name=org/apache/jasper/util/** /
/fileset
/jar
+
+!-- Copy Ant JAR --
+copy todir=${jasper.deploy}/common/lib file=${ant.jar}/
/target
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[PATCH] Re: SSI Servlet has big problems
Hi everyone. Here are more changes to the SSI code. I have a test case ( comparing SSI behavior to Apache by using .shtml files in different tomcat webapps / apache directories ) which I have not included because I'm not sure where to put manual test cases like this. If there is an apprioriate place for these kinds of things, please let me know. I also have not yet updated package.html in the o.a.c.ssi directory. I will do this when I come back from a weekend trip. Here are the instructions for installing the new code, using the jakarta-tomcat-4.0 dir as the base dir. delete files in ( and dir ) : catalina/src/share/org/apache/catalina/util/ssi delete file: catalina/src/share/org/apache/catalina/servlets/SsiInvokerServlet.java unjar the jar -this puts SSIServlet.java into catalina/src/share/org/apache/catalina/servlets -this puts the rest of the files in catalina/src/share/org/apache/catalina/ssi Since the name of the SSI servlet class changes, and since I added some notes to it, patch web.xml according to the included patch. Since I'm planning on maintaining this for a while, commit access might be a good idea, as it makes things easier for everyone. Thanks have a great weekend! -Dan Index: web.xml === RCS file: /home/cvspublic/jakarta-tomcat-4.0/catalina/src/conf/web.xml,v retrieving revision 1.34 diff -r1.34 web.xml 150d149 157a157 !-- This will generally SLOW-DOWN processing. -- 169c169,170 !-- the server root? (0=false, 1=true) [0]-- --- !-- the server root? See note below. -- !-- (0=false, 1=true) [0] -- 171,174c172,177 !-- ignoreUnsupportedDirective -- !-- Should unknown or misspelled Ssi directives-- !-- be ignored and no errors shown?-- !-- (0=false, 1=true) [1] -- --- !-- NOTE : If you set isVirtualWebappRelative to 1 (true), -- !--you probably want to set crossContext=true on the -- !--context that contains the server-side include files -- !--because otherwise the default security will prevent -- !--access to other contexts. The file to change is -- !-- server.xml. -- 181,207c184,204 servlet servlet-namessi/servlet-name servlet-class org.apache.catalina.servlets.SsiInvokerServlet /servlet-class init-param param-namebuffered/param-name param-value1/param-value /init-param init-param param-namedebug/param-name param-value0/param-value /init-param init-param param-nameexpires/param-name param-value666/param-value /init-param init-param param-nameisVirtualWebappRelative/param-name param-value0/param-value /init-param init-param param-nameignoreUnsupportedDirective/param-name param-value1/param-value /init-param load-on-startup4/load-on-startup /servlet --- servlet servlet-namessi/servlet-name servlet-classorg.apache.catalina.servlets.SSIServlet/servlet-class init-param param-namebuffered/param-name param-value0/param-value /init-param init-param param-namedebug/param-name param-value0/param-value /init-param init-param param-nameexpires/param-name param-value666/param-value /init-param init-param param-nameisVirtualWebappRelative/param-name param-value0/param-value /init-param load-on-startup4/load-on-startup /servlet 209d205 ssi.jar Description: Binary data -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Remy, The result of ant in jk dir: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- Anthony W. Marino Pres./CTO, AWM Objects email: [EMAIL PROTECTED] phone: (732) 610-2441 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Try ant all. - Original Message - From: Anthony W. Marino [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED]; Remy Maucherat [EMAIL PROTECTED] Sent: Friday, May 17, 2002 3:52 PM Subject: Re: Status of JK2 Remy, The result of ant in jk dir: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- Anthony W. Marino Pres./CTO, AWM Objects email: [EMAIL PROTECTED] phone: (732) 610-2441 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Are there other properties files that I need to adjust besides in jk and jk/native2 Thanks, Anthony Try ant all. - Original Message - From: Anthony W. Marino [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED]; Remy Maucherat [EMAIL PROTECTED] Sent: Friday, May 17, 2002 3:52 PM Subject: Re: Status of JK2 Remy, The result of ant in jk dir: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
ant all in jk dir gives me the same error: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony Try ant all. - Original Message - From: Anthony W. Marino [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED]; Remy Maucherat [EMAIL PROTECTED] Sent: Friday, May 17, 2002 3:52 PM Subject: Re: Status of JK2 Remy, The result of ant in jk dir: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
news
John: I never heard anymore on the pooling stuff you and I were working on. Has there been any headway with Craig on this. Sorry I have been traveling some lately and may not be caught up on my emails. Tony John Holman wrote: At 04:28 04/01/02, Tony Dahbura wrote: I would like to see about proposing the development of an additional realm module for tomcat. I have begun some design on this and think it will meet the needs of many folks out there utilizing LDAP. I would like to propose a native LDAP realm module that allows utlization of ldap features that may or may not be possible through the JNDI layer. As far as I can see, writing a native LDAP realm module - if by that you mean using the API provided by the Netscape directory SDK rather than Sun's JNDI API - would make little difference to the functionality possible. There may be performance benefits, though I have read conflicting reports on that. The items I am looking at designing into this module are: 1-Connection pooling to support high performance access 2-HA capabilities to support failover if a server goes away 3-Authentication via the server rather than comparison of the passwords in digested forms (this option will also be supported) 4-support for other realm group models (still checking into this). 5-User location without DN identification (no need to be able to build the DN to find the user) 6-SSL support for communications Some history ... The current JNDIRealm implementation in Tomcat 4 is based on code I proposed back in April last year. I believe the existing implementation is sufficiently flexible to cover most ways of representing group information in the directory (item 4), and adding SSL support (item 6) should be trivial. However item 3 (authentication by binding to the directory as the user rather than by retrieving credentials and comparing them explicitly in the realm) and feature 5 (essentially, finding the user's DN by searching the directory on an arbitrary attribute) are not included. I think items 3 and 5 are essential if the module is to be of much practical use. In fact my original proposal did include much of the missing functionality (though not the performance and availability enhancements you mention). Craig made several significant improvements to the code before committing it, but also removed support for items 3 and 5. I subsequently proposed a patch restoring item 3, and planned to propose a second patch restoring item 5 if the first patch was accepted. Craig's response was that we should first get agreement on top-level goals, and proposed a functional specification for the JNDI Realm which is included in the Tomcat release documentation. This spec includes two login modes which cover item 3, but says little about the other items. As far as I know there has been no discussion of the spec since then, and it still has proposed status. So perhaps the next step before enhancing the existing module would be for the group to reach agreement about the required features and produce a revised spec. I'm afraid I never got round to proposing changes to the spec myself but now the subject has come up again I will try to have a go at it. (I'll probably need to look at the format of the source document, which is in some dialect of xml). However, I don't know what the position would be about a completely new module. Cheers, John. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Remy, With connector source from cvs (nothing compiled) what is the very least process I need to do in order to get jk2 for apache2/TC4.1.2/SuSE7.3? Thank You, Anthony Remy, The result of ant in jk dir: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. Anthony This is what I get when I do ant: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/jk/native2/build.xml:90: Could not create task of type: so. Common solutions are to use taskdef to declare your task, or, if this is an optional task, to put the optional.jar in the lib directory of your ant installation (ANT_HOME). Any thoughts? You have to build the Java parts of JK first (go in jakarta-tomcat-connectors/jk, do ant), which include the Ant tasks. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PATCH] Re: [PROPOSAL] Modification of the code generated byJasper2
Mr Chung, I agree completely with your proposed change. Two arrays is all right for me. On Fri, 17 May 2002, Kin-Man Chung wrote: This way, the size of the stack is the maximum number of nesting of the tags, which should much smaller than the number of tags in the page. Such information is easy to collect in Jasper 2, which can be done either in Validator.java, or we have a separate pass whose sole purpose is to collect info such as this. Now, about the level of nesting, shouldn't the information be available through the PageInfo object? After all, the purpose of this class is A repository for various info about the page under compilation. And Generator currently has access to an instance of it. So, if PageInfo had something like a public int getTagElementsMaxNestingLevel() method, Generator could use it to allocate the arrays. We have two changes on the table: 1. Get the information about the level of the nesting with Visitor, or a separate pass; 2. Remove the finallies and replace it with the two state arrays; For #2, I'm confident that I could do it without problem. For the #1, well, I've taken a quick look at Visitor, but the change seems to me far less obvious. The way I see it, in the constructor we initialize the nesting to zero. Each time: public void visit(Node.CustomTag n) throws JasperException is called we increment the nesting, and right after the call visitBody(n);, just before the method terminate we decrement the nesting count. Obviously, we must keep track of the maximum depth level. The information is ready to be used at the end of the: public static void validate(Compiler compiler, ... method, this is the one that initiates the visit(XXX) calls, right?. Would you like me to propose a patch for #1? For #2? And what about having the maximum CustomTag nesting depth level available through PageInfo? Thanks! -- Denis Benoit [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
On Fri, 17 May 2002, Anthony W. Marino wrote: ant all in jk dir gives me the same error: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. You need to build coyote first ( cd j-t-c/coyote ; ant ). Probably that will require tomcat-util :-) There is a build.xml in j-t-c/ that will build all of them. Or you can try the 'configure' path :-) Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
ant coyote in jtc results: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/build.xml:17: /mydirpath/jakarta-tomcat-connectors/jk/build/WEB-INF/classes not found. Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: ant all in jk dir gives me the same error: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.jar to copy. You need to build coyote first ( cd j-t-c/coyote ; ant ). Probably that will require tomcat-util :-) There is a build.xml in j-t-c/ that will build all of them. Or you can try the 'configure' path :-) Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler PageDataImpl.java
kinman 02/05/17 16:44:00
Modified:jasper2/src/share/org/apache/jasper/compiler
PageDataImpl.java
Log:
- Recreate the InputStream in case it is used twice.
Revision ChangesPath
1.3 +10 -15
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java
Index: PageDataImpl.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- PageDataImpl.java 24 Apr 2002 21:12:52 - 1.2
+++ PageDataImpl.java 17 May 2002 23:44:00 - 1.3
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v
1.2 2002/04/24 21:12:52 kinman Exp $
- * $Revision: 1.2 $
- * $Date: 2002/04/24 21:12:52 $
+ * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageDataImpl.java,v
1.3 2002/05/17 23:44:00 kinman Exp $
+ * $Revision: 1.3 $
+ * $Date: 2002/05/17 23:44:00 $
*
*
*
@@ -101,9 +101,6 @@
// default xmlns:jsp and version attributes of jsp:root element
private static AttributesImpl defaultJspRootAttrs;
-// input stream of the XML view
-private InputStream is;
-
// string buffer used to build XML view
private StringBuffer buf;
@@ -136,14 +133,6 @@
SecondPassVisitor secondPassVisitor
= new SecondPassVisitor(page.getRoot(), buf);
page.visit(secondPassVisitor);
-
- // Turn StringBuffer into InputStream
-try {
-is = new ByteArrayInputStream(buf.toString().getBytes(UTF-8));
-} catch (UnsupportedEncodingException uee) {
- // should never happen
-throw new RuntimeException(uee.toString());
-}
}
/**
@@ -152,7 +141,13 @@
* @return the input stream of the XML view
*/
public InputStream getInputStream() {
- return is;
+ // Turn StringBuffer into InputStream
+try {
+return new ByteArrayInputStream(buf.toString().getBytes(UTF-8));
+} catch (UnsupportedEncodingException uee) {
+ // should never happen
+throw new RuntimeException(uee.toString());
+}
}
/*
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [PATCH] Re: [PROPOSAL] Modification of the code generated byJasper2
Now, about the level of nesting, shouldn't the information be available through the PageInfo object? After all, the purpose of this class is A repository for various info about the page under compilation. And Generator currently has access to an instance of it. So, if PageInfo had something like a public int getTagElementsMaxNestingLevel() method, Generator could use it to allocate the arrays. Yes, the information will be available throught PageInfo object, and which is updated in either Validator or Collector (I just make this up). We have two changes on the table: 1. Get the information about the level of the nesting with Visitor, or a separate pass; 2. Remove the finallies and replace it with the two state arrays; For #2, I'm confident that I could do it without problem. For the #1, well, I've taken a quick look at Visitor, but the change seems to me far less obvious. The way I see it, in the constructor we initialize the nesting to zero. Each time: public void visit(Node.CustomTag n) throws JasperException is called we increment the nesting, and right after the call visitBody(n);, just before the method terminate we decrement the nesting count. Obviously, we must keep track of the maximum depth level. The information is ready to be used at the end of the: public static void validate(Compiler compiler, ... method, this is the one that initiates the visit(XXX) calls, right?. Would you like me to propose a patch for #1? For #2? And what about having the maximum CustomTag nesting depth level available through PageInfo? I'll implement maximum tag nesting (though PageInfo) and you can work on #1. Deal? Thanks! Thanks. -- Denis Benoit [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler PageInfo.java Validator.java
kinman 02/05/17 17:29:24
Modified:jasper2/src/share/org/apache/jasper/compiler PageInfo.java
Validator.java
Log:
- Collect maximum tag nesting info and place it in PageInfo.
Revision ChangesPath
1.4 +12 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageInfo.java
Index: PageInfo.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageInfo.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- PageInfo.java 6 May 2002 04:33:15 - 1.3
+++ PageInfo.java 18 May 2002 00:29:24 - 1.4
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageInfo.java,v
1.3 2002/05/06 04:33:15 glenn Exp $
- * $Revision: 1.3 $
- * $Date: 2002/05/06 04:33:15 $
+ * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/PageInfo.java,v
1.4 2002/05/18 00:29:24 kinman Exp $
+ * $Revision: 1.4 $
+ * $Date: 2002/05/18 00:29:24 $
*
*
*
@@ -88,6 +88,7 @@
private boolean isErrorPage = false;
private String errorPage = null;
private String pageEncoding = null;
+private int maxTagNesting = 0;
PageInfo(BeanRepository beanRepository) {
this.beanRepository = beanRepository;
@@ -202,5 +203,13 @@
public String getPageEncoding() {
return pageEncoding;
+}
+
+public int getMaxTagNesting() {
+return maxTagNesting;
+}
+
+public void setMaxTagNesting(int maxTagNesting) {
+this.maxTagNesting = maxTagNesting;
}
}
1.7 +34 -3
jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java
Index: Validator.java
===
RCS file:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Validator.java15 May 2002 20:42:03 - 1.6
+++ Validator.java18 May 2002 00:29:24 - 1.7
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java,v
1.6 2002/05/15 20:42:03 kinman Exp $
- * $Revision: 1.6 $
- * $Date: 2002/05/15 20:42:03 $
+ * $Header:
/home/cvs/jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler/Validator.java,v
1.7 2002/05/18 00:29:24 kinman Exp $
+ * $Revision: 1.7 $
+ * $Date: 2002/05/18 00:29:24 $
*
*
*
@@ -581,6 +581,30 @@
}
}
+/**
+ * A visitor for collection info on the page
+ */
+static class CollectVisitor extends Node.Visitor {
+
+private int maxTagNesting = 0;
+private int curTagNesting = 0;
+
+public void visit(Node.CustomTag n) throws JasperException {
+
+if (curTagNesting maxTagNesting) {
+maxTagNesting = curTagNesting;
+}
+
+curTagNesting++;
+visitBody(n);
+curTagNesting--;
+}
+
+public void updatePageInfo(PageInfo pageInfo) {
+ pageInfo.setMaxTagNesting(maxTagNesting);
+}
+}
+
public static void validate(Compiler compiler,
Node.Nodes page) throws JasperException {
@@ -609,6 +633,13 @@
* (third validation step for custom tags according to JSP.10.5).
*/
page.visit(new TagExtraInfoVisitor(compiler));
+
+/*
+ * Collect information about the page and update pageInfo object.
+ */
+CollectVisitor collectVisitor = new CollectVisitor();
+page.visit(collectVisitor);
+collectVisitor.updatePageInfo(compiler.getPageInfo());
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Costin, Problem/Fixh: j-t-c/jk/build.xml is missing a mkdir for jk/build/WEB-INF/classes. Once I added the mkdir in build.xml I'm able to do ant coyote in j-t-c dir. Anthony : ant coyote in jtc results: BUILD FAILED /mydirpath/jakarta-tomcat-connectors/build.xml:17: /mydirpath/jakarta-tomcat-connectors/jk/build/WEB-INF/classes not found. Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: ant all in jk dir gives me the same error: /mydirpath/jakarta-tomcat-connectors/jk/build.xml:100: Could not find file /mydirpath/jakarta-tomcat-connectors/coyote/build/lib/tomcat-coyote.j ar to copy. You need to build coyote first ( cd j-t-c/coyote ; ant ). Probably that will require tomcat-util :-) There is a build.xml in j-t-c/ that will build all of them. Or you can try the 'configure' path :-) Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[FAQ] jGuru FAQ Update
jGuru maintains FAQs and Forums on Servlets, JSP, and Tomcat (as well as many other Java topics). Here is an automated update on recent postings to Tomcat-related FAQs. Please direct flames and feedback to [EMAIL PROTECTED] . - Alex JGURU PREMIUM SERVICE! How often has jGuru helped you solve a problem? Contribute to the Java community and keep jGuru the best place to get answers by becoming a premium member. Get the World's BEST JAVA SEARCH ENGINE, FASTER PAGE RENDERING, and NO ADS. Just 4.95 a month or subscribe for a year at 49.95 and get 12 months for the price of 10 and a FREE XL JGURU T-SHIRT! Sign up now and try out the premium service for two weeks at no charge! http://www.jguru.com/misc/page.jsp?fsm=premiumregnode=blurbsrc=email Hi. You asked to be notified weekly when certain jGuru.com items get new entries. ++ Tomcat FAQ: http://www.jguru.com/faq/Tomcat Problem with Tomcat (4 and 3.3.x) with Cocoon 1.8.2: Logicsheet util.xsl not found http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=875317 Tomcat4 and AJP12 Connector http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=875216 Configuring cgi-bin virtual path in a stand alone Tomcat 4 installation http://www.jguru.com/misc/faqtrampoline.jsp?src=notifyEID=875215 You can shut email notification off at the FAQ home page(s) or: http://www.jguru.com/guru/notifyprefs.jsp -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
On Fri, 17 May 2002, Anthony W. Marino wrote: I'm now running TC4.1.2 and want to use mod_jk2/apache2 for the early stages of my project however I'm not certain what the issues are or when it might become production quality or what I see the empty download areas set up for the various connectors which I hope is an indication of precompiled drops soon to be available. Jk2 is pretty close - I am running all kind of tests, Henri is finishing the configure, Nacho got it running on IIS. Except for iPlanet support, most of the features are ready or pretty close. I'm only doing 'cosmetic' and bug-fixes now - plus documentations for the new config, auto-generation of config from web.xml, etc. I think the release of jk2 depends only on the ammount of help we can get with the build/testing/docs. After we're in a decent state with the docs and the build we can release betas/milestones. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Status of JK2
Costin, If you can give me an idea what I need to do to get it built/running with apache2/TC4.1.2/SuSE7.3 I would be more than happy to do some testing if not more. Thank You, Anthony On Fri, 17 May 2002, Anthony W. Marino wrote: I'm now running TC4.1.2 and want to use mod_jk2/apache2 for the early stages of my project however I'm not certain what the issues are or when it might become production quality or what I see the empty download areas set up for the various connectors which I hope is an indication of precompiled drops soon to be available. Jk2 is pretty close - I am running all kind of tests, Henri is finishing the configure, Nacho got it running on IIS. Except for iPlanet support, most of the features are ready or pretty close. I'm only doing 'cosmetic' and bug-fixes now - plus documentations for the new config, auto-generation of config from web.xml, etc. I think the release of jk2 depends only on the ammount of help we can get with the build/testing/docs. After we're in a decent state with the docs and the build we can release betas/milestones. Costin -- Anthony W. Marino Pres./CTO, AWM Objects email: [EMAIL PROTECTED] phone: (732) 610-2441 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
