deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <john.d.am...@gmail.com>
Subject Re: [DISCUSS][SECURITY-API] [DELTASPIKE-64] @Secured
Date Tue, 31 Jan 2012 12:05:26 GMT
Is it up to the developer to define the bean that implements an interface?

On Tue, Jan 31, 2012 at 6:59 AM, Gerhard Petracek <
gerhard.petracek@gmail.com> wrote:

> hi @ all,
>
> imo this feature of myfaces codi-core is a nice starting point for the
> security-api discussion, because the basic idea behind it is a very thin
> integration layer (which can be used by other modules).
>
> the basic concept:
> a cdi interceptor invokes (inline) voters to secure the target method/s.
> a voter is a (custom) cdi bean which implements a specific interface and
> therefore has access to the InvocationContext.
> furthermore, a voter detects 0-n violations and >can< be used to integrate
> 3rd party security-frameworks.
> [1] provides a bit more details of the basic concept as well as the basic
> usage of @Secured.
>
> please send
> +1, +0 or -1 because...
> for the >basic concept<.
>
> (please add >basic< objections also to [2]. we can discuss details e.g.
> further objections about the concrete implementation (e.g. internal
> classes,...) as soon as we agreed on including this concept.)
>
> regards,
> gerhard
>
> [1] https://issues.apache.org/jira/browse/DELTASPIKE-64
> [2]
> https://cwiki.apache.org/confluence/display/DeltaSpike/SE+Feature+Ranking
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message