Em Wed, 04 Nov 2009 15:00:38 -0200, Martin Reurings <mar...@windgazer.nl>
escreveu:
Using those two classnames as a reference I still can't figure out how I
could possibly assert the control I need.
I agree that my answer wasn't as clear as it should.
Honestly, I am somewhat surprised with how hard this seems to be :(
It isn't. :)
There's an editor available and I'm providing a BeanBlock that is _not_
an editor, why are those two in conflict, when they clearly should not
be?
Contributing a DefaultDataTypeAnalyzer, you create a type. Tapestry
expects you provide both editing and viewing blocks. In your case, you
just need to add a line in contributeBeanBlockSource to inform Tapestry
what editor it should use for jodaTime. I don't know what editor block
Tapestry was using before, but I guess it's 'date'. So please try adding
the following line to your contributebeanBlockSource() method and then
post the result:
configuration.add(new BeanBlockContribution("jodatime",
"PropertyEditBlocks", "jodatime", true));
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
