header item uniqueness

[Boris Goldowsky]

I have a situation like this:

public void renderHead(IHeaderResponse response) {
    …
    response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters1, 
“id1”));
    response.render(JavaScriptHeaderItem.forReference(resRef, pageParameters2, 
“id2”));
}

where same ResourceReference is used for both resources – the different page 
parameters point it to different actual Resources.

However, the check for uniqueness of header items seems to consider them equal, 
despite the different PageParameters and different IDs, and only one of them 
actually gets rendered in the page head.

Is this a bug, or is there a way to force the two items to both be included?

I’m using Wicket 7.5.0.

Boris