< prev index next >

src/java.management/share/classes/javax/management/remote/rmi/package.html

Print this page




 370 
 371      <p>The mechanism described here does not apply when the IIOP
 372       Remote objects (Stubs or Servers) are created and connected to
 373       an ORB manually before being passed to the RMIConnector and
 374       RMIConnectorServer.</p>
 375 
 376 
 377     <h3>Dynamic code downloading</h3>
 378 
 379     <p>If an RMI connector client or server receives from its peer an
 380       instance of a class that it does not know, and if dynamic code
 381       downloading is active for the RMI connection, then the class can
 382       be downloaded from a codebase specified by the peer.  The
 383       article <a
 384     href="{@docRoot}/../technotes/guides/rmi/codebase.html"><em>Dynamic
 385     code downloading using Java RMI</em></a> explains this in more
 386     detail.</p>
 387 
 388  
 389     @see <a href="{@docRoot}/../technotes/guides/rmi/index.html">
 390         Java<sup><font size="-1">TM</font></sup> Remote Method
 391         Invocation (RMI)</a>
 392 
 393     @see <a href="{@docRoot}/../technotes/guides/jndi/index.html">
 394         Java Naming and Directory Interface<sup><font
 395         size="-1">TM</font></sup> (JNDI)</a>
 396 
 397     @see <a href="http://www.ietf.org/rfc/rfc2045.txt">RFC 2045,
 398     section 6.8, "Base64 Content-Transfer-Encoding"</a>
 399 
 400 
 401     @since 1.5
 402 
 403   </body>
 404 </html>


 370 
 371      <p>The mechanism described here does not apply when the IIOP
 372       Remote objects (Stubs or Servers) are created and connected to
 373       an ORB manually before being passed to the RMIConnector and
 374       RMIConnectorServer.</p>
 375 
 376 
 377     <h3>Dynamic code downloading</h3>
 378 
 379     <p>If an RMI connector client or server receives from its peer an
 380       instance of a class that it does not know, and if dynamic code
 381       downloading is active for the RMI connection, then the class can
 382       be downloaded from a codebase specified by the peer.  The
 383       article <a
 384     href="{@docRoot}/../technotes/guides/rmi/codebase.html"><em>Dynamic
 385     code downloading using Java RMI</em></a> explains this in more
 386     detail.</p>
 387 
 388  
 389     @see <a href="{@docRoot}/../technotes/guides/rmi/index.html">
 390         Java&trade; Remote Method
 391         Invocation (RMI)</a>
 392 
 393     @see <a href="{@docRoot}/../technotes/guides/jndi/index.html">
 394         Java Naming and Directory Interface&trade; (JNDI)</a>

 395 
 396     @see <a href="http://www.ietf.org/rfc/rfc2045.txt">RFC 2045,
 397     section 6.8, "Base64 Content-Transfer-Encoding"</a>
 398 
 399 
 400     @since 1.5
 401 
 402   </body>
 403 </html>
< prev index next >