yeah, it does seem inconsistent :|
will have to think about this some more. on the first glance field.key
seems ok and personally i do not mind going back to it but i need to
search back through the archives and reread the threads that affected
this change in the first place if i can find them
Igor Vaynberg schrieb:
yeah, it does seem inconsistent :|
will have to think about this some more. on the first glance field.key
seems ok and personally i do not mind going back to it but i need to
search back through the archives and reread the threads that affected
this change in the first
Major Péter schrieb:
Dear Igor
referring to your comment on
https://issues.apache.org/jira/browse/WICKET-2350
where it reads: the proper format of the override key is
formid.componentid.key, you are missing the formid part. this was
considered a bug in earlier versions of wicket and was
done:
https://issues.apache.org/jira/browse/WICKET-2350
2009-06-30 02:32 keltezéssel, Igor Vaynberg írta:
open a jira issue with a quickstart attached.
-igor
2009/6/29 Major Pétermajorpe...@sch.bme.hu:
Hi all,
I have recently upgraded my application to wicket 1.4-rc5, and now I have
some
Hi all,
I have recently upgraded my application to wicket 1.4-rc5, and now I
have some troubles with the localization.
With the previous 1.3.6 release I was capable to restrict a localization
message for a validation to only one wicket id e.g. :
in foobar.java
RequiredTextField nameTF = new
open a jira issue with a quickstart attached.
-igor
2009/6/29 Major Péter majorpe...@sch.bme.hu:
Hi all,
I have recently upgraded my application to wicket 1.4-rc5, and now I have
some troubles with the localization.
With the previous 1.3.6 release I was capable to restrict a localization
