What we actually want to do is, to use the regular converter for Date.class
with a small addition.
The converter uses a DateFormat. We want to set this DateFormat:
setLenient(true).
I thought to put it in the application scope as we want this everywhere in
the application.
Following this thread, I
problem is datetextfield suppports different formats which require
different converters, so it is a bit of a special case with regard to
using a global date converter.
-igor
On Thu, May 7, 2009 at 11:16 AM, Eyal Golan wrote:
> "if you want to use your own converter then override getconverter() a
"if you want to use your own converter then override getconverter() and
return whatever you like."
True. This is what I suggested my mate when we discussed it. And I guess
this what we'll do.
But isn't using a converter for the whole application eliminates the need to
create a custom component?
T
if you want to use your own converter then override getconverter() and
return whatever you like.
-igor
On Thu, May 7, 2009 at 1:38 AM, Eyal Golan wrote:
> I'm going to review on Sunday the code my team mate has made .
> I'll be able to give you more information and see if maybe we misunderstood
I'm going to review on Sunday the code my team mate has made .
I'll be able to give you more information and see if maybe we misunderstood
something.
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't p
we looked the one from wicket-extensions
Eyal Golan
egola...@gmail.com
Visit: http://jvdrums.sourceforge.net/
LinkedIn: http://www.linkedin.com/in/egolan74
P Save a tree. Please don't print this e-mail unless it's really necessary
On Wed, May 6, 2009 at 6:43 PM, Igor Vaynberg wrote:
> what
what is the full name of this class? there are two DateTextField
classes in wicket codebase.
-igor
On Tue, May 5, 2009 at 9:51 AM, Eyal Golan wrote:
> Hello,
> We use Wicket 1.3.5 and I found something annoying with the DateTextField.
> In the constructor of that class, the converter is created
More on that,
we used the newConverterLocator() in out application exactly as it is
suggested in WIA, page 297.
However, because the DateTextField has its own converter, we even don't get
to our customized converter.
Is it a bug?
Please advise.
Eyal Golan
egola...@gmail.com
Visit: http://jvdru
Hello,
We use Wicket 1.3.5 and I found something annoying with the DateTextField.
In the constructor of that class, the converter is created internally.
If I want to use my own converter, I need to inherit DateTextField, add a
converter as a member, and return it in the getConverter method.
Why no