@DataModel enhancement suggestion

[texan]

Are there any examples or explanations for the @DataBinderClass and @DataSelectorClass annotations? I'm curious whether they could be used to insert a different DataModel implementation class (for example, a data model with extra functionality for sorting and paging).

[texan]

BTW, sorry for the misleading topic title - I started out to suggest that the Seam team implement a way to indicate which class to use for the datamodel, then I remembered those other tags and couldn't figure out what they do...

[gavin.king]

They are really for supporting different data structures (eg. trees), but I suppose you would be able to use it for stuff like sorting...

[texan]

Is there any documentation about them or examples? I can only find the brief references in the manual.

What I wanted was to substitute a different class (say a subclass of DataModel) with additional attributes. That way, all of the attributes related to my table manipulation would live in the model itself.

Ideally, I'd love to see the following (hence my original title for this topic):

@DataModel(impl="MyDataModel.class")

[mzeijen]

I like the idea but the tag should probably look like this:

@DataModel(impl="my.package.MyDataModel")