Setting Wicket Configuration Mode to Deployment

[David Beer <da...@gmail.com>]

Hi All

I am applying the final touches to my application before going to
staging/production. I use the Webservlet 3 process via java code and
annotations for setting the Wicket Filter all works well. I am trying to
add the init param for the configuration mode.

I was hoping I could use maven filtering to filter the value in the java
file but this seems awkward and not really possible.

So I tried setting it by reading a properties file in the WicketApplication
class and setting the value in the init() method, however I got an
exception saying the value can only be set once.

It seems the WicketFilter class sets this by default to development and
unless overridden in the annotations doesn't seem like it can be set.

Is this correct behaviour, what is the best way to set the value at build
time? I am using wicket 7.9.0.

Thanks

David

Re: Setting Wicket Configuration Mode to Deployment

[Sven Meier <sv...@meiers.net>]

Hi,

changing the configuration type in #init() is too late, as it was 
already decided by the application at that point of time.

You can:

- override #getConfigurationType()

- set the type into system-properties/filter-init-param/context-param 
before the application is created.

Have fun
Sven


Am 17.11.2017 um 20:02 schrieb David Beer:
> Hi All
>
> I am applying the final touches to my application before going to
> staging/production. I use the Webservlet 3 process via java code and
> annotations for setting the Wicket Filter all works well. I am trying to
> add the init param for the configuration mode.
>
> I was hoping I could use maven filtering to filter the value in the java
> file but this seems awkward and not really possible.
>
> So I tried setting it by reading a properties file in the WicketApplication
> class and setting the value in the init() method, however I got an
> exception saying the value can only be set once.
>
> It seems the WicketFilter class sets this by default to development and
> unless overridden in the annotations doesn't seem like it can be set.
>
> Is this correct behaviour, what is the best way to set the value at build
> time? I am using wicket 7.9.0.
>
> Thanks
>
> David
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org