[jira] [Commented] (WICKET-6362) HeaderItems with different PageParameters are treated as identical

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007010#comment-16007010 ] 

ASF subversion and git services commented on WICKET-6362:
---------------------------------------------------------

Commit 47aa1461d58b9a5660fc11032db952ce4df36a33 in wicket's branch refs/heads/master from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=47aa146 ]

WICKET-6362 HeaderItems with different PageParameters are treated as identical

Implement proper #equals() and #hashCode() for all HeaderItems


> HeaderItems with different PageParameters are treated as identical
> ------------------------------------------------------------------
>
>                 Key: WICKET-6362
>                 URL: https://issues.apache.org/jira/browse/WICKET-6362
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.5.0, 8.0.0-M5
>            Reporter: Boris Goldowsky
>            Assignee: Martin Grigorov
>            Priority: Minor
>
> Given code like the following, where same ResourceReference is used for both resources but they have different PageParameters and different IDs, only one of them actually gets rendered in the page head:
> {code}
> public void renderHead(IHeaderResponse response) {
>     …
>     response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters1, “id1”));
>     response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters2, “id2”));
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)