-
Task
-
Resolution: Done
-
Major
-
8.1.0.Final
-
None
The scenario in https://issues.jboss.org/browse/WFLY-2988 (https://bugzilla.redhat.com/show_bug.cgi?id=1072638) is rejected by engineer as it's considered current behaviour is correct.
Adding tests to cover @RolesAllowed use if the bean class has superclasses.
Example in EJB 3.1 spec 17.3.2.1:
Example:
@RolesAllowed(“admin”)
public class SomeClass {
public void aMethod () {...}
public void bMethod () {...}
...
}
@Stateless public class MyBean extends SomeClass implements A {
@RolesAllowed(“HR”)
public void aMethod () {...}
}
public void cMethod () {...}
...
Assuming aMethod, bMethod, cMethod are methods of business interface A, the method permis-
sions values of methods aMethod and bMethod are RolesAllowed(“HR”) and RolesAl-
lowed(“admin”) respectively
- relates to
-
WFLY-2988 Class-level @RolesAllowed does not affect inherited methods
-
- Closed
-
