Figure 25 shows a visual matrix of Method Permissions on the bean Book.
图25显示了bean Book上方法许可的可视化矩阵。
Next we'll configure method permissions for EJB2.1 and EJB3 session beans.
接下来，我们将配置EJB2.1和EJB3会话Bean的方法权限。
Listing 1 shows an example of code defining some role-based method permissions.
清单1所示的是用于定义某些基于角色的方法权限的示例代码。
In this section we see how to define security roles and configure method permissions.
在此部分，我们将了解如何定义安全角色和配置方法权限。
We configure the bean method permissions by using the method-permission element under assembly-descriptor in ejb-jar.xml.
我们通过在 ejb-jar.xml 中的 assembly-descriptor下使用method-permission元素定义Bean方法权限。
Listing 7 shows fragments of the EJB application deployment descriptor used to configure the method permissions for SimpleSessionBean.
清单7显示了用于配置SimpleSessionBean的方法权限的EJB应用程序部署描述符的片段。
Using declarative security, you can define security roles in the assembly descriptor of the EJB Module and assign method permissions to each role.
通过使用声明的安全，您可以定义EJB模块的集合描述符中的安全角色，并为每个角色分配方法许可。
With EJB components, I need to define method permissions on a bean-per-bean basis. The same goes for security identity and transaction demarcations.
对于EJB组件，需要在bean-per-bean 的基础上定义方法许可，安全性验证和事务区分同样需要这样的办法。
So, deployment descriptor properties such as isolation levels, access intent, security, method permissions, and so on cannot be set for such problem methods.
所以，就无法为这类问题方法设置隔离级别（isolation level）、访问目的（access intent）、安全性（security）和方法许可（method permission）等这些部署描述符属性。
EJB visual Editor now enables visual creation of new Method Permissions and manipulation of existing Method Permissions. To create a new Method permission.
ejb可视化编辑器现可以直接创建新方法许可和操作已有的方法许可。
In addition to configuring method permissions for a bean's methods, you can configure a Run-as role for the bean to specify the security identity with which the bean invokes other beans.
除了配置Bean的方法的方法权限外，还为Bean配置Run - as角色，以指定Bean用于调用其他Bean的安全标识。
Method permissions map security roles to specific EJB methods and security constraints map security roles to Web resource collections that are a combination of HTTP methods and URL patterns.
方法权限将安全性角色映射到特定的EJB方法而安全性约束则将安全性角色映射到Web资源集合中，这些Web资源集合是HTTp方法和URL模式的一个组合。
In essence, what happens upon calling this method is that a snapshot of the state of the call stack is taken at that very instant and the sets of permissions intersected with each other.
本质上，调用这个方法所发生的事情是对那一瞬间调用堆栈和一组相互交叠的权限进行快照。
The Permissions class also provides an implies() method.
Permissions类还提供了一个implies()方法。
Listing 14 shows how to invoke the authorize method with permissions to write content.
清单14展示了如何利用权限调用authorize方法，以写入内容。
Recall from Listing 8 how the login menu item invokes the authorize method with permissions.
回想一下清单8中登录菜单项是如何利用权限调用authorize方法的。
Users and user groups are created and are either given or denied execute permissions on any enterprise bean or method.
创建用户和用户组并且要么给予要么拒绝它们对任何企业bean或方法的执行许可。
You can specify permissions using one or more role-name elements, one for each role that is allowed to access the method.
您可以使用一个或多个role - name元素指定权限，允许访问此方法的每个角色有一个对应的此元素。
Ejb constraints are added to ejb-jar.xml and define method level permissions.
ejb约束添加到ejb - jar . xml中，用于定义方法级别的权限。
It then obtains a heterogenous PermissionCollection populated with statically bound permissions granted to the class's CodeSource, by calling the abovementioned getPermissions() method.
然后它调用上述 getPermissions() 方法获得授予类的 CodeSource 的一个填充了静态绑定权限的异类PermissionCollection 。
The Policy class provides a method called getPermissions() that can be called to obtain the set of permissions granted to a specific CodeSource.
Policy类提供了一个名为getPermissions()的方法，可以调用它以获得授予特定 CodeSource 的一组权限。
Finally, in the products add method, you could have checked to make sure the user had permissions.
最后，在productsadd方法中进行检查以确保用户具有权限。
The method-permission's method element specifies the security permissions for one or more methods in a bean.
method -permission的method元素指定Bean中一个或多个方法的安全权限。
Demands are applied at the class and method level as a mechanism for requiring that callers of your code have the permissions that you want them to have.
要求是一种应用于类级别和方法级别的机制，它要求调用您的代码的调用方拥有您所希望的权限。
But this method is proving to be a nightmare to maintain, especially when users come up with special case scenarios, which completely deviate from existing role permissions.
但是这种方法被证明是维护，特别是当用户拿出特例情况下，可以完全脱离现有的角色权限偏离了一场噩梦。
For example, a secure class library might have a method for creating files that would demand that its callers have permissions to create files.
例如，安全类库可能有创建文件的方法，该方法可能要求其调用方拥有创建文件的权限。
For example, a method on the call stack might deny all of its callers a set of permissions named PSET1, such that any demand for a permission that is part of PSET1 fails for those callers.
例如，呼叫堆叠中的方法可以使用一组具名为P SET1的使用权限拒绝它所有的呼叫端，如此一来，只要对这些呼叫端要求任何属于pset1一部分的使用权限都会失败。
They can be manipulated from other static and non-static method (basically from anywhere provided permissions are there).
他们可以从静态和非静态方法(基本上从任何地方提供的权限有)。
The exact permissions you demand will depend on the functionality exposed by your method.
您要求的确切权限将取决于由方法公开的功能。
The exact permissions you demand will depend on the functionality exposed by your method.
您要求的确切权限将取决于由方法公开的功能。
应用推荐