Ted Neward wrote: > The dynamic download of stubs is not mandated by the J2EE specification--in > fact, you're flying directly in the face of the J2EE Spec, because dynamic > download of stubs is not handled under the IIOP protocol, which is the > preferred RMI protocol for EJB.
According to Sun's home page for RMI-IIOP (which can be found at http://java.sun.com/products/rmi-iiop/): RMI over IIOP is based on two specifications of the Object Management Group: * Java Language Mapping to OMG IDL Specification * CORBA/IIOP 2.3.1 Specification, formal/99-10-07 The first specification (http://cgi.omg.org/cgi-bin/doc?ptc/00-01-06) explicitly states that downloading *is* supported. Section 1.4.9 is titled "Code Downloading" and starts with this statement: Class downloading is supported for stubs, ties, values, and value helpers. The specification has been designed to be implementable using either JDK 1.1.6 or Java 2 APIs, allows transmission of codebase information on the wire for stubs and ties, and enables usage of pre-existing ClassLoaders when relevant. The rest of the section documents the required mechanism in detail. -- Larry =========================================================================== 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".
