Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 57340 invoked from network); 11 Nov 2002 07:48:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Nov 2002 07:48:23 -0000 Received: (qmail 27513 invoked by uid 97); 11 Nov 2002 07:49:21 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 27468 invoked by uid 97); 11 Nov 2002 07:49:20 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 27453 invoked by uid 98); 11 Nov 2002 07:49:19 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <00a601c28957$a2ae7ee0$d2b32b04@dslverizon.net> From: "Bill Barker" To: "Tomcat Developers List" References: <3DCF43C3.9080904@mail.more.net> Subject: Re: JSPC refactoring/documentation Date: Sun, 10 Nov 2002 23:54:58 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archived: msg.XXCfyOIa@sneezy X-Scanned-By: MIMEDefang 2.11 (www dot roaringpenguin dot com slash mimedefang) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Glenn Nielsen" To: Sent: Sunday, November 10, 2002 9:44 PM Subject: JSPC refactoring/documentation > Based on problems reported by users of JSPC Remy made a proposal > to deprecate it. > > This resulted in a number of people responding that they used JSPC > and strongly felt it should be kept. > > There did seem to be some consensus that JSPC could beneifit from > a review and refactoring to make it easier to use. > > It could also benefit from better documentation if it is to remain > part of Tomcat. > > Perhaps those who so strongly support JSPC should take the lead to > review, refactor, simplify, and better document JSPC. Perhaps a > JSPC-HOWTO for the Tomcat docs once the refactoring is completed? > > > This could be part of a Tomcat 4.2 development effort. > There has been some discussion about other possible new features. > > Some new features/changes that have been discussed: > > A SecurityManager XML Policy file that allows secure delegation > to web applications for setting their own policies (within a sandbox). > > Using JMX to instrument Tomcat for production runtime monitoring. > > Possibly a JSPC refactoring. > > Audit the SecurityManager web application sandbox. > > Are there other changes/features that could be part of Tomcat 4.2 development? > >From previous posts, I gather that Remy isn't interested in RMing a 4.2 release. Unless Remy jumps in and tells me that I don't know what I'm talking about :), the biggest change would be to find someone to volunteer to RM it. Once I have my webapps working with 4.1 (the hold-up is basically porting custom Realm stuff at the moment), I'm sure I'll have a wish-list ;). > I have a laundry list of smaller issues I would like to address. Nothing major. > > Regards, > > Glenn > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: