Hello guys, I have a question, why access decision voters on views (defined in a typesafe view-config) are evaluated before any page parameters are set? Authorization could change in function of the page params (say, a page used to create/edit an entity depending on a parameter passed to it, and the user could be authorized only to edit, not to create new entities). Is this the expected behavior? In Seam for example, the evaluation order is page params, restrict expressions (analogous to access decision voters) and then page actions, so the described use case can be implemented without any problems. Here's the demo for my case, with an extended discussion: https://github.com/jpangamarca/deltaspike-authorization-demo. Any chances of supporting that kind of authorization requirements? Should I file a ticket?
Thanks for your attention.
