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/08/16 00:21:06 UTC
DO NOT REPLY [Bug 42099] - 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
------- 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