From: fhanik <fhanik@13f79535-47bb-0310-9956-ffa450edef68>
Date: Thu, 11 Oct 2007 15:35:33 +0000 (+0000)
Subject: Proposal for a generic way of setting attributes, letting the components decide if... 
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=d87b27068ffee7d9c5e10e6b8a311bbc47b9f064;p=tomcat7.0

Proposal for a generic way of setting attributes, letting the components decide if a warning should be issued or not by implementing 'boolean setProperty' instead of 'void setProperty'.
The old way, 'void setProperty' is still backwards compatible, and its behavior has not changed.



git-svn-id: https://svn.apache.org/repos/asf/tomcat/tc6.0.x/trunk@583853 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/STATUS b/STATUS
index 9ea00d8df..989670a6d 100644
--- a/STATUS
+++ b/STATUS
@@ -38,8 +38,16 @@ PATCHES PROPOSED TO BACKPORT:
 * Call StopAwait at StandardServer.stop as port==-1
   +1: pero
   -1: remm (would like clarification on the sleep value, currently 100s)
-
+  -1: No link to proposed fix given.
+  
 * Arrange doc of connectors.
   http://people.apache.org/~jfclere/patches/tc.docs.patch
   +1: jfclere, remm
   -1:
+
+* Make server.xml parsing warnings more generic, add support for the NIO connector
+* Connector is no longer an exception case. Any new component can still use setProperty and return a boolean 
+* to accept or reject the property
+  http://people.apache.org/~fhanik/patches/digester-attribute-warnings.patch
+  +1: fhanik
+  -1: