Using those two classnames as a reference I still can't figure out how I could possibly assert the control I need. Honestly, I am somewhat surprised with how hard this seems to be :( 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?

Lately I've found that when I ran into problem with T5 it was because I was making things harder than they needed to be, but this time I don't see how I can make it more simple :(

Thiago H. de Paula Figueiredo wrote:
You could use a DataTypeAnalyzer instead of a DefaultDataTypeAnalyzer. This way, you have more control.

Em Wed, 04 Nov 2009 14:08:08 -0200, Martin Reurings <mar...@windgazer.nl> escreveu:

Hi Uli and/or anybody else reading this,

Could you help me some more? I ran into an unexpected problem :) There is a known editor-block for Joda DateTime, however, there is no known view-block?!? When I added the following:
    /**
* This method is used to add aditional editors / views to the Grid and BeanEditor components.
     * @param configuration
     */
    @SuppressWarnings("unchecked")
public static void contributeDefaultDataTypeAnalyzer(MappedConfiguration<Class, String> configuration)
    {
      configuration.add(DateTime.class, "jodaTime");
    }
public static void contributeBeanBlockSource(Configuration<BeanBlockContribution> configuration)
    {
configuration.add(new BeanBlockContribution("jodatime", "AppPropertyViewBlocks", "jodatime", false));
    }

And the appropriate stuff in AppPropertyViewBlocks.java and .tml I was able to view the DateTime properties on my Pojo, yay! However, this came with an unexpected side-effect, another Pojo which contained a DateTime field is using a BeanEditor, which was able to generate an editor for the DateTime field and is now throwing 'Unable to locate a block to edit property 'dateAccountCreated' (with data type 'jodaTime')' :( Any thoughts on how I can add the viewer without killing the editor?

Cheers,

 Martin




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to