[
https://issues.apache.org/jira/browse/WICKET-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117438#comment-13117438
]
Igor Vaynberg commented on WICKET-4088:
---------------------------------------
initializers are there to synchronize certain things between application nodes.
for example, it gives libraries a way to set up shared resources, etc. they are
not really there to "configure" the application. i consider the current case of
wiquery setting something like that a misuse of the initializer. we will change
the order in 1.6.0.
> Make Application#init() run after IInitializers to allow the application to
> override any settings configured by initializers
> ----------------------------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 1.6.0
>
>
> 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
