hi juan, please create a jira-ticket for such an improvement. i'll also provide some details about an approach which allows to do it with the current versions.
regards, gerhard http://www.irian.at Your JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces, DeltaSpike and OpenWebBeans 2015-11-13 16:46 GMT+01:00 Juan Pablo <[email protected]>: > Thanks a lot. I'll be ready to provide any additional info if necessary. > > 2015-11-13 10:07 GMT-05:00 Gerhard Petracek <[email protected]>: > > > hi juan, > > > > i'll have a look at your demo soon. > > > > regards, > > gerhard > > > > > > > > 2015-11-13 15:54 GMT+01:00 Juan Pablo <[email protected]>: > > > > > 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. > > > > > > > > > -- > Atte. > > Juan Pablo Angamarca >
