heap size -xms and -xmx definition on a per-app basis in manifest file?

[Fernando Cassia]

On Wed, Sep 12, 2012 at 2:19 AM, Stuart Marks <stuart.marks at oracle.com>wrote:

> On 9/10/12 6:15 AM, Fernando Cassia wrote:
>
>> On Sun, Sep 9, 2012 at 9:16 PM, Fernando Cassia <fcassia at gmail.com>
>> wrote:
>>
>>>
>>> Well, after asking all this... I hope this isn´t an issue that has been
>>> already adressed. ;-)
>>>
>>
>> ...and if my proposal is stupid just tell me too. ;)
>>
>
> Not a stupid proposal, but the jar manifest is really at the wrong level.
> This kind of thing is addressed by JNLP. It's possible to specify initial
> and max heap sizes, JDK versions, etc. in a JNLP file. See


The manifest currently describes parameters of the packaged app, like the
default class, so that people do not have to specify the default class name
when running the app and so that it runs seamlessly when doing a double
click (on windows, whose JRE associates .jar with "java -jar"), or by
calling it with java -jar apname.jar. So why can´t the app´s memory
requirements be another parameter, just like the default class name?

If I package my app as a single .jar, and tell users to "download and run
this jar (double click on windows or java -jar appname.jar" on Linux, how
is jnlp involved? it isn´t.

FC
-- 
During times of Universal Deceit, telling the truth becomes a revolutionary
act
- George Orwell