[
https://issues.apache.org/jira/browse/WICKET-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117033#comment-13117033
]
Emond Papegaaij commented on WICKET-4088:
-----------------------------------------
It is not that is causing problems. We want to set a custom header response
decorator, based on the one WiQuery uses, but as I said, the application.init
runs first. So if I set it in init, it will get overridden by the WiQuery
initializer. You cannot override the initializers from application.init, it is
the other way around. Perhaps, these methods should be swapped, but that a
breaking change, because the outcome may no longer be the same. For now, we've
put the code in validateInit, but I consider that a hack.
> IInitializers are executed out-of-order
> ---------------------------------------
>
> Key: WICKET-4088
> URL: https://issues.apache.org/jira/browse/WICKET-4088
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.18, 1.5.0
> Reporter: Emond Papegaaij
> Priority: Minor
>
> wicket.properties urls are added to an HashSet, causing the IInitializers to
> be loaded in random order. In AbstractClassResolver.getResources, the HashSet
> should be changed to a LinkedHashSet.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
