• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Package problem

 
Zee Ho
Ranch Hand
Posts: 128
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi, I plan to submit my project in few days. In order to make the hierarchy more clearer, I separate it to client and server sub-package like

--suncertify -- Launcher.java//to start the whole project.
|
|- client-//contains 4 sub-packages
| |
| |- controller - The controllers of MVC
| |- dao - DAOFactory
| |- model - Application Model
| |- ui - All created UI
|
|
|-db - DBAccess, Data, LocalData, Exception
|-server - RemoteInterface, LockManager, RemoteData, Server
|-utility - Some Utiltiy files

Do I separate them in a correct way?

Another question is sun only require us to package one jar named runme.jar, then why he talk about some dynamic downloading issue? I think rmic the code and jar them is enough. right?
[ April 24, 2005: Message edited by: Zee Ho ]
 
Zee Ho
Ranch Hand
Posts: 128
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
call up!
 
Andrew Monkhouse
author and jackaroo
Marshal Commander
Pie
Posts: 12014
220
C++ Firefox Browser IntelliJ IDE Java Mac Oracle
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Zee,

Your packages look reasonable.

You are correct - running RMIC and putting the stubs into the runme.jar file is all you need do.

FYI...

Under the older assignment (Fly By Night Services), it was not necessary to have a single executable jar file (or any jar file at all). So it was possible for candidates to have separate code for client and server, and to require dynamic downloading of the stub files. This has been explicitly banned in the current assignments.

Likewise, JDK 1.5 added support for the dynamic generation of stub classes at runtime, however utilising this might run foul of the dynamic downloading clause.

Regards, Andrew
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic