cvs commit: jakarta-tomcat/src/native/mod_jk/apache2.0 Makefile.linux mod_jk.c

hgomez 01/02/09 00:48:42 Modified:src/native/mod_jk/apache2.0 Makefile.linux mod_jk.c Log: mod_jk.c adapted to the lastest Apache 2.0 API Enjoy ! Revision ChangesPath 1.5 +25 -26jakarta-tomcat/src/native/mod_jk/apache2.0/Makefile.linux Index:

TEI to get info from a outer tag

Hi, I have the following tags in my taglib: example:parent attrib1="fish" example:results parentTag="parent" do something with results e.g. %=parent.getId()% /example:results /example:parenttag The parent goes off and gets a collection of bean's

mod_jk TC 3.2.2 != TC 3.3 = was RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

While looking updating TC 3.2.2 with mod_jk for Apache 2.0 I notice that mod_jk from TC 3.2.2 and 3.3 are still differents I attached a list of diff without the version which are also different in each files. I propose that the whole TC 3.3 mod_jk native code (ap1.3, ap2.0 and common) are

RE: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core Constants.java

|it is appropriate for bugs to be reported against 3.2.1. or NIGHTLY. Unfortunately, only the installer will know which is appropriate. Anybody else will misfile the bug. Given some of the bug reports I've seen, even the installer may misfile the bug. Standard Apache practice is to bump the

RE: cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core Constants.java

I didn't see the thread immediatly. I tagged constants like to show that's no more 3.2.1. You could change in 3.2.2-beta or better 3.2.2-dev ( la Apache httpd) but the name must be changed to show that's it's a new version La prise de conscience de votre propre ignorance est un grand pas vers

Tomcat 3.3 Milestone 1 Status

Hi All, The TC3.3 release plan called for a Milestone 1 freeze yesterday (2/2/2001). However, some important changes were needed and I haven't finished my review of the documentation, so this has been delayed. I plan to finish my review of the documentation today. Then after a good nights

cvs commit: jakarta-tomcat/src/tests/webpages/WEB-INF test-tomcat.xml

costin 01/02/09 09:02:03 Modified:src/tests/webpages/WEB-INF test-tomcat.xml Log: Ops, the updated file was in build and didn't got commited ( thanks to nightly build for finding that :-) Revision ChangesPath 1.16 +28 -22

cvs commit: jakarta-tomcat/src/etc server1.xml

costin 01/02/09 09:05:02 Added: src/etc server1.xml Log: Server.xml, with the simplified syntax ( old RequestInterceptor class= " will still work, of course ). If nobody objects I'll make it the default. I would also move the context definitions in a separate file, as

Porting mod_webapp to APACHE 2.0 (At least trying)

Hi, I have started to port mod_webapp to APACHE 2.0, I reached the following: +++ Module Name: mod_webapp.c Content handlers: (code broken) Configuration Phase Participation: none Module Directives: WebAppConnection - [optional parameter] WebAppMount - Current Configuration:

class LDADRealm

Hello, First an apology: Sorry, I know the right way to submit code is through the CVS Repository, but I really just wanted to give this one useful class to the project (if you want it.) Anyway, I wrote it, I documented it pretty well, I thought it might be useful to others, it may need to be

Session-expiry bug? getLastAccessedTime

Hi, I noticed a problem with session timeouts in Tomcat3.2.1 The background thread that recycles sessions based on timeouts uses Session.getLastAccessedTime(). The session object itself has two variables lastAccessedTime and thisAccessedTime. - public

Re: Tomcat 3.3 Milestone 1 Status

Hi Larry, What about doing that after weekend ? Let's say is superstition, but so far Monday has been a good day for milestones. Though not completely frozen, only simple (i.e. safe) bug fixes should be made at this point. If there is something bigger that you think should be in TC3.3m1,

Re: Tomcat 4 status

Glenn Nielsen wrote: I was wondering what the status of getting Tomcat 4 ready for its next beta release currently is. I have finished implementing the Java SecurityManager and the changes to jasper class loading. I know we took a step back to make a few architectural changes. Are those

Re: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was 'Re: 3.2.2 Release?'

Just checking back on the status of this patch, I received some email from someone who isn't actively on the list but has the same problem as originally reported in Bugrat report 723. Anyone have any feedback on the patch or the control characters in URL question I had? David Weinrich -

Re: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was'Re: 3.2.2 Release?'

Just checking back on the status of this patch, I received some email from someone who isn't actively on the list but has the same problem as originally reported in Bugrat report 723. Anyone have any feedback on the patch or the control characters in URL question I had? I will work on it for

[PATCH] encryption support in SimpleRealm.java

Hi, I've been playing around with Tomcat 3.2.1 as we have several production servers using it and was concerned by the way the passwords were stored in tomcat-users.xml. The included patch modifies SimplesRealm.java (org.apache.tomcat.request.SimpleRealm) so it can correctly manage a

BodyContentImpl optimization

Hopefully this is the right place for the following information. If not, I'm sorry. I don't really do active development on tomcat (cvs updates, etc) but while profiling our application, I noticed a couple of minor improvements that could be made to BodyContentImpl.java. Specifically, in

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/core Constants.java

marcsaeg01/02/09 15:05:47 Modified:src/share/org/apache/tomcat/core Tag: tomcat_32 Constants.java Log: Changing TOMCAT_VERSION to 3.2.2-dev Revision ChangesPath No revision No revision 1.22.2.10

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

marcsaeg01/02/09 15:06:27 Modified:src/webpages Tag: tomcat_32 index.html Log: Changing version to 3.2.2-dev Revision ChangesPath No revision No revision 1.13.2.10 +2 -2 jakarta-tomcat/src/webpages/index.html

[PATCH] TC4: TomcatBlock on Avalon 3.1a1: Part 1

Hi guys. I've just finished a bunch of changes to make Tomcat 4 (Catalina and Jasper) work on top of Avalon 3.1a1. Remy: Thanks for CatalinaBlock -- it served as a good starting point! What I've done is made the necessary modifications to make Tomcat 4 build as a single Avalon .bar (Block

[PATCH] TC4: TomcatBlock on Avalon 3.1a1: Part 2

Attached are the diffs to the files that I modified to make TomcatBlock (Tomcat 4 running on Avalon 3.1a1). Explanation: build.xml (the top-level build.xml file) I moved the dist-opt-avalon target (and associated stuff) to this file since to build the bar file it needs to copy stuff from

[PATCH] TC4: TomcatBlock on Avalon 3.1a1: Part 2 (for real this time)

Last time I forgot to attach the diffs! Sorry.. This mail has them. Attached are the diffs to the files that I modified to make TomcatBlock (Tomcat 4 running on Avalon 3.1a1). Explanation: build.xml (the top-level build.xml file) I moved the dist-opt-avalon target (and associated stuff)

[PATCH] TC4: TomcatBlock on Avalon 3.1a1: Part 3

Attached are the files I added to make TomcatBlock (Tomcat 4 running on Avalon 3.1a1): catalina/src/conf/avalon-MANIFEST.MF This manifest file is used to create tomcat-4.0.bar. Avalon needs a special manifest to know which Block is contained in the BAR file.

RE: Porting mod_webapp to APACHE 2.0 (At least trying)

Nice to see that we could have Apache 2.0 with mod_webapp. La prise de conscience de votre propre ignorance est un grand pas vers la connaissance. -- Benjamin Disraeli -Original Message- From: jean-frederic clere [mailto:[EMAIL PROTECTED]] Sent: Friday, February 09, 2001 5:19 PM To:

jspDestroy() seems broken

When using Tomcat 3.1 I had an initialization page that made use of the jspInit() and jspDestroy() methods to initialize and destroy a server pool like the following: %! static public Pool pool = null; %! public void jspInit() { System.out.println("JSP init"); pool =

Re: Porting mod_webapp to APACHE 2.0 (At least trying)

jean-frederic clere [EMAIL PROTECTED] wrote: Hi, I have started to port mod_webapp to APACHE 2.0, I reached the following: +++ Module Name: mod_webapp.c Content handlers: (code broken) Configuration Phase Participation: none Module Directives: WebAppConnection - [optional

cvs commit: jakarta-tomcat/src/share/org/apache/tomcat/util/compat SimpleClassLoader.java Jdk11Compat.java

costin 01/02/10 00:12:42 Modified:src/share/org/apache/tomcat/startup Main.java src/share/org/apache/tomcat/util/compat Jdk11Compat.java Added: src/share/org/apache/tomcat/util/compat SimpleClassLoader.java Removed: