Luis Bernardo commented on FOP-2307:

The original issue does not happen in current trunk due to changes to 
CommonBorderPaddingBackground.equals(), which now, incorrectly, compares two 
colors by comparing that they are the same instance. This effectively disables 
caching since a cached color property will be replaced by a new instance of the 
same color (whether that has practical performance implications is another 

> Weird border color inheritance (hashCode collisions)
> ----------------------------------------------------
>                 Key: FOP-2307
>                 URL: https://issues.apache.org/jira/browse/FOP-2307
>             Project: Fop
>          Issue Type: Bug
>          Components: renderer/pdf
>    Affects Versions: 1.1
>         Environment: Windows 7/64-bit, Oracle JDK 7.0.45 64-bit
>            Reporter: Jan Tošovský
>              Labels: border, cmyk, color
> 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

This message was sent by Atlassian JIRA

Reply via email to