Re: Google AppEngine Initializer and Wicket 6?

2015-05-12 Thread Martin Grigorov
Hi, This is the way wicketstuff-gae-initializer works since its day 1. Branch 1.5.x also uses IInitializer: https://github.com/wicketstuff/core/blob/7c2a78df17674b3eff9503a8d3afae2fa8622176/jdk-1.5-parent/gae-initializer-parent/gae-initializer/src/main/resources/wicket.properties AFAIK there were

Re: Drop Down Choice default value

2015-05-12 Thread Chris
Marcel, Sven, thanks a lot for your answers! Chris Am 12.05.2015 um 15:24 schrieb Marcel Barbosa Pinto marcel.po...@gmail.com: Another way is to provide a value on your .properties file. For instance: nullValid=Please choose myFieldId.nullValid=Please choose a value for ${label}

Re: Drop Down Choice default value

2015-05-12 Thread Sven Meier
Hi, you have to override #getNullValidDisplayValue(), #getNullKeyDisplayValue() is for cases where null is *not* valid. Regards Sven On 12.05.2015 12:44, Chris wrote: Hi all, I have a Drop down choice field and would like to override the default select value. I have made following

Drop Down Choice default value

2015-05-12 Thread Chris
Hi all, I have a Drop down choice field and would like to override the default select value. I have made following settings but the default value is empty. Is there sth missing? setNullValid(true); @Override protected String getNullKeyDisplayValue() { return Please choose; } Thanks, Chris

Initializer problem - resources not being loaded

2015-05-12 Thread mscoon
Hi all, We have a web application which is using an internal library called wicket-sol. The library is installed in our local maven repository. wicket-sol contains a property file wicket.properties which has a single entry: initializer=gr.sol.wicket.Initializer The gr.sol.wicket.Initializer

Re: Drop Down Choice default value

2015-05-12 Thread Marcel Barbosa Pinto
Another way is to provide a value on your .properties file. For instance: nullValid=Please choose myFieldId.nullValid=Please choose a value for ${label} On Tue, May 12, 2015 at 8:26 AM, Sven Meier s...@meiers.net wrote: Hi, you have to override #getNullValidDisplayValue(),

Re: Initializer problem - resources not being loaded

2015-05-12 Thread Sven Meier
Hi, if the problematic dev machine produces a war (via maven), and the war is deployed to our test server, the initializer is again never loaded. Wars built from other machines work fine. mh, sounds like a build problem. Do you have a broken wicket-sol artefact in your local maven

Re: Initializer problem - resources not being loaded

2015-05-12 Thread mscoon
You are actually right Sven. It is a broken pom.xml that causes the wicket.properties file to not be included in the jar file. And a broken build process that hides the problem in pom.xml in most dev machines. Apologies for bothering the list with an irrelevant issue... On Tue, May 12, 2015 at

Re: Google AppEngine Initializer and Wicket 6?

2015-05-12 Thread Christopher Merrill
Thanks for responding, Martin. I have found only one error in the AppEngine logs - that was for the #3 that I mentioned above - there is a Wicket error in the logs that says a button is not enabled. It appears when I click the button (which had been previously enabled via an Ajax event). Other