Doubt :
1. ) In the XML deployment descriptor, the method permissions are
specified using the method-permission tag as :
<method-permission>
<role-name>admin</role-name>
<method>
<ejb-name>EmployeeServiceAdmin</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
As per this block the "*" refer to all the methods in the
EmployeeServiceAdmin bean. Can we over ride permission for some of the
methods in this bean by adding one more method-permission block as :
<method-permission>
<role-name>superuser</role-name>
<method>
<ejb-name>EmployeeServiceAdmin</ejb-name>
<method-name>methodOfEmployeeServiceAdmin</method-name>
</method>
</method-permission>
In short can these two blocks exist simultaneously.
2.) On the same line as above can <method-name>*</method-name> used to
sepcify the "default" transaction attribute inside
<container-transaction> ....</container-transaction> tags, which may be
overridden by subsequent <container-transaction> tags.
3 ) Is it valid for a method-permission block to have methods from
different beans ? e.g.
<method-permission>
<role-name>superuser</role-name>
<method>
<ejb-name>EmployeeServiceAdmin</ejb-name>
<method-name>methodOfEmployeeServiceAdmin</method-name>
</method>
<method>
<ejb-name>ClientInfromation</ejb-name>
<method-name>methodOfClientInformation</method-name>
</method>
</method-permission>
4.) Also on the same lines is it valid to have methods from different
beans ( from the same jar) inside the <container-transaction>
....</container-transaction> tags
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
