This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 247484 - jar does not contain a manifest
Summary: jar does not contain a manifest
Status: RESOLVED WORKSFORME
Alias: None
Product: javaee
Classification: Unclassified
Component: Samples (show other bugs)
Version: 8.0.1
Hardware: PC Linux
: P1 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-26 03:37 UTC by thufir
Modified: 2015-03-27 14:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thufir 2014-09-26 03:37:39 UTC
I filed a glassfish bug -- when reading it, perhaps the bug is actually with Netbeans.  Netbeans creates an Application Client Container (ACC) application which runs correctly:

https://netbeans.org/kb/docs/javaee/entappclient.html

However, when the resulting EAR is deployed, the appclient cannot be launched because the JAR doesn't contain a manifest. 

The error is along the lines of:



org.glassfish.appclient.client.acc.UserError: ACC007: The app client file
/__JWSappclient/__app/SingletonQueue/SingletonQueueClient/
SingletonACCClient.jar does not contain a manifest; the app client
container cannot process it. Embedded programs should pass URIs with
scheme "jar:" for JAR files and scheme "file:" for directories.


While it's possible that this is my error, the sheer number of problems without solutions, or even references to documentation, indicated that there's a problem with netbeans, glassfish, or the documentation.
Comment 1 thufir 2014-09-26 03:38:35 UTC
the glassfish bug:

https://java.net/jira/browse/GLASSFISH-21215
Comment 2 Petr Hejl 2015-03-27 14:05:01 UTC
I'm sorry, but I tried really hard to reproduce this. But in any case the resulting jar contains the proper manifest. Though it might be a bug in GF. Appclient works ok in NB.