When running with a Java™ SecurityManager, invocation of some methods in the CORBA API classes might cause permission checks to be made that could result in a SecurityException.
The following table shows methods affected when running with Java 2 SecurityManager:
Class/Interface | Method | Required permission |
---|---|---|
org.omg.CORBA.ORB |
init |
java.net.SocketPermission resolve |
org.omg.CORBA.ORB |
connect |
java.net.SocketPermission listen |
org.omg.CORBA.ORB |
resolve_initial_references |
java.net.SocketPermission connect |
org.omg.CORBA. |
_is_a |
java.net.SocketPermission connect |
org.omg.CORBA. |
_non_existent |
java.net.SocketPermission connect |
org.omg.CORBA. |
OutputStream _request (String, boolean) |
java.net.SocketPermission connect |
org.omg.CORBA. |
_get_interface_def |
java.net.SocketPermission connect |
org.omg.CORBA. |
invoke |
java.net.SocketPermission connect |
org.omg.CORBA. |
send_deferred |
java.net.SocketPermission connect |
org.omg.CORBA. |
send_oneway |
java.net.SocketPermission connect |
javax.rmi. |
narrow |
java.net.SocketPermission connect |
If your program uses any of these methods, ensure that it is granted the necessary permissions.