Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Stub and Skeleton source code

 
Steve Marks
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Should I upload the stub and skeleton source code
generated by rmic -keep <filename>?
The reason I ask, is because in the spec it says that all object and source code should be submitted.
If I don`t have to, it will save a little work
as these files run to over 500 lines each, and as I didn`t write them it will be a little harder to document them easily. :roll:
 
Mark Spritzler
ranger
Sheriff
Posts: 17278
6
IntelliJ IDE Mac Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you are using RMI for the assignment, you have to have that or your program won't work.
RMI has to have those in order to have a lcient connect. THe Stub and skleton act as Adapters to the real class.
Mark
 
Steve Marks
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No, you misunderstood Mark.
I meant the stub and skeleton .java files that are created by the -keep on the command line.
 
Enrico Mannarino
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Steve,
no, I didn't keep them, actually I didn't even generate them. For me it's a bit overkill, because they are generated files. It's a bit like keeping your servlet files generated from your jsp, it doesn't make sense to me.
Every time I changed my code I did a makeall(compiling all java source files) , the rmic, the makejars. Then I was sure that everything was up to date.
/Enrico
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic