[GLASSFISH-17549] Deployment should warn if an app client module JAR manifest lacks Main-Class setting because java Web Start launches will fail Created: 01/Nov/11  Updated: 24/May/13

Status: Open
Project: glassfish
Component/s: standalone_client
Affects Version/s: 3.1.1, 3.1.2, 4.0
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Tim Quinn Assignee: Tim Quinn
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


GlassFish correctly accepts an app client JAR that does not specify Main-Class in its manifest. We should do so because the appclient command allows users to specify what main class to launch, even in the absence of the Class-Path setting in the manifest.

But, Java Web Start launches will fail because users have no (good) way of specifying the main class.

Plus, app clients that do not specify Main-Class do not conform to the Java EE spec.

GlassFish should point that out to the user during deployment, and the app client container should detect this and report the error nicely. (Currently it throws an NPE.)

Comment by Tim Quinn [ 24/May/13 ]

Correcting the title

Generated at Tue Sep 01 15:23:49 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.