Internal Website Search
21-30 of 89 resultsRefreshObjectDB Server Connection Permissions It would be useful if instead of creating a web service layer on top of a database, I could just set up permissions to entities and entity variables for client connections ... Hogan Type level permissions are currently not supported so this would be a new feature | |
Add Type level permissions to ObjectDB Server could just set up permissions to entities and entity variables for client connections ... supports directory and file (i.e. database) level permissions. It may be possible to add for every user also permission settings of specific entity classes. Each such entity class | |
Server Configuration can be accessed by the server. Appropriate file system permissions have to be set on the data directory | |
Eclipse Distribution License - v 1.0 without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT | |
Chapter 6 - Configuration. Appropriate file system permissions have to be set for all the paths that are specified | |
ObjectDB Website - Terms and Conditions of Use> Permission is granted to temporarily download one copy of the materials (information or | |
java.security.BasicPermission java.security.Permission boolean implies (Permission arg0) implies (Permission arg0) | |
[ODB1] Chapter 5 - JDO Connections connection to enable user identification and permission checking. Username and password are optional in ... which permissions are not managed, these properties are always optional and ignored if specified. | |
javax.jdo.spi.JDOPermission java.security.Permission permission and has no actions. There are two names currently defined. Each named permission has a corresponding public static final field which contains an instance of the named permission | |
checkAuthorizedStateManager(sm) the set of authorized classes is checked, and if not present, a regular permission check is made. The regular permission check requires that all callers on the stack, including the persistence-capable |