[OT] Configure wicket.configuration outside web.xml in Tomcat 6

[Mike Mander <wi...@gmx.de>]

Hi,

i'm trying to configure my wicket.configuration property without adding 
it to web.xml. I use tomcat 6.
Adding wicket.configuration=deployment in 
CATALINA_HOME/conf/catalina.properties was not working.
App starts in development mode (after tomcat restart / param not present 
in web.xml). Adding the property to command line is only the last option 
for me. Because i'm stupid i bet i will forget it somewhere :-).

Background is: If i add the property to web.xml
a) i have to change it for all production apps on server
b) and i have to deploy all apps twice in production. Firstly with the 
"default" configured web.xml (development) and then hotdeploy with the 
changed web.xml (deployment).

This leads often to perm gen space which is another problem (I know it 
and it's not part of this problem :-).

Maybe someone has a good plan on this issue.

Thanks
Per

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

Re: [OT] Configure wicket.configuration outside web.xml in Tomcat 6

[Mike Mander <wi...@gmx.de>]

Thanks Bas,

you solved my problem. I don't use tomcat within eclipse. I use the 
standard jetty server with Start class. I wasn't clear at this point.

But you brought me the light. I set "deployment" as 
configuration-param-value to my web.xml. And in Start class i set the 
system property "wicket.configuration" to "development". And it works.

Thanks and Cheers
Per

Am 04.07.2011 12:56, schrieb Bas Gooren:
> Hi,
>
> As suggested on the mailing list once, what I've been using for a 
> while now is having "deployment" in web.xml, and adding 
> -Dwicket.configuration=development to my tomcat command line from 
> Eclipse.
>
> This way you always package a production-ready jar/war/ear and can run 
> in development mode locally.
>
> Bas
>
> Op 4-7-2011 9:46, schreef Mike Mander:
>> Hi,
>>
>> i'm trying to configure my wicket.configuration property without 
>> adding it to web.xml. I use tomcat 6.
>> Adding wicket.configuration=deployment in 
>> CATALINA_HOME/conf/catalina.properties was not working.
>> App starts in development mode (after tomcat restart / param not 
>> present in web.xml). Adding the property to command line is only the 
>> last option for me. Because i'm stupid i bet i will forget it 
>> somewhere :-).
>>
>> Background is: If i add the property to web.xml
>> a) i have to change it for all production apps on server
>> b) and i have to deploy all apps twice in production. Firstly with 
>> the "default" configured web.xml (development) and then hotdeploy 
>> with the changed web.xml (deployment).
>>
>> This leads often to perm gen space which is another problem (I know 
>> it and it's not part of this problem :-).
>>
>> Maybe someone has a good plan on this issue.
>>
>> Thanks
>> Per
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>


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

Re: [OT] Configure wicket.configuration outside web.xml in Tomcat 6

[Bas Gooren <ba...@iswd.nl>]

Hi,

As suggested on the mailing list once, what I've been using for a while 
now is having "deployment" in web.xml, and adding 
-Dwicket.configuration=development to my tomcat command line from Eclipse.

This way you always package a production-ready jar/war/ear and can run 
in development mode locally.

Bas

Op 4-7-2011 9:46, schreef Mike Mander:
> Hi,
>
> i'm trying to configure my wicket.configuration property without 
> adding it to web.xml. I use tomcat 6.
> Adding wicket.configuration=deployment in 
> CATALINA_HOME/conf/catalina.properties was not working.
> App starts in development mode (after tomcat restart / param not 
> present in web.xml). Adding the property to command line is only the 
> last option for me. Because i'm stupid i bet i will forget it 
> somewhere :-).
>
> Background is: If i add the property to web.xml
> a) i have to change it for all production apps on server
> b) and i have to deploy all apps twice in production. Firstly with the 
> "default" configured web.xml (development) and then hotdeploy with the 
> changed web.xml (deployment).
>
> This leads often to perm gen space which is another problem (I know it 
> and it's not part of this problem :-).
>
> Maybe someone has a good plan on this issue.
>
> Thanks
> Per
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>