For Java application, JNLP (Java Network Launching Protocol) used by Webstart would be a good reference point for how to describe a java application. William On 8 Mar 2005, at 10:04, Donal K. Fellows wrote:
Quote from Karl's mail:
-- more structure for java -- jar versus bytecode class -- native compiled java? -- like executable but java-style parameterization -- class w/ Main() to invoke -- language version -- external class dependencies? -- supported JVMs (java portability 50% myth)
Any sensible suggestions in this area are entirely welcome, though we need to distinguish between modes of operation. For running of a classic Java application, supplying the name of the class or jar is sufficient (there's already an established pattern for such things, and they are distinguishable normally by the fact that class names virtually never correspond 100% with filenames without *some* kind of simple mapping). For other kinds of hosting system, it might be necessary to do other things, and it would be interesting to hear about them...
Donal.
--- William Lee @ London e-Science Centre, Imperial College London -- --- Software Coordinator --- A: Room 380, Department of Computing, Imperial College London, Huxley Building, South Kensington campus, London SW7 2AZ, UK E: wwhl@doc.ic.ac.uk | william@imageunion.com W: www.lesc.ic.ac.uk | www.imageunion.com P: +44(0)20 7594 8251 F: +44(0)20 7581 8024 --- Projects ---------------------------- GridSAM: http://www.lesc.ic.ac.uk/gridsam Markets: http://www.lesc.ic.ac.uk/markets ICENI: http://www.lesc.ic.ac.uk/iceni -----------------------------------------