You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@deltaspike.apache.org by Rainer Schön <de...@mr-partner.ch> on 2013/04/08 19:14:55 UTC

Secures vs. DecisionVoter

Hello,

I am evaluating DS for a migration project java ee5 Seam -> java ee6. Currently it is the security module that I am exploring (clone of 0.4-incubating-SNAPSHOT / 9720bec commit and locally built / Java 7 SDK). Some questions have arisen during my tests. I will begin with my first discovery:

- Secures and DecisionVoter seam to me somewhat redundant. What is the idea behind this design decision?

- Secures seams not to work with the type safe view configuration feature. Is this intentional or an anomaly?

- If it is intentional, what are the considerations?

Thanks in advance for a feedback
Rainer

Re: Disable WindowScope and its stuff

Posted by in...@softwareentwicklung-hell.de.

Hi John,

of course, i will create a Jira.

Regards
Florian

Quoting "John D. Ament" <jo...@gmail.com>:

> Hi Florian,
>
> Can you start w/ a bug/feature request?
> I agree, we shouldn't enable this by default.
>
> John
>
>
> On Wed, May 22, 2013 at 10:12 AM, <in...@softwareentwicklung-hell.de> wrote:
>
>> Hi all,
>>
>> is there a chance to disable the WindowScope and the default generated
>> windowId and dsRid url params?
>>
>> I'm not using the WindowScope and don't want that url stuff, also the
>> default loading screen is really crappy stuff. Don't like it when a
>> framework is simply going into my application and change randomized some
>> stuff.
>>
>> Thanks and regards
>> Florian Hell
>>
>

Re: Disable WindowScope and its stuff

Posted by "John D. Ament" <jo...@gmail.com>.

Hi Florian,

Can you start w/ a bug/feature request?
I agree, we shouldn't enable this by default.

John

On Wed, May 22, 2013 at 10:12 AM, <in...@softwareentwicklung-hell.de> wrote:

> Hi all,
>
> is there a chance to disable the WindowScope and the default generated
> windowId and dsRid url params?
>
> I'm not using the WindowScope and don't want that url stuff, also the
> default loading screen is really crappy stuff. Don't like it when a
> framework is simply going into my application and change randomized some
> stuff.
>
> Thanks and regards
> Florian Hell
>

Disable WindowScope and its stuff

Posted by in...@softwareentwicklung-hell.de.

Hi all,

is there a chance to disable the WindowScope and the default generated  
windowId and dsRid url params?

I'm not using the WindowScope and don't want that url stuff, also the  
default loading screen is really crappy stuff. Don't like it when a  
framework is simply going into my application and change randomized  
some stuff.

Thanks and regards
Florian Hell

Re: Secures vs. DecisionVoter

Posted by Gerhard Petracek <ge...@gmail.com>.

hi rainer,

i agree with you, however, there was no agreement in the community to keep
just @Secured.
since @Secures is a generic binding, we refactored @Secured (now it's based
on @Secures and isn't a std. cdi-interceptor any longer).

regards,
gerhard



2013/4/9 Rainer Schön <ra...@mr-partner.ch>

> Hi Gerhard
>
> I appreciated your quick reply, thanks. It is about what I thought when I
> studied the documentation of seam security and CODI security. In my
> opinion, the "@Secured" way provides the functionality needed and is
> virtually self documenting by it's DecisionVoter concept. Why the effort,
> to maintain two api for the same goal (apart the view-config integration
> which only @Secured provides)?
>
> Regards,
> Rainer
>
>
>
>
>
> Am 08.04.2013 21:04, schrieb Gerhard Petracek:
>
>  hi rainer,
>>
>> @Secures came from seam3 and is a cdi like ~simple binding.
>> @Secured is (now) based on @Secures and just a different style + offers
>> more than that (e.g. the integration with the view-config).
>>
>> regards,
>> gerhard
>>
>>
>>
>> 2013/4/8 Rainer Schön <de...@mr-partner.ch>
>>
>>  Hello,
>>>
>>> I am evaluating DS for a migration project java ee5 Seam -> java ee6.
>>> Currently it is the security module that I am exploring (clone of
>>> 0.4-incubating-SNAPSHOT / 9720bec commit and locally built / Java 7 SDK).
>>> Some questions have arisen during my tests. I will begin with my first
>>> discovery:
>>>
>>> - Secures and DecisionVoter seam to me somewhat redundant. What is the
>>> idea behind this design decision?
>>>
>>> - Secures seams not to work with the type safe view configuration
>>> feature.
>>> Is this intentional or an anomaly?
>>>
>>> - If it is intentional, what are the considerations?
>>>
>>> Thanks in advance for a feedback
>>> Rainer
>>>
>>>
>>>
>>>
>>>
>>>
>>
>

Re: Secures vs. DecisionVoter

Posted by Rainer Schön <ra...@mr-partner.ch>.

Hi Gerhard

I appreciated your quick reply, thanks. It is about what I thought when I studied the documentation of seam security and CODI security. In my opinion, the "@Secured" way provides the functionality needed and is virtually self documenting by it's DecisionVoter concept. Why the effort, to maintain two api for the same goal (apart the view-config integration which only @Secured provides)?

Regards,
Rainer





Am 08.04.2013 21:04, schrieb Gerhard Petracek:
> hi rainer,
>
> @Secures came from seam3 and is a cdi like ~simple binding.
> @Secured is (now) based on @Secures and just a different style + offers
> more than that (e.g. the integration with the view-config).
>
> regards,
> gerhard
>
>
>
> 2013/4/8 Rainer Schön <de...@mr-partner.ch>
>
>> Hello,
>>
>> I am evaluating DS for a migration project java ee5 Seam -> java ee6.
>> Currently it is the security module that I am exploring (clone of
>> 0.4-incubating-SNAPSHOT / 9720bec commit and locally built / Java 7 SDK).
>> Some questions have arisen during my tests. I will begin with my first
>> discovery:
>>
>> - Secures and DecisionVoter seam to me somewhat redundant. What is the
>> idea behind this design decision?
>>
>> - Secures seams not to work with the type safe view configuration feature.
>> Is this intentional or an anomaly?
>>
>> - If it is intentional, what are the considerations?
>>
>> Thanks in advance for a feedback
>> Rainer
>>
>>
>>
>>
>>
>

Re: Secures vs. DecisionVoter

Posted by Gerhard Petracek <ge...@gmail.com>.

hi rainer,

@Secures came from seam3 and is a cdi like ~simple binding.
@Secured is (now) based on @Secures and just a different style + offers
more than that (e.g. the integration with the view-config).

regards,
gerhard



2013/4/8 Rainer Schön <de...@mr-partner.ch>

> Hello,
>
> I am evaluating DS for a migration project java ee5 Seam -> java ee6.
> Currently it is the security module that I am exploring (clone of
> 0.4-incubating-SNAPSHOT / 9720bec commit and locally built / Java 7 SDK).
> Some questions have arisen during my tests. I will begin with my first
> discovery:
>
> - Secures and DecisionVoter seam to me somewhat redundant. What is the
> idea behind this design decision?
>
> - Secures seams not to work with the type safe view configuration feature.
> Is this intentional or an anomaly?
>
> - If it is intentional, what are the considerations?
>
> Thanks in advance for a feedback
> Rainer
>
>
>
>
>