• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

NX: Jar Packaging

Ranch Hand
Posts: 442
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
quote :

The JAR file must have the following layout and contents in its root:
The executable JAR containing the programs. This must be called runme.jar.

I initially understood this to mean that runme.jar will be used to extract other jars, ie client & server, but having re-read the mode flag section a few times again this seems to be way off, another quote :

When you submit your assignment, each part (client and server) must be executable using a command of this exact form:

The mode flag must be either "server", indicating the server program must run, "alone", indicating standalone mode, or left out entirely, in which case the network client and gui must run.

now what I understand or think I understand is that all modes are executed with java -jar runme.jar and then specifying whatever mode is relevant, and this would mean the client ends up having all files, even if they're not all needed, so where no mode is specified only gui package and common Data related interfaces/adapters and remote stub would be needed but instead he has everything.
have I misunderstood ?
Ranch Hand
Posts: 7729
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The runme.jar contains everyting relevant to runtime excution of both clients and the server.
That is my interpretation. I think the idea is good because it makes the implementation of an RMI solution so much easier.
[ April 17, 2003: Message edited by: Barry Gaunt ]
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic