We have an app with three "user types" and two "user levels" (read or read-write in effect). We want to use these in authorization, and thought about an approach using annotations. However, at the point of the Wicket auth. interface methods, only class-targeted annotations are visible, and that will lead to excessive subclassing (especially since Java does not let you annotate anonymous inner classes).
Would it be a better approach to use "behaviorless Behavior" objects that we add to the relevant components and look for in isActionAuthorized()? Med vennlig hilsen TOR IVER WILHELMSEN Senior systemutvikler Arrive AS T (+47) 48 16 06 18 E-post: [email protected] http://www.arrive.no http://servicedesk.arrive.no
