
<mlet enabled="true">
<classpath>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/jmxr-adaptor.jar</jar-url>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/ext/jmxremote.jar</jar-url>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/ext/jmxri.jar</jar-url>
<security-permission-spec>
grant{
...
permission java.net.SocketPermission "<REMOTE_HOST>","accept";
...
</mlet>
...
<mlet>
<classpath>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/web-console.war</jar-url>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/web-console-jmx.jar</jar-url>
<jar-url>@FILE_URL@@RHINO_BASE@/lib/ext/javax.servlet.jar</jar-url>
...
<security-permission-spec>
...
grant{
...
permission java.net.SocketPermission "<REMOTE_HOST>","accept";
...
</mlet>
15.4 Signing Deployable Units
When a deployable unit is installed, the contained component jars are extracted to a temporary location determined by the
SLEE. This means that individual component jars cannot be identified via a ‘codeBase’ rule in the security policy file.
However security permission can still be applied to the component jar, using the ‘signedBy’ rule. For example:
Open Cloud Rhino 1.4.3 Administration Manual v1.1 90
Comentários a estes Manuais