🚀 go-pugleaf

David,

I have recently developed a framework to accomplish the same objective.
I can suggest the following implementation hints. I apologize if they sound 
trivial.

1. Make sure that all actions in your application are implemented as Swing
Actions. I implemented an extension to AbstractAction, which in addition to 
many
other things encapsulates a security token which allows to check it's 
permission
against a set of security tokens, managed by your own security 
implementation.
That way, when you define your action in one place in your application in 
the same
place you give it a security token.

2. Never build your menus/trees manually. Define your own nested data 
structure,
which you will use to code a nested set of Actions. Then pass your data 
structure to
a factory method, which can generate a tree or a menu, based on the data 
structure.
Among other things your factory method can easily check permissions for the 
security
token in the Action and choose to exclude the node from the tree based on 
the results
of such check, naturally if your factory will be building a menu you can 
choose whether to
keep the action as disabled or omit it.

Tony.