We use DateTime/LocalDate in our entities as well. It's easy enough to roll your own form components.
See the patch and zip file attached to this issue, you can probably just put those classes in your own project and run with it. https://issues.apache.org/jira/browse/WICKET-466 The patch is meant to handle java.util.Date, and Joda DateTime and LocalDate all at the same time. Now that Wicket FormComponents are generic though, I think it's better to just have separate FormComponents and Converters for each class. Ned Collyer wrote: > > Its a requirement for me that my domain entities have DateTime. > > I'd like to use wicket-datetime (as described here) > http://www.nabble.com/my-domain-model-and-Joda-Time-td15660961.html#a15660961 > > I can see its internals are all DateTimey which is AWESOME!! > > What is the easiest / quickest way of getting this stuff to work with > DateTime in my domain model. > > I'm running 1.4m1. > > What I'm toying with is compiling the project and applying the patch from > http://issues.apache.org/jira/browse/WICKET-466 > > But I'd rather have a simpler way - eg, extend or reimplement a class. > -- View this message in context: http://www.nabble.com/How-can-I-use-the-wicketdate-time-stuff-with-DateTime-on-my-model--tp19872583p19911816.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]