The default is now deployment because you can use a System property:
String configuration = System.getProperty("wicket." + Application.CONFIGURATION );
// If no system parameter check servlet specific <init-param>
if (configuration == null)
{
configuration = wicketServlet.getInitParameter(Application.CONFIGURATION );
}
// If no system parameter and not <init-param>, than check <context-param>
if (configuration == null)
{
configuration = wicketServlet.getServletContext ().getInitParameter(Application.CONFIGURATION);
}
// Deployment mode is default if not settings have been found
if (configuration != null)
{
configure(configuration, wicketServlet.getInitParameter("sourceFolder"));
}
else
{
configure(Application.DEPLOYMENT, wicketServlet.getInitParameter("sourceFolder"));
}
So you don't have to configure anything for deployment and if you develop then you can say that with a
system property so no configuration files needs to be updated for a WAR build.
If we make the default development then the system property doesn't make much sense i am affraid
because setting a system property for deployment is a bit strange.
johan
On 1/20/06, Igor Vaynberg <
[EMAIL PROTECTED]> wrote:
whenever there is an exception i always get the internal error page now instead of the exception page.
-Igor
