, i tried to dig the code, but haven't found a way
submitButton = new Button(button.send,new
that the button needs to be handled in a special way,
is there maybe a way to improve this, or am i doing something wrong?
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Johan Compagner schrieb:
why aren't you subclassing button and have a button that has that
modifier and use that one on all your forms?
doh! thanks, i haven't seen that obvious possibility
..is it right, to check wether the button is enabled in the
onComponentTag event before putting the
Thanks in advance
View this message in context:
Sent from the Users forum mailing list archive at Nabble.com
thanks for you quick replies! I will create the quick start and attach it to a
Thanks to your hint Martin, for the moment I will use jQuery#replaceWith() to
make sure my app runs as expected.
Am 14.05.2013 um 16:56 schrieb Martin Grigorov-4 [via Apache Wicket
replaceWith is now the standard replacement.
Will this appear in Wicket 6.9.0?
Am 28.05.2013 um 21:12 schrieb Maxim Solodovnik [via Apache Wicket]:
I also saw this behavior using 6.8.0
The component with additional
I've had excellent results with Glassfish. The login server for the MMO I
worked on (swtor.com) has been benchmarked at 32,000 logins per second on a 8
CPU machine. The maximum throughput on a simple servlet (nothing dynamic
though, just static data), was benchmarked at around 70k.
Hmmm, does that imply that one of the member variables may be Serializable?
On 25 Apr 2010, at 05:18, Igor Vaynberg wrote:
the exception might have caused your page to not be serialized
properly into the pagestore
On Sat, Apr 24, 2010 at 6:06 PM, Douglas Ferguson
I can assure you that there are no apparent problems/conflicts in using
EclipseLink alongside Wicket. I'm doing it constantly :)
It is likely that there is an issue with how your IDE is setup or packages the
files. Some tools write their own META-INF directory in a war instead of using
On 10/3/2010 1:35 PM, Eike Kettner wrote:
Just want to mention that with this change in wicket 1.5, wicket cannot
be used in OSGi environments as easiliy as wicket 1.4. One usually has
to create a wrapped jar somehow. Maybe this is worth to mention on the
migration guide wiki page?
Mail list logo