Uploaded image for project: 'Log4cxx'
  1. Log4cxx
  2. LOGCXX-22

Backslashes in filenames in XML config of FileAppender broken

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.9.7
    • Fix Version/s: 0.10.0
    • Component/s: Appender
    • Labels:
      None

      Description

      Backslashes in filenames in XML config files for FileAppenders are treated as escape characters which I thinkm but haven't confirmed, is inconsistent with log4j. Using forward slashes or double backslashes can work around the problem, but the double backslashes will no longer work after the problem is resolved.

        Activity

        Hide
        carnold@apache.org Curt Arnold added a comment -
        Show
        carnold@apache.org Curt Arnold added a comment - Actual log4j bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=22894
        Hide
        carnold@apache.org Curt Arnold added a comment -

        Related log4j bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=33485

        With the 10 Feb 2005 patch, log4cxx no longer treats \ as a special character in XML configuration files. Two compensations were added to preserve compatibility with existing configurations, FileAppender::setOption will eliminate double backslashes from any specified file name and PatternLayout::setOption will process patterns with OptionConverter::convertSpecialCharacters.

        With the patch, log4cxx's behavior is no longer compatible with log4j, but hopefully log4j will come into synch.

        Show
        carnold@apache.org Curt Arnold added a comment - Related log4j bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=33485 With the 10 Feb 2005 patch, log4cxx no longer treats \ as a special character in XML configuration files. Two compensations were added to preserve compatibility with existing configurations, FileAppender::setOption will eliminate double backslashes from any specified file name and PatternLayout::setOption will process patterns with OptionConverter::convertSpecialCharacters. With the patch, log4cxx's behavior is no longer compatible with log4j, but hopefully log4j will come into synch.
        Hide
        carnold@apache.org Curt Arnold added a comment -

        The CVS HEAD also appears to have an issue if a drive designator other the the current default drive is used in the filespec.

        Show
        carnold@apache.org Curt Arnold added a comment - The CVS HEAD also appears to have an issue if a drive designator other the the current default drive is used in the filespec.

          People

          • Assignee:
            carnold@apache.org Curt Arnold
            Reporter:
            carnold@apache.org Curt Arnold
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development