MaDViWorld design issues, questions & ideas

Navigation: Up

Open questions

• Persistence design (State.fst etc.)?
• RMI/Jini design?
• Client startup script: what is UPLOADDIR1?
• strange, negative DUID generation: f9dc36:f710c61482:-7fea

Suggestions

• Improve overall project structure

  • portable across linux, win32 etc.
  • use of Ant (rmic, jar packaging etc.)
  • join all classes, use package names to distinguish between server, client and wizard
• use better logging (log4j), useful for debugging
• make better use of different ways to do a thing - pluggable modules (to make possible doing persistence with a database, or even better with a persistence layer like Hibernate)
• use configuration object (for runtime arguments)
• prevent code duplication, remove commented code
• use Javadoc consequently, add Ant target for generation of Javadoc
• make a commandline version first, then care about GUI
• use Swing instead of AWT
• remove confusion in Class Server - better split up in HTTP server (plain file serving) and add another (more independent) layer for class handling

Server suggestions

Client suggestions

Wizard suggestions

• check license of Symantec library
• Resolve Bug:44

Runtime environment under Linux

These preparations are necessary until I rewrite some Java code and extend the Ant script:

1. create following directories client, server, META-INF in /build
2. unpack jini-core.jar, jini-ext.jar, tools.jar (all from /lib/jini/lib) and symantec.jar to /build
3. copy PREFERRED.LIST to META-INF
4. copy .META-INF.PREFERRED.LIST to /build

PREFERRED.LIST:

 PreferredResources-Version: 1.0
 Preferred: false