Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
jvx:server:security:object_method_access [2020/06/15 11:13] cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
jvx:server:security:object_method_access [2020/06/25 10:52] (current) cduncan |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| If you use a [[jvx:server:security:manager|SecurityManager]], you can restrict the access to life cycle objects. But sometimes you need restrictions for custom objects or methods of a life cycle object. | If you use a [[jvx:server:security:manager|SecurityManager]], you can restrict the access to life cycle objects. But sometimes you need restrictions for custom objects or methods of a life cycle object. | ||
| - | We are not big fans of "configuration til death" because config files are not more than config files. Nobody should fill config files with application logic. Keep your logic in your source code. | + | We are not big fans of "configuration til death" because config files are nothing more than config files. Nobody should fill config files with application logic. Keep your logic in your source code. |
| If you implement ''com.sibvisions.rad.server.security.IObjectAccessController'', you'll have full control over object and method calls. The interface offers following methods: | If you implement ''com.sibvisions.rad.server.security.IObjectAccessController'', you'll have full control over object and method calls. The interface offers following methods: | ||
| Line 58: | Line 58: | ||
| </file> | </file> | ||
| - | We use the object name for our checks. It is also possible to check class names or instances and is not a problem to read the configuration from a XML file, if you think it's better. | + | We use the object name for our checks. It is also possible to check class names or instances and is not a problem to read the configuration from an XML file if you prefer. |