fanste

I don't see a requirement for collecting clientIds instead of UIComponents. This would only be required, if there is any code that may replace a components instance and so the...

I will try to implement a test. Last time this was a pain in the ... as our infrastructure here is really picky.

I was on vacation and will try to implement a test tomorrow. UIComponents instead of clientIds can stay for now or does it need to be changed?

I just changed it to the clientId, but then the behaviour might be wrong. That is now up to you, to decide it. Using the UIComponent, the same instance is...

A valid usecase where clearing the input should be allowed while the minimum is set to `> 0` is the `required` attribute. If `p:inputNumber required="false" minValue="1"` Then the value should...

There could be a relatively simple intermediate solution until this gets properly fixed: - Add a JUnit `ParameterResolver` that simply returns `null` for the own injection types (e.g. `@InitalPage`, `@ArquillianResource`,...

Found another solution, which requires some more changes to the codebase. I will try to create a example repo with my changes. - Register a JUnit `ParameterResolver` which fires a...

Looks good on the first try. We will run some more tests

After some more testing, it is NOT working - in my first test I used the first row of the table which was still the first row after filtering. The...

Sorry for the delay - a lot to do.. Reproducer: https://github.com/fanste/primefaces-test/tree/test-10013 Some observations by myself. **Working as expected:** - Filter by `Table 1 Col 1` - Filter by `Table 2...