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 93699 - EJB jar file's manifest file missing Class-Path attribute causing class not found in ws-gen during deployment
Summary: EJB jar file's manifest file missing Class-Path attribute causing class not f...
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-31 18:38 UTC by J Xu
Modified: 2007-07-16 16:44 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 J Xu 2007-01-31 18:38:36 UTC
Build used: 20070122-0230

Steps to reproduce:
1. Create an EJB module project
2. Create a web service in the project
2. Create a jar file library using Library Manager and add some jar files to
that library
3. Add the library that's just been created to the EJB module project
4. Write some code in the web service impl class that uses some of the classes
in the library
5. Do a clean and build of the project

Please note that in the manifest file of the generated ear file the Class-Path
attribute is not set although all the jar files in the library have been
packaged into the ear file.  The workaround is manually set the Class-Path
attribute in the manifest file under the project's Configuration Files folder,
which is not convenient and not user friendly.

If you try to deploy this ear file, a class not found error will occur in WS-GEN
while it tries to discover the WS interface through reflection.
Comment 1 J Xu 2007-02-01 19:20:33 UTC
Should have said "EJB jar file", not "ear file"
Comment 2 Andrei Badea 2007-07-16 16:44:16 UTC
If the EJB module is standalone no Class-Path attribute is added to the manifest, because this is not supported by the
Java EE spec. You must include the module in an enterprise application.