[
https://issues.apache.org/jira/browse/WICKET-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115273#comment-13115273
]
Emond Papegaaij commented on WICKET-4088:
-----------------------------------------
AbstractClassResolver tries 3 different classloaders. Starting with the
classloader for Application, followed by the classloader for your application,
followed by the context classloader (or a custom classloader, if a different
subclass of AbstractClassResolver is used). IMHO, the last should always be the
most specific, and it's an ideal location to perform some additional
configuration that depends on the configuration set by the other initializers.
> 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
