You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2007/04/12 16:04:17 UTC

DO NOT REPLY [Bug 42099] New: - ExpressionFilter backport

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42099>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42099

           Summary: ExpressionFilter backport
           Product: Log4j
           Version: 1.3alpha
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: carnold@apache.org


This enhancement extracts the org.apache.log4j.filter.ExpressionFilter and o.a.l.filter.LocationInfoFilter 
from log4j 1.3 and adapts it to work with log4j 1.2.  The initial goal is to support Chainsaw on log4j 1.2, 
however hopefully the resulting package can be used by log4j 1.2.x users who would like to use the 
ExpressionFilter.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


DO NOT REPLY [Bug 42099] - ExpressionFilter backport

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42099>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42099


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From carnold@apache.org  2007-04-12 15:30 -------
Should be functional at the writing.  Can be checked out from:

svn co https://svn.apache.org/repos/asf/logging/sandbox/log4j/expression-filter

Maven build will use log4j-1.2.14.jar (which it will download if it hasn't already).  Put a recent Maven 2 on 
path and do:

mvn package : to build jar
mvn site        : to build documentation
mvn install    : to add to local Maven repo   

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


DO NOT REPLY [Bug 42099] - ExpressionFilter backport

Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42099>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42099





------- Additional Comments From carnold@apache.org  2007-08-15 15:21 -------
Committed changes in rev 566357 that migrates the ExpressionFilter from Jakarta ORO to 
java.util.regex that was introduced in JDK 1.4.  The change should be transparent unless you used 
pattern delimiters in filters like:

MSG LIKE /.*foo/

instead of just writing:

MSG LIKE .*foo

If that level of compatibility is needed, identical bracketing characters could be detected and the rule 
could return true if either the straight pattern or the pattern with bracketing characters removed 
matched the field.  However, since ExpressionFilter was introduced in log4j 1.3, I don't feel the need for 
that level of compatibility unless it that was known to be used in the field.  Feedback appreciated.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org