Results 1 to 2 of 2

Thread: @Secured nightmare

  1. Oct 22nd, 2006, 08:58 PM #1
    crbaker
    crbaker is offline Junior Member
    Join Date
    Jan 2006
    Location
    Sydney, Australia
    Posts
    14

    Default @Secured nightmare

    I'm really confused and even more concerned about my @Secured annotations.

    We have built an entire project with @Secured annotations placed on implementation of classes. As far as we knew this was a correct usage of the annotation.
    Since upgrading to Spring 2.0 it appears that none of these annotations work any more. Only when the @Secured annotation is placed on the interface is the method now secured.

    I really concerned that others may have upgraded to Spring 2.0 without the knowledge that this will break there @Secured method security, assuming my assumption is correct.

    Can someone more intelligent than me tell me what is going on?
    Reply With Quote Reply With Quote
  2. Oct 22nd, 2006, 09:01 PM #2
    crbaker
    crbaker is offline Junior Member
    Join Date
    Jan 2006
    Location
    Sydney, Australia
    Posts
    14

    Default Sorry wrong topic

    Sorry wrong topic
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules