[
https://issues.apache.org/jira/browse/WICKET-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Compagner closed WICKET-2221.
-----------------------------------
Resolution: Won't Fix
This wont change.
internalInit needs that parameter, and internal init needs to be before init so
there is just no other way
override the getConfigurationType() yourself and do there your stuff
> Application.getConfigurationType() is called before Application.init()
> ----------------------------------------------------------------------
>
> Key: WICKET-2221
> URL: https://issues.apache.org/jira/browse/WICKET-2221
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.5
> Reporter: Alex
>
> We've run into an issue where the configuration type (i.e. DEPLOYMENT /
> DEVELOPMENT) was computed in the Application.init() based on the
> ServletContext attributes. Unfortunately the getConfigurationType() method
> requesting the type was called from the internalInit() method before init had
> a chance to compute the correct value. What was worse though is that
> getConfigurationType() was called again later and Wicket printed that it was
> running in the DEPLOYMENT mode when it was not ! The ModificationWatcher was
> started based on the "uninitialized" value of the configuration type.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
