Re: Wicket 8 migration / header contributions question

[Tobias Gierke]

Hi,
Hi,
this should be caused by WICKET-6498. This issue has changed the 
behavior for HeaderResponseDecorator. You can find how to adapt your 
code in the migration guide or in the release note of Milestone 9:

https://wicket.apache.org/news/2018/02/17/wicket-8.0.0-M9-released.html

Thanks for the quick response! I already tried this and it didn't have 
any effect :/

My Application#init() method is doing:

setHeaderResponseDecorator( response ->new ResourceAggregator(new 
FilteringHeaderResponse(response) ) );



Cheers,
Tobias