myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Sullivan (JIRA)" <>
Subject [jira] Updated: (TRINIDAD-1795) Agent version support in JIRA-1547 broke CSS hashcode
Date Thu, 22 Apr 2010 03:10:53 GMT


Blake Sullivan updated TRINIDAD-1795:

           Status: Resolved  (was: Patch Available)
    Fix Version/s: 1.2.14-core 
       Resolution: Fixed

Fixed in revision 936602
Fixed in 1.2.x revision 936601
Fixed in Trunk 936599

> Agent version support in JIRA-1547 broke CSS hashcode
> -----------------------------------------------------
>                 Key: TRINIDAD-1795
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.2.13-core , 1.2.14-core ,
>         Environment: All
>            Reporter: Blake Sullivan
>            Assignee: Blake Sullivan
>             Fix For: 1.2.14-core ,
>         Attachments: JIRA_1795_1_2_12_2.patch, JIRA_1795_1_2_x.patch, JIRA_1795_main.patch
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> The Agent Version support uses the hash code of enums as part of its hash code.  Since
the enum hash code is based on the memory address of the enum, this causes the hash code on
the cached css file to change every time the server is restarted even if the css file itself
did not change.  The result is the user agent pull new copies of the CSS file more often than
> The solution is to use the hash code of the enum's name instead, which is stable.
> Doing so I now see the same hash code ( "d8dxpq" in the case of the rich client fusion
skin on JSF2) across runs rather than different values("iyn8lw" and "idkr6t") like I did before

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message