Querying user groups while using @RunAs on a bean

Question

Hi,
I am trying to implement a scenario in which I have three entities:
- bean A - datastore for all users
- bean B - implementing logic, filtering results from datastore for specific user based on groups he is in
- User - calling bean B
Calling chaing is User -> bean B -> bean A.
bean B has to query user groups and filter data based on that. I've implemented that using:
Subject subject = Security.getCurrentSubject();
for (Principal principal : subject.getPrincipals()) {
if (principal instanceof WLSGroup) {
Without any security specified (like @RolesAllowed) it works like charm.
But I want to add security constraints to the beans:
@RolesAllowed("admin")
class A {}
@RolesAllowed("user")
class B {}
The problem is that B cannot acces A methods because it is calling A using 'user' security context.
I've thought I change it to:
@RunAs("application")
@RolesAllowed("user")
class B {}
"Application" is an account in group admin.
Now B can call A. The problem is that security context is switched to "application" on entering B's methods. Inside them I cannot query user groups using method presented above, because I get "application" groups.
Is there a way to change security context on calling other bean methods? Like using Security.runAs( somehowGetApplicationSubject(), runnable) ??
Other method I've thought of, but I have no idea how to implement that, is somehow querying weblogic to get groups of SessionContext.getCallerPrincipal(), which returns user account regardless of using RunAs.
Hope someone made through this problem before,
Krzysiek

Answer 1

getBounds() will only generally make sense while the component itself is being rendered. I wouldn't be completely surprised if the framework which gets that component also resets its size once it's done painting the thing.
If you're calling it from outside the rendering loop, perhaps you could try calling validate() on the component, which should force it to determine its size.
Failing that, you could possible use getPreferredSize() instead, which will likely obtain a similar result in most cases.