My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 138: Declaring FilterMatcher With Class/Property
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  jeff.johnston.mn@gmail.com
Closed:  Aug 2008


 
Project Member Reported by jeff.johnston.mn@gmail.com, Aug 22, 2008
it seems that when you add the new filter matcher explicitly,
you need to explicitly add filter matchers to the any other columns
you want to filter on ...

You found a bug!! Change the MatcherKey to an Object.class and it should
work for you. I'll put in an issue ticket for this. The bug is that when
you specify a class and a property the registry should not be checking the
on just the class for the columns.

tableFacade.addFilterMatcher(new MatcherKey(Object.class, "available"), new
AvailableFilterMatcher());
Aug 23, 2008
Project Member #1 jeff.johnston.mn@gmail.com
Fixed on the trunk. Now doing a check so when doing the second and third check will
not include MatcherKey's that have a property defined.
Status: Fixed

Powered by Google Project Hosting