Marten,
Please bear with me and just tell me how to define the method security on the interface without using the @secured annotation.
Thank you!
Marten,
Please bear with me and just tell me how to define the method security on the interface without using the @secured annotation.
Thank you!
Sigh... As I stated and I assume you know how to define an interface?!
...the methods you want to secure have to be part of your interface...
Marten Deinum
Java Consultant / Pragmatist / Open Source Enthousiast / Author
Pro Spring MVC: With Web Flow
Conspect
Have you read the reference guide.
Use the [ code ] tags, young padawan
Ok.. now that brings us back to our start point... because they are part of the interface.. I thought you meant that the security interception definition should be part of the interface.
What I will do is that I will try removing the circular reference.. but that was a hack to fix the problemt that I had from the very begining... and no.. I didn't have it working.. because I was getting the same Object in all sessions and not the same Proxy.. so all the users will use the Object of the first user.. not the only the proxy.
Thank you for your time... and please, just relax!