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.
The basic problem with explaining something that is clear as day to you
lies in finding out what the other doesn't yet understand :)
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));
I ended up using:
configuration.add(new BeanBlockContribution("jodatime",
"PropertyEditBlocks", "date", true));
But I had to add coercion to and from DateTime to Date (Not really that
hard to do...), which leads me to suspect that perhaps somebody changed
the property on the account pojo from normal Date to DateTime without
telling me... Anyways, lessons learned, thank you very much for your
patience!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
