The Concept of Bound Security is found here.
The default TL-Security depends on a single (Knowledge-)
Object. From POS however comes the idea of Security bound
to Objects resp. Views. This is all expressend by interfaces.
- The {@link com.top_logic.tool.boundsec.BoundObject} is an
Object that will be protected by Bound Security. BoundObjects
live in a TreeHirarchy and Security can be inherited
from Parent objects.
- The {@link com.top_logic.tool.boundsec.BoundChecker} is some
Object using/displaying/holding (in POS a View) a
BoundObject. It will eventually work for no (a null)
BoundObject in case the Security belongs to the
View/Checkder and cannot be derived from a BoundObject.
BoundChecker live in a TreeHirarchy and Security
can be inherited from Parent checkers.
- A {@link com.top_logic.tool.boundsec.BoundCommand} represents
some Action to be performand on a BoundObject. Default Command
types are Read/View, Write/Modify and Delete. Other Command
types may defined as desired.
- A {@link com.top_logic.tool.boundsec.BoundRole} allows relations
of BoundCommands to Users (The standard TopLogic User).
Copyright (c) 2003 Business Operation Systems GmbH. All Rights Reserved