Re: TableProvider question

Hi,
Could you elaborate on what you mean by "permanently restricting the dataset" and "temporary filtering"? I'm not sure I quite understand..
Although I am assuming you want to want to move from a Customers view to an Orders view based on a selected customer?
If this is the case, I would create a new (or extend the Default impl) TableProvider that can take the Customer or Customers id as an argument to use in a query to your backend.
I have done this sort of thing in applications I have written, so it is possible and quite easily achieved.

The next version of Wicket RAD will allow you to do more elaborate queries and filters, but it's not quite there yet, and I don't know if it will help you in your specific scenario.

If you think it helps, please feel free to upload a file (I think Nabble allows for that), or include a code snippet in your response, because I'm not sure I understood exactly what you where asking.

/ Wille

Jan Mikkelsen wrote:

Hi

I am in the process of building a small application based on Wicket RAD. It is looking very promising!

I have a question related to tables. Let's say my model consists of CUSTOMERS having ORDERS. When I present a table of orders, it will therefore be in the context of a customer. I am using something very similar to FilterPageToRuleThemAll which uses DefaultBeanPropertyTableProvider. This class does offer filtering, but that mechanism is not meant to be used to "permanently restricting the dataset", only for "temporary filtering". How would you handle such a case?

Thanks,
Jan