Two Laptop Bag*
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes rmic stub source Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "rmic stub source" Watch "rmic stub source" New topic

rmic stub source

Dmitri Christo
Ranch Hand

Joined: Jan 19, 2007
Posts: 81
Hi, I think I am almost done with packaging the assignment deliverables.

There is one doubt I was hoping to get some advice about:
I execute rmic successfully on the remote class and it is placed in the correct package structure: scjd\suncertify\remote\DataRemote_Stub.class

Then, everything seems ready to jar it all up into the final runme.jar (stub class included)

After creating the jar (in eclipse), the message is: "Export finished with warnings"

Warnings after the jar operation:
JAR export finished with warnings. See details for additional information.
Could not find source file attribute for: C:\scjd\suncertify\remote\DataRemote_Stub.class
Source name not found in a class file - exported all class files in /scjd/suncertify/remote

So, I am not sure if the eclipse jar operation is looking for a source. The class was generated by rmic itself (via a console command outside eclipse) without me having to write any source code, should I just ignore this warning from eclipse, or am I doing something wrong? Clearly the rmic stub generation part works successfully, so it has to be the jar creation. I will try doing it with ant, but not sure if will make any difference.

Thanks for your advice
[ March 25, 2008: Message edited by: Dmitri Christo ]
Dmitri Christo
Ranch Hand

Joined: Jan 19, 2007
Posts: 81
pardon this question, problem solved. Just used the -keep flag with rmic
I agree. Here's the link:
subject: rmic stub source
Similar Threads
Eclipse, RMI, and stubs
Creepy classpath?
NX: Execute runme.jar with RMI
IOP00110227 - Problem in rmic
rmic problem - IOP00110227