Restrictions on RMI
To avoid unnecessary complexity in the marking environment certain restrictions are placed on solutions that use RMI. Specifically:
# You must not require the use of an HTTP server.
# You must not require the installation of a security manager.
# You must provide all classes pre-installed so that no dynamic class downloading occurs.
# You must use RMI over JRMP (do not use IIOP)
The yes/no type answer is going to come back to whether or not your client can access the stub files from the local machine. Since your stubs will be in the runme.jar file, the client will be able to access them directly, so no dynamic loading will be required.How do I know if it's being used? Any RMI expert could probably answer yes or no. Yes your current implementation is dynamically loading the class or no your fine.
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7 Personal blog
Nov 14, 2005 11:22:52 AM sun.rmi.server.LoaderHandler loadClass
FINE: AWT-EventQueue-0: name = "suncertify.server.DataServiceImpl_Stub", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@133056f
Nov 14, 2005 11:22:52 AM sun.rmi.server.LoaderHandler loadClass
FINE: AWT-EventQueue-0: name = "java.rmi.server.RemoteStub", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@133056f
Nov 14, 2005 11:22:52 AM sun.rmi.server.LoaderHandler loadClass
FINE: AWT-EventQueue-0: name = "java.rmi.server.RemoteObject", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@133056f
Nov 14, 2005 11:22:52 AM sun.rmi.server.LoaderHandler loadClass
FINE: AWT-EventQueue-0: name = "java.rmi.dgc.Lease", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader@133056f
etc, etc, etc... -------------->
server:
ProductServer.class <launch code>
ProductImpl.class
Product.class <interface>
ProductImpl_Stub.class
client:
ProductClient.class <launch code>
Product.class <interface>