Re: CVS / mod_webapp / web-connector sub-project

On Tue, 17 Apr 2001, Jon Stevens wrote: > > mod_jk is the de-facto standard to link a web server (not only > > Apache) to tomcat. mod_webapp is really new and having it > > incompatible with mod_jk will raise more questions and requests > > than necessary. > > Huh? mod_jk is not 100% compatible

Re: CVS / mod_webapp / web-connector sub-project

On Tue, 17 Apr 2001, Craig R. McClanahan wrote: > * Configuration complexity - The above issues can often be dealt with > by tediously configuring everything twice (once in web.xml and once > in httpd.conf). A better approach would be to make ajp12/ajp13 > auto-configure Apache from the we

Re: CVS / mod_webapp / web-connector sub-project

> Why not use mod_webapp/mod_jk to start the > web-connector sub-project allowing us to remove many question > related to connectors from Tomcat user/dev lists ? > > The same web-connector project could be used against > Tomcat 3.2/3.3/4.0 but not be restricted to Tomcat. > Any project unde

Re: /dev/urandom patch

Hi Bojan, It's the third ( no time ), I am deep into some charset bugs and jasper and most developers are busy with various projects. You may file a feature request on bugzilla, attach you patch - this way it'll be recorded. Or send few more patches ( there are many open bugs, most of them are

Re: CVS / mod_webapp / web-connector sub-project

Henri, I think Dan is right on this one - improving the configuration of mod_jk is probably the most important thing, and merging with mod_webapp and porting it's protocol and config mechanism would be a good way to do that. I think the best way to do that would be a revolution ( like jasper34

Re: mod_jk on HP-UX11

Hi, > yesterday I played around with the source code of mod_jk because it does > not work for HP-UX 11. In order to test some things, I need to know > something about the expected behaviour (the Faq-O-Matic is out of order > at the moment): That's great, can you compile it ? ( there is a bug in

RE: CVS / mod_webapp / web-connector sub-project

On Thu, 19 Apr 2001, GOMEZ Henri wrote: > >I think Dan is right on this one - improving the configuration > >of mod_jk > >is probably the most important thing, and merging with mod_webapp and > >porting it's protocol and config mechanism would be a good way > >to do that. > > I agree that int

RE: [PATCH] */build.sh

On Thu, 19 Apr 2001, GOMEZ Henri wrote: > What about checking also the build.sh for Tomcat 3.3 :) What about removing the build.sh/build.bat completely ( at least from 3.3). It used to be a workaround, when ant didn't had support for classpath. Proposal: remove build.sh/build.bat, use "ant".

Re: Jasper

Hi Mel, As you know, we are on the same page on the main issue ( refactoring jasper), but there are few details... ( sorry for responding so late) First, I think we need to agree on the goals :-) Your proposal is great, but I would like to make explicit the following ( at least ): - clean sepa

Re: Jasper

> > - "commons"-style components. Even if we'll use explicit interfaces for > > ... > > I'll need to review the commons project to adopt any > standards that are in play there, but I don't see a > problem. This brings up some things I'll need to know The important ideas ( for this discussion )

Re: Access log files in the style of Apache

Hi Jochen, Thank you for this patch - it is something very needed. I don't think this can make it for 3.2.2 release ( but it can be made available for people to compile as a separate module), but it'll be available for 3.3 ( I hope in the default distribution - but we do have the option of makin

Bugs <500

Hi, I finished reviewing bugs marked as LATER with ID<500. There are 5 bugs that we should fix for 3.3: 345 - Date header 348 - Security roles 375 - // security checking - revert to paranoid path checks 454 - mod_jk spawning (hunged ) apache processes when tomcat is down ( maybe later -

RE: Bugs <500

On Mon, 23 Apr 2001, Steve Downey wrote: > 360 and 412 look like they might cause me some headaches. Are you -1 on > fixing them, or -0? That is, should I bother or not? I'm +1 on fixing them - the list reflects what I think whould have high priority ( i.e. things fixed in 3.2 but not 3.3, spec

Re: [VOTE] New Committer: Bip Thelin

+1 Costin On Sun, 22 Apr 2001, Kief Morris wrote: > I would like to propose Bip Thelin as a new committer. He has made a number > of contributions of patches over the past several months, including SSI and > JDBCRealm, and most recently, is doing solid work on session persistence. > > Kief >

RE: Store Proposal

On Mon, 23 Apr 2001, Craig R. McClanahan wrote: > 3.3 wants to maintain JDK 1.1 compatibility -- at least that's the last I > heard; maybe attitudes are changing. My attitude is changing indeed - I would like to propose J2ME compatibility for tomcat 3.3 :-) ( the only problem is one class that

RE: Store Proposal

Typos... > That doesn't mean 3.3 _modules_ are restricted in any way to JDK1.1. > Tomcat has already at least 2 modules that are JDK1.2 compatible. Are using JDK1.2 specific features. > > The restriction ( the way I understand it at least ) is that tomcat4 > should provide a (basic) se

Re: ServerSocket not being closed properly.

Fixed for 3.3, I'm not sure it's very easy for 3.2.2. The threads are waiting in accept, so one solution is to set "stopped" and make a dummy connection. The problem is that there are few places that need to be fixed to support stop/start ( another bug was that logger and session expirer thread

RE: Store Proposal

On Mon, 23 Apr 2001, Craig R. McClanahan wrote: > > Yes, I think the session manager should be a separate module, with minimal > > dependencies on other components. > > Given that the 4.0 architecture exists, works fine, lasts a long time, > ... what you'd want, then, is for the existing Catalin

RE: ServerSocket not being closed properly.

On Mon, 23 Apr 2001, Arun Katkere wrote: > In my experience (having started/stopped Tomcat engine programatically via > ContextManager API in a loop 100s of times), server socket is always closed > correctly. And looking at 3.2.2 beta 3 source code, both PoolTcpEndpoint and > SimpleTcpEndpoint cl

RE: ServerSocket not being closed properly.

On Tue, 24 Apr 2001, Brad Cox PhD wrote: > At 7:19 PM -0700 04/23/2001, [EMAIL PROTECTED] wrote: > >On Mon, 23 Apr 2001, Arun Katkere wrote: > >In general you need to do something to unblock the accept thread, and 3.2 > >doesn't have this in. > > Yes, I remember now. You're absolutely right. You

Re: Fixing error pages on virtual hosts.

Hi Peer, Great fix - thank's. I will do the fix in 3.3, and if Marc makes another beta ( for jsp fixes ) it would be great if he takes this one in. Marc - I know the code pretty well, and this line should have been in. I don't think it'll affect any other piece of code, getHandlerForPath is

RE: ServerSocket not being closed properly.

On Tue, 24 Apr 2001, Brad Cox wrote: > At 7:23 AM -0700 04/24/2001, [EMAIL PROTECTED] wrote: > >Anyway - a cleaner solution ( IMHO ) is to just set "stoped" and do a > >bogus connection. That's what I did in 3.3 - and seems to work fine. > > That does sound better. I really hope this gets nailed

Re: what is the deal with tomcat 4 and web server connectors??

Dan, It seems the most requested ( and important) feature for mod_jk is simpler configuration - and I think we can do many simple things with a lot of effect ( sending the config automatically is one - and quite easy ). Regarding the use of mod_jk for tomcat4 - I would sugest a different aproac

RE: ServerSocket not being closed properly.

On Tue, 24 Apr 2001, Brad Cox wrote: > >In 3.3 we package all the tests as self-contained wars, and the admin has > >a web-based runner - but it needs more polishing to make it really easy to > >use. > > That's roughly how I meant for a gui to work. A few text boxes for > options every novice m

Re: Tomcat 3.2.2 patches

On Tue, 24 Apr 2001, Marc Saegesser wrote: > Costin, Henri, > > You both asked about some simple patches for Tomcat 3.2.2. There will be > another (hopefully the last) beta release for 3.2.2, so go ahead and commit > those changes. Thanks. > I'm working a bug in Jasper that will certainly re

Re: Tomcat 3.2.2 and Thread synchronization

One quick comment - this should be provided by the servlet container. ( i.e. make sure that destroy() is not called while a servlet is in progress ). Of course, JspServlet is overriding the container and manage it's own servlets. I'll look at the code and try to port it to 3.3 - and send more c

Re: cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/sessionStoreBase.java

> While you are at it, the current convention in Tomcat is to use spaces > rather than embedded tabs for indentation. I know some of the old code Is it a convention or an absolute requirement ? Costin ( waiting for the space police to remove my tabs :-)

Jasper34: runtime

Hi Mel, I noticed you used jakarta-tomcat/src/jasper34 for your protoype classes. If you don't mind, I would like to move them in proposals/jasper34/, and keep the work in jasper34 in the experimental area until it's ready. I'll do a small commit - I did a refactoring for the runtime ( 1.1

Jasper34: Constants

One change - the Constants is used for "constnats" and for logging and localization. Constants.message() and getString() will be removed ( both 1.1 and 1.2 runtimes ), moved to JspFactoryImpl.ContainerLiaiason. I would also like to move some of the constants that are specific to a particular cl

Jasper34: diffs between 1.1 and 1.2

Hi, There are few diffs between the runtime for 1.1 and 1.2. Some of them are obviously due to API changes ( additions mostly, only one change that I could identify - JspInclude ). Most are due to changes/fixes that went only in one branch ( various optimizations for 3.3, security manager for 4

Jasper34: sandboxing/Priviledged

Glenn, I hope you're around... Can you explain ( again ) the rationale for the doPriviledged() in PageContextImpl ? >From what I see, the release() doesn't do anything special, and init() does only the System.getProperty - but there are other ways to do that without a full Priviledged. 3.3 s

RE: Jasper34: diffs between 1.1 and 1.2

On Fri, 27 Apr 2001, Steve Downey wrote: > The only downside I see is that the security manager triggers the use of > URLClassloader on a per JSP page basis. As I understand it, this class is > broken w.r.t. Java 1.1. Ok, now I'm completely confused - what's the relation between doPriviledged a

Re: ajp13 question

What about creating a directory jakarta-tomcat/src/doc/notes and checking in all the "relevant" mail - like this one ? I'm talking about proposals, technical notes, etc. Searching the mail archive to find "good stuff" is hard ( given the noise), and maybe someone could turn various mails into do

Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)

On Mon, 30 Apr 2001, kevin seguin wrote: > that's what i've decided to do. my goal is to first get things working, > at least minimally, then i (or someone else) can address load-balancing > later. my gut feeling, though, after spending some time on ajp13 and > tomcat 4 is it's certainly possib

RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)

On Mon, 30 Apr 2001, GOMEZ Henri wrote: > >damn! i wasn't expecting that complex of an answer ;) > > The difficulty is in the difference between TC 3.2/3.3 and 4.0 > and the how the connector are written. They're just to highly > linked in the tomcat core ! Well, someone can reimplement the pr

Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)

On Mon, 30 Apr 2001, Remy Maucherat wrote: > > The 3.3 adapter is not linked to the tomcat core, but more to the > > low-level objects ( and most of the performance comes from that > > layer ). In other words - minimal garbage generation, lazy evaluation, > > and all the stuff. > > Unless everyo

RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)

> Good. > > Did there is people around using NES/IPLANET which could > confirm the status of ajp13 and NES ? > I tested it ( long ago ), both NES and IIS ( yes, I did installed windows for that !). Ajp13 and JNI used to work fine ( JNI doesn't work very well with Apache1.3.x, as it's not multit

Re: Tomcat 3.2.2 beta 4

On Mon, 30 Apr 2001, Marc Saegesser wrote: > Tomcat 3.2.2 beta 4 is available for download. If you can provide binaries > for various please send them to me or update the FTP site. Thanks. Great !. Marc - one bad news, I have a bug that I think we should fix, it should be an easy fix and prob

RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)

On Tue, 1 May 2001, Ignacio J. Ortega wrote: > > Good. > > > > Did there is people around using NES/IPLANET which could > > confirm the status of ajp13 and NES ? > > > > HAve sense to continue naming ajp12 on IIS howto doc? i think not as > there isnt a substitute for isape_redirect.dll as mod

Re: ANNOUNCE - web-connector

On Mon, 30 Apr 2001, Scott Sanders wrote: > Hopefully we might even get back to one that worked as well as JServ's > connector. > > As a goal, could you add back the ability to restart the JVM if necessary? > +1 as a goal. ( it will help if you could also send a patch :-) Costin

RE: Tomcat 3.2.2 beta 4

On Mon, 30 Apr 2001, Marc Saegesser wrote: > Costin, > > Let me know what you find and what the fix looks like. If its a simple fix > then I'm OK with just developer testing and code review. Ok, it seems it's a false alarm - the problem may be related with the infinte loop if no ROOT exist, an

Re: "core"

Hi Thomas, I don't think changing the "core" is possible at this stage, and you should really fix your unix scripts - the "core dump" can't be a directory, and checking if something is a regular file or a dir is quite trivial. Costin On Tue, 1 May 2001, Thomas Riemer wrote: > In several dif

Re: [TC3.3]Servlet-Engine Header in ajp13 and Http10 connectors

On Tue, 1 May 2001, Ignacio J. Ortega wrote: > Hola a todos: > > I'm wondering if the lack of "Servlet-Engine:" header in ajp13 and > http10 connectors is intentional or a missed feature ( for not call it a > bug as for me it's not :) ?? > > The same for the "Date" header in Http10 ?? > > "

RE: Tomcat 3.2.2 beta 4

Marc, I can quickly backport the jdkcompat package from 3.3 - it would be cleaner than hacking generateSessionId. The package is "standalone", doesn't depend on any 3.3 feature - and it's quite simple and effective. Also, if you could review the following patch that will fix "case sensitive

RE: Tomcat 3.2.2 beta 4

On Tue, 1 May 2001, Marc Saegesser wrote: > Costin, > > The toLowerCase() patch look OK. > > If Glenn can fix the session id stuff easily then I think thats the best > approach right now. Adding the jdkcompat package can't hurt - it'll be a minimal change in SessionUtil plus the addition of 3

RE: Relase 3.3 status

On Wed, 2 May 2001, Larry Isaacs wrote: > Regrettably, I have been swamped with other work for a while. > I am currently reviewing the state of bugs to see what > work remains. I'll add a release notes file to show > what we plan to fix for 3.3 and which bugs will not. > I'll then update the sch

RE: Tomcat 3.2.2 beta 4

Done. The code doesn't compile on JDK1.1 ( I can add the excludes for util.compat, but there are other places in the code - compiling on JDK1.1 is not a major requirement, only the ability to run ). Costin On Wed, 2 May 2001, Marc Saegesser wrote: > Glenn, Costin, > > If Glenn is OK with it

Re: cvs commit: jakarta-tomcat/proposals/build2/ant tomcat.jsp

Hi Casey, Sorry, I have too many things for now - the web based build is going to wait a bit. If you could check in the changes, great.( I hope you got the commit access ) BTW, I have few ideas for the pooling in jasper34 ( I would like to make the pool pluggable, and managed by the container ).

Re: [VOTE] New Committer: Kevin Seguin

+1 Costin On Thu, 3 May 2001, GOMEZ Henri wrote: > I would like to propose Kevin Seguin as a new committer. > > He make a great job in developping the ajp13 protocol > for Tomcat 4.0 and this code will be a great help for > sites wanting to upgrade from 3.2.x to 4.0 while still > using mod_j

Re: [VOTE] New Committer: Kevin Seguin

+1 Costin On Thu, 3 May 2001, GOMEZ Henri wrote: > I would like to propose Kevin Seguin as a new committer. > > He make a great job in developping the ajp13 protocol > for Tomcat 4.0 and this code will be a great help for > sites wanting to upgrade from 3.2.x to 4.0 while still > using mod_jk

Re: Realm implementations

Hi Antony, > In TC 3.x authenticate() method of a realm is called for every request. Well, yes and no. The BaseInterceptor.authenticate() callback is called on every request ( as it is on Apache and other servers ). The authenticate method of the realm ( that goes to a database or does expe

Re: [PROPOSAL/VOTE] New Repositories for Collaborative Development

+1 for separate repository, but I preffer "jakarta-tomcat-modules" or some common repository. Reason: connector and jasper are just particular modules that could be used in multiple versions of tomcat ( like 3.2, 3.3, 4.0 or 4.1 ). There are other pieces that could be developed in the common r

Re: [GUMP] Build Failure - Tomcat 3.x

Ok, 2 changes in ant: copy no longer ignores inexisting source, and the parser changed. Both seem fair changes, we should fix the build.xml in tomcat. I would like to use this "oportunity" to also upgrade to jaxp1.1. ( in order to avoid too much pain - since tomcat used to build with no exter

Re: [PROPOSAL/VOTE] New Repositories for Collaborative Development

On Fri, 4 May 2001, Craig R. McClanahan wrote: > > +1 for separate repository, but I preffer > > > > "jakarta-tomcat-modules" or some common repository. > > > > Reason: connector and jasper are just particular modules that could be > > used in multiple versions of tomcat ( like 3.2, 3.3, 4.0 o

Re: [PROPOSAL/VOTE] New Repositories for Collaborative Development

On Fri, 4 May 2001, Bip Thelin wrote: > [EMAIL PROTECTED] wrote: > > > > On Fri, 4 May 2001, Craig R. McClanahan wrote: > > > > > > [...] > > > > > > I've said it before, and i'll say it again -- 3.2 is in maintenance mode, > > > and doesn't need any further focus for enhancements. Time spent p

Re: ajp12, ajp13, mod_webapp, and http protocols

On Sat, 5 May 2001, kevin seguin wrote: > i believe the original reason why mod_jserv and ajp were introduced was > for connecting the apache web server to the old JServ servlet > container. when tomcat showed up, mod_jserv was used for it too. i > think mod_jk, which added support for more web

Re: ajp12, ajp13, mod_webapp, and http protocols

Hi, On Sat, 5 May 2001, Xilei Wang wrote: > 1. I know ajp protocol was originally introduced by > by mod_jserv to communicate with JServ. But what I > was wondering is, why at that time, a new protocol, > ajpxx was introduced rather using the existing http > protocol. It is felt that a binary

RE: [PROPOSAL/VOTE] New Repositories for Collaborative Development

On Mon, 7 May 2001, Craig R. McClanahan wrote: > > There seems to be consensus growing around these three names. Does that > meet with everyone's agreement? If so, I can create the new repositories > and set up the permissions stuff later today. +1 ( Regarding the name for the third: +0.7 fo

Re: [PROPOSAL AJP14] AJP13 Evolution

On Mon, 7 May 2001, Dan Milstein wrote: > Henri, > > Lots of good stuff. A few ideas/possibilities: > > 1) We've talked about specifying a response packet to indicate that the > engine (or the web server) doesn't recognize a packet sent over. This would > allow us much more flexiblity to add

RE: [PROPOSAL/VOTE] New Repositories for Collaborative Development

On Mon, 7 May 2001, Craig R. McClanahan wrote: > * Dependence on Java2 as a base platform. This is not just an issue > of using the collections classes (although that's part of it). Consider > a few other issues: Once again - there is no problem with using Java2 for tomcat modules in 3.x.

RE: [PROPOSAL/VOTE] New Repositories for Collaborative Development

> > - Performance tuning for Java2 JVMs (particularly HotSpot) focuses > your attention on different areas than JDK 1.1. Trying to optimize > for both increases the effort required, and could lead to conflicts > where you want to do things differently on different platforms. Well,

RE: [PROPOSAL/VOTE] New Repositories for Collaborative Development

> That's more feasible, but it also has a different set of issues: > > * Configuring the current generation of web connectors causes 90% of the > user gripes about Tomcat. Anyone who needs evidence should subscribe > to TOMCAT-USER and start answering all the questions about configuring. We

Re: [GUMP] Build Failure - Tomcat 3.x

I guess there's a problem in gump - the build.xml has been fixed, I guess the update didn't worked. > prepare: > [mkdir] Created dir: /home/rubys/jakarta/jakarta-tomcat/build/tomcat > ... > [copy] Copying 7 files to /home/rubys/jakarta/jakarta-tomcat/build/tomcat/bin > [copy] Could

RE: [PROPOSAL AJP14] AJP13 Evolution

On Mon, 7 May 2001, Mike Braden wrote: > +1 > > As for the security key, would it be possible to generate > a unique key when mod_jk is first installed? Maybe we could > create some basic mechanism, similar to the way ssh generates That's what tomcat3.3 does for ajp12 shutdown messages: at st

RE: [PROPOSAL AJP14] AJP13 Evolution

> Argh, all the subtility is here. > Basically even if ajp13 is a bidirectional protocol, > it's a request/reply protocol since it's how a web > server function : > 1) FORWARD REQUEST FROM WEB-SERVER TO SERVLET ENGINE > 2) WAIT FOR RESPONSE > 3) GET RESPONSE AND FORWARD TO WEB-SERVER. Well, I se

Re: [PROPOSAL AJP14] AJP13 Evolution

On Tue, 8 May 2001, Dan Milstein wrote: > The only thing we really lose is the ability for the servlet engine to send > a message to TC in between requests. And the main messages, as I see it, > are: > >a) the entire engine is shutting down > >b) certain contexts are shutting down >

Re: Tomcat 3.2.2 beta 4 - AJP14 continuation

On Tue, 8 May 2001, Andrey Kartashov wrote: > What I'm trying to say is: > To address this group of people I'd suggest splitting distribution into > "pure java" Tomcat part + extensions. This way only NECESSARY files will > make their way to "conf" directory. If someone is (for example) intereste

RE: [PROPOSAL AJP14] AJP13 Evolution

On Wed, 9 May 2001, GOMEZ Henri wrote: > May be with the directive > > JkEnvVars MYVAR1 MYVAR2 MYVAR3 MYVAR4... > > > The traffic will be more important but these informations > will be usefull for some... > > What about that ? +1 to add this to a TODO list, but low priority :-) Let's firs

Re: [GUMP] Build Failure - Tomcat 3.x

On 9 May 2001, Craig McClanahan wrote: > > This email is autogenerated from the output from: > > Craig, Sam - can someo

Re: Collaborative Development (not Cat and Dog)

On Wed, 9 May 2001, Craig R. McClanahan wrote: > Just off the main Apache web site, Tomcat binary downloads (in various > release and nightly build formats) run from 50,000 to 100,000 downloads > per month. That doesn't count mirror sites (official and unofficial), > people who download Tomcat a

Re: [PROPOSAL] Update to Tomcat 3.3 Release Plan

+1 Larry - it would be great to also have a list with the bugs you consider to have high "priority", in order for us to work on those bugs first. Costin On Wed, 9 May 2001, Larry Isaacs wrote: > Sorry to have been out of action for so long. To bring > Tomcat 3.3 to a release, I pro

Re: Collaborative Development (not Cat and Dog)

> > I feel a personal, moral, obligation to the thousands and thousands of > people who download Tomcat in the hopes of having a servlet container that > works, and who want to have confidence in a solid support and future +1 Very well put, for me it's the only reason I'm still subscribed to th

RE: FW: Any known issues with Tomcat 3.2.1 and class loading ?

One possible problem may be the fact that by default, tomcat3.2.1 doesn't set the context class loader ( a JDK1.2 feature ). Just add Jdk12Interceptor in server.xml ( the default config assumes JDK1.1. In tomcat3.3 we detect the VM and add the interceptor automatically, but this feature h

RE: [PROPOSAL AJP14] AJP13 Evolution

Regarding APR: I do remember the same discussion happened about one year ago, when mod_jk was starting up. And at that time we felt that APR is the best solution for us, for the long term - and the same is probably true today. The "common" dir in mod_jk was intended as a temporary substitute

Bug votes on bugzilla

Hi, I just read the release plan for xalan2.1, and I think there is a great idea in it: start using the bugzilla voting system to prioritize the bugs. Every user ( who register with bugzilla I think ) has 6 votes to assign to various bugs. This is the best way to send a message about what's impo

Re: [PROPOSAL AJP14] AJP13 Evolution - Second Pass

+1 I'll try to implement the Java side as you go with the C changes, unless someone else volunteers ( jasper is taking more than I expected, and xalan has a release planned in few weeks ). BTW, we'll need to discuss about the Java side - so optimizations on the "lower" level would work on any

RE: [PROPOSAL AJP14] AJP13 Evolution - Second Pass

On Thu, 10 May 2001, GOMEZ Henri wrote: > > AJP14 will be only available to TC 3.3/4.0 since the 3.2 is closed > to new features. But did the AJP12/AJP13 in jakarta-tomcat-connectors will > contains code for tomcat 3.2 tree also ? > If anyone writes it - yes. Most tomcat users are using tocma

Re: ajp13 and tomcat 4

On Thu, 10 May 2001, kevin seguin wrote: > will the ajp13 connector go in there two? currently, it relies on core > catalina classes to build. if the ajp13 connector is in > jakarta-tomcat-connector, it'll require a catalina.jar to build. that's > fine with me though... +1 jakarta-tomcat-con

Re: [PROPOSAL AJP14] AJP13 Evolution - Second Pass

On Thu, 10 May 2001, kevin seguin wrote: > > This is not the "easiest" solution - from my point of view the easisest > > would be to just write the Ajp14Interceptor and use the existing and > > optimized 3.3 infrastructure. ( and use a reimplementation of the protocol > > for 4.0 - using their lo

Re: [PROPOSAL AJP14] AJP13 Evolution - Second Pass

On Thu, 10 May 2001, kevin seguin wrote: > > > The whole idea is to avoid expensive operations until they are actually > > needed - most servlets don't read all the headers, so there's no need to > > create the strings and hash them. ( it's not even needed to convert from > > bytes to chars - an

Re: [PATCH] LDAPRealm implementation

On Fri, 11 May 2001, Ellen Lockhart wrote: > I actually ported this one from a 3.2.1 implementation I did, with a few > changes. But since there is now a JNDIRealm implementation, wouldn't it be > preferred to have a counterpart to that one on the TC 3.3 tree (same setup, > etc.)? If you have a

Re: [PROPOSAL] jakarta-tomcat-connectors renaming

What about: j-t-c/jk/native/ j-t-c/jk/java/org/apache/jk/ajp/{common,ajp13,ajp14} j-t-c/jk/java/org/apache/jk/jtc/jni j-t-c/jk/java/org/apache/jk/tc33 j-t-c/jk/java/org/apache/jk/tc32 j-t-c/jk/java/org/apache/jk/tc40 ( with conditional compilation to include only what you need ) Another module c

Re: Tomcat Security

On Fri, 11 May 2001, Benjamin Chad wrote: > Hi, > What security development still needs to be done on Tomcat? Depends on what you mean by "security" :-) If you're talking about authentication -> we need to better integrate tomcat with auth mechanisms in the web server ( that should be part of t

RE: problems running a servlet that uses core catalina classes

On Fri, 11 May 2001, Ted Neward wrote: > Glenn, just out of curiosity, how could someone create an "administrative" > web-app for controlling and administering Tomcat? (One of the things I've > been toying with was the idea of doing just such an "administrative" > interface--installing new webapp

Re: Class Reloading

On Fri, 11 May 2001, Craig R. McClanahan wrote: > Tomcat 4.0-beta-4 is also subject to the "...jsp%00" bug that Marc just > fixed in 3.2.2 (patch will be committed in a second). However, the more > serious issue is the introspection one (I can hear Costin laughing at me > from 600 miles away :-)

Re: Class Reloading

On Fri, 11 May 2001, Craig R. McClanahan wrote: > > The introspection problem is not very serious - it doesn't work if > > sandboxing is enabled ( at least from what I know - if it works then it's > > a very serious VM bug ). > > > > It doesn't work if you start Tomcat 4.0 with a security mana

Re: Class Reloading

On Sat, 12 May 2001, Glenn Nielsen wrote: > [EMAIL PROTECTED] wrote: > > > > If the security manager is not used everything has AllPermissions - the > > fact that someone can access the internal objects is quite small compared > > with the fact that it could call System.exit() and read/change an

Re: HTTP 1.1 in Tomcat

On Mon, 14 May 2001, Bruce Butterfield wrote: > What would be the major issue of adding HTTP 1.1 capability to Tomcat > 3.2.x? Our application uses Tomcat standalone because there is almost no > static content and thus using the Apache server seems superfluous. We > expose SOAP-like APIs to th

Re: [PROPOSAL AJP14] AJP13 Evolution

On Sun, 13 May 2001, kevin seguin wrote: > in the java side of ajp13, it is pretty much assumed that strings are > iso-8859-1 encoded. (i'm not sure how things that deal with > MessageBytes that come out of ajp13 deal with encoding...). MessageBytes is supposed to delay the conversion from byte

Re: configure for jakarta-tomcat-connectors

On Mon, 14 May 2001, jean-frederic clere wrote: > Hi, > > I have started a configure.in and makefile(s).in for the > jakarta-tomcat-connectors. Excelent ! > Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I > have some questions: > > - The idea is to have one co

Re: one session for many web sites

Salut Mihai, > How can I have the same session for many web sites? > > By default, for the first request tomcat creates a implicit session and > sends a cookie with domain=servername. What I wanna do is setting this > cookie for domain=partian domain name (like .kiki.ro) (that means this > cooki

Re: FORM implementation

On Fri, 11 May 2001, JULIEN,TIMOTHY (HP-NewJersey,ex2) wrote: > does Tomcat save header, cookie, and parameter (could be POST data) data > when doing FORM login? > AFAIK, tomcat 3.2 and 3.3 is saving only the query string. The code is in modules.aaa.AccessInterceptor ( for 3.3 ), tomcat.reque

Re: Jasper performance

> Jasper performance has already been identified as an area needing > improvement. > > Discussions and work on this has already started in the main tomcat > branch in CVS jakarta-tomcat/proposals/jasper34, but this may be > moving to the CVS repository jakarta-tomcat-jasper. > > This work just

Re: configure for jakarta-tomcat-connectors

Wow, it is so good to see development discussion on tomcat-dev, and be able to participate :-) I have a big question - what happens if configure/libtool is used and different options are given for mod_jk and apache ? I can't give a concrete example, but APXS had the big benefit that it "cached"

Re: web_app in jakarta-tomcat-connectors ?

On Tue, 15 May 2001, Pier P. Fumagalli wrote: > GOMEZ Henri at [EMAIL PROTECTED] wrote: > > > What about importing the mod_webapp code in > > jakarta-tomcat-connectors ? > > > > There is allready jk stuff (native, java), we could > > also have here a 'wa' subdir > > > > jakarta-tomcat-con

Re: [jakarta-tomcat-connectors] a dilemma ...

On Mon, 14 May 2001, kevin seguin wrote: > so, i'm looking at decoupling the Ajp13 java stuff from servlet > container code. > > some background... in tomcat 3, the ajp code takes a core tomcat Request > object and adds decoded information from the ajp request into the > Request object. when i

Re: configure for jakarta-tomcat-connectors

On Tue, 15 May 2001, jean-frederic clere wrote: > By the way I have a question: Why jk_jni_worker.c is in common not in jni? What > it is used for? (I have to add JAVA_HOME to the configure for it and I am > curious). Error - it shouldn't be in common... jk_jni_worker uses JNI to start tomcat i

Re: Jasper performance

On Tue, 15 May 2001, Glenn Nielsen wrote: > I would like to propose that the new Jasper require jdk 1.2. > The current version of jasper can be used by those who have jdk 1.1.x. > Then we don't have to worry about jumping through hoops trying to > get the new jasper to run both in 1.1 and 1.2, pl

RE: Java World Editors' Choice Awards

I'll be at Java One ( of course ) and looking forward to meet all of you. Marc did an amazing work - and I would be happy if he'll get the award for us ! :-) Costin

Re: Jasper performance

On Tue, 15 May 2001, Jon Stevens wrote: > on 5/15/01 7:05 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > On Tue, 15 May 2001, Glenn Nielsen wrote: > > > >> I would like to propose that the new Jasper require jdk 1.2. > >> The current version of jasper can be used by those who have jdk

  1   2   3   4   5   6   7   8   9   >