ICEpdf
  1. ICEpdf
  2. PDF-455

Verbose logging when parsing hex strings

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.3.3
    • Fix Version/s: 4.3.4
    • Component/s: Core/Parsing
    • Labels:
      None
    • Environment:
      any

      Description

      During the QA test cycle for 4.3.3 I noticed a lot of of logging noise coming out of HexStringObject. This bug is to mark that someone needs to review this code and see why it's so noisy.

        Activity

        Patrick Corless created issue -
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #30902 Tue Sep 18 09:47:02 MDT 2012 patrick.corless PDF-455 lower the logging noise when a name and hexString encounter an error from warning to finner.
        Files Changed
        Commit graph MODIFY /icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/HexStringObject.java
        Commit graph MODIFY /icepdf/trunk/icepdf/core/src/org/icepdf/core/pobjects/Name.java
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #30903 Tue Sep 18 09:47:46 MDT 2012 patrick.corless PDF-455 lower the logging noise when a name and hexString encounter an error from warning to finner
        Files Changed
        Commit graph MODIFY /icepdf/branches/icepdf-4.3.3/icepdf/core/src/org/icepdf/core/pobjects/HexStringObject.java
        Commit graph MODIFY /icepdf/branches/icepdf-4.3.3/icepdf/core/src/org/icepdf/core/pobjects/Name.java
        Hide
        Patrick Corless added a comment - - edited

        Changed the log level from warning to finer to avoid quite a bit of noise when parsing out hex values in both the Name and HexStringObject classes. The warning message have been causing some confusion when seen by users. Basically the errors in this case should shouldn't be reported back to the general log as they aren't actually causing any problems.

        Show
        Patrick Corless added a comment - - edited Changed the log level from warning to finer to avoid quite a bit of noise when parsing out hex values in both the Name and HexStringObject classes. The warning message have been causing some confusion when seen by users. Basically the errors in this case should shouldn't be reported back to the general log as they aren't actually causing any problems.
        Hide
        Patrick Corless added a comment - - edited

        Update the trunk and the 4.3.3 branch accordingly.

        Show
        Patrick Corless added a comment - - edited Update the trunk and the 4.3.3 branch accordingly.
        Migration made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Patrick Corless made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Patrick Corless
            Reporter:
            Patrick Corless
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: