Affects Version/s: 3.1.1, 3.1.2, 4.0
Fix Version/s: None
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.)
|Field||Original Value||New Value|
|Summary||Deployment should warn if an app client module JAR manifest lacks Class-Path setting because java Web Start launches will fail||Deployment should warn if an app client module JAR manifest lacks Main-Class setting because java Web Start launches will fail|