Even though Java 5.0 has added dynamic stub generation to alleviate RMI developers from
explicitly invoking rmic on their remote classes prior to runtime, you must still do so for the certification
project. This is important: The use of rmic is still required as of this writing for the Java developer certification
Because I've decided to use the RMI as my server-client communication. However, I can't find any requirements in my assignment to say I must use the rmic. (My assignment is Bodgitt and Scarper v.2.2.1)
Must I use the rmic in my assignment?
Roberto Perillo wrote:I guess I was the only one that didn't generate any stub. Most of the people around here chose to run rmic.
That's because I convince people not to take the risk of automatic failure, it's easy and not a lot of work (certainly if you use an Ant-script to build your submission jar, like I did).
This release adds support for the dynamic generation of stub classes at runtime, obviating the need to use the Java(tm) Remote Method Invocation (Java RMI) stub compiler, rmic, to pregenerate stub classes for remote objects. Note that rmic must still be used to pregenerate stub classes for remote objects that need to support clients running on earlier versions.
So use of rmic is a must requirement to pre-generate the stub classes (although many people passed already without doing so, maybe Oracle/Sun needs to update their instructions)
You must provide all classes pre-installed so that no dynamic class downloading occurs
It clearly states that all classes should be pre-installed. And how you can check this, can be read in this thread.