[
https://issues.apache.org/jira/browse/WICKET-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115582#comment-13115582
]
Igor Vaynberg commented on WICKET-4088:
---------------------------------------
right. but what specifically? and if you are looking for something "last" why
not put it into application's init()?
i am rather wary of introducing any kind of ordering into this. iinitializers
are meant to be standalone and do things orthogonal to other iinitializers.
creating dependencies between them is a bad idea as they are not easily
controlled since they rely on classpath ordering, etc.
also introducing an ordering means introducing a reverse-ordering for
idestroyers. unless i hear a very convincing usecase for this im -1.
> 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
