So wicket-extensions shouldnt be used for dates now?
If so, how can I pursuade the DateTextField from there to use a long
(classic unix timestamp) instead of a Date inside a model? (without
overiding getModelObject/ setModelOject as its an inner class and I cant
have the model beeing final?)
e.g.:
public static class LongDateTextFieldEditor extends Fragment {
public LongDateTextFieldEditor(String id, IModel model,
IModel labelModel, final String pattern) {
super(id, "dateEditor");
add(new Label("label", labelModel));
add(new DateTextField("edit", model, new
PatternDateConverter(pattern, false)).add(new DatePicker()));
}
}
model.getModelObject here just returns 124922732 (long unix timestamp)
Best Regards,
Korbinian
PS: does wicket-datetime somehow depend on yoda-time? sorry, for asking
but I'm bit confused lately with the Date/ Locale/ pattern/ long chaos
in Java
Eelco Hillenius schrieb:
On 9/7/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 9/8/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:
DateLabel component, however I cannot find it in my version of wicket.
Add wicket-extensions to your project.
Nope, add wicket-datetime.
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
