Uploaded image for project: 'FOP'
  1. FOP
  2. FOP-2307

[PATCH] Weird border color inheritance (hashCode collisions)

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 2.2
    • Component/s: renderer/pdf
    • Labels:
    • Environment:
      Windows 7/64-bit, Oracle JDK 7.0.45 64-bit

      Description

      When I define an object with a specific border and the thickness of this border matches with the one defined in the static-content, the latter color is used instead. But it appears only if my object color is specified using the pseudo #CMYK profile.

      It can be tested with this simplified test case:
      http://drifted.in/other/_border.fo
      http://drifted.in/other/_border.pdf

      The first object border uses the standard color so it is unaffected.
      The second is affected.
      The third uses a different thickness (3.5pt instead of 2.5) so it is also unaffected.

      In the generating log there are lot of following hashCode collisions so I suppose it relates together:

      X 23, 2013 5:09:34 ODP. org.apache.fop.fo.properties.PropertyCache fetch
      INFO: 60 hashCode() collisions for org.apache.fop.fo.properties.ColorProperty
      X 23, 2013 5:09:34 ODP. org.apache.fop.fo.properties.PropertyCache fetch
      INFO: 70 hashCode() collisions for org.apache.fop.fo.properties.ColorProperty

        Attachments

        1. fop-2307.patch
          0.9 kB
          Alexios Giotis
        2. FOP-2307-NOT_FOR_COMMIT.patch
          0.7 kB
          Alexios Giotis

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jan.tosovsky.cz Jan Tošovský
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: