Hi,
On Tue, May 12, 2015 at 6:48 PM, Christopher Merrill
ch...@webperformance.com wrote:
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
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
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
(Is this the right place for this question? Should I raise an issue on
WicketStuff instead?)
Curious to see if anyone is doing this and what your level of success is?
I ask because we have a Wicket/GAE app that we recently moved up to Wicket
6 and we're experiencing a lot of spontaneous
