Mailing-List: contact users-help@deltaspike.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@deltaspike.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CANeU0Grygjbu5S8bgchzFb1HQ8MJt0omd0O+bPMxH0FHpdZm7w@mail.gmail.com>
References: 
 <CANeU0Grygjbu5S8bgchzFb1HQ8MJt0omd0O+bPMxH0FHpdZm7w@mail.gmail.com>
From: Gerhard Petracek <gerhard.petracek@gmail.com>
Date: Fri, 13 Nov 2015 16:07:50 +0100
Message-ID: 
 <CAGJtJfETnR5e_1CQdt5NQ-kMB6oSUioLg9YQTXx7Y-aNP4g+1Q@mail.gmail.com>
Subject: Re: Question about page parameters and access decision voters
 evaluation
To: users@deltaspike.apache.org
Content-Type: multipart/alternative; boundary=e89a8f923faa6f78e605246d6d90

--e89a8f923faa6f78e605246d6d90
Content-Type: text/plain; charset=UTF-8

hi juan,

i'll have a look at your demo soon.

regards,
gerhard


2015-11-13 15:54 GMT+01:00 Juan Pablo <jpangamarca@gmail.com>:

> 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.
>

--e89a8f923faa6f78e605246d6d90--