cgriffith,
All my business beans do implement common methods as you describe.
InterfaceDef getIntfDef();
FunctionDef[] getFunctionDefs();
These methods inspect access and different types of functionality offered by
the session bean that only the bean knows about and return the full set of
meta
matt10,
I would say this is an interesting use case. The problem with making client
unaware of buisness components is that you then have to come up with ways to
configure your client to do stuff with abstract notions of business objects.
In that case what you have done with annotation inspect
j2ee_junkie,
Thanks for your input.
I trivialised my use case as enabling/disabling menu items for the sake of
forum post.
My client is not so much a fat client as an automatic user interface which
exposes business methods directly to the user. It generates forms and offers
functionality with
matt10,
Wouldn't it be better if your fat client enabled/disabled menu items based on
the roles the user has rather than the methods they can call. I mean really
this is the same thing, only you do not have to go get method permissions.
cgriffith
View the original post :
http://www.jboss.com
It is possible to do this by inspecting the bean's own annotations with code,
i.e. method @PermitAll, @RolesAllowed, and class defaults. This works.
IMHO It would be nice if there was a JBoss method that would allow such method
access checks though.
View the original post :
http://www.jboss.co
