IMO I like it the way it is because it makes it very simple to change
it at runtime... in your case you simply run jety, adding a param tot
eh comamnd line: eg.
java -Dwicket.configuration=deployment com.jetty.Start
I can do that easily at any time and reconfigure things on various
servers to get what I need... if I did that in code, I'd still have to
have some sort of switch to put it onto dev or prod mode... so why
bother?
- Brill Pappin
On 24-Feb-09, at 7:35 AM, Eyal Golan wrote:
Hi,
It's been a long time since I've written in this mailing list.
Here's my question:
I was looking for a way to set the mode to DEVELOPMENT in the Jetty
starter
while setting DEPLOYMENT in the web.xml.
I encountered the following thread:
http://www.nabble.com/dummy-question%2C-how-to-set-wicket-in-Deloyment-mode--td13364304.html#a13364498
In there there is this line:
System.setProperty("wicket.configuration", "development");
I am using Wicket 1.3.4
Wicket Application class has a static filed called CONFIGURATION,
which is
without the 'wicket' part.
Why doesn't it have a static 'wicket.configuration' ?
Wouldn't it be better?
Thanks
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really
necessary
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
