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 114121 - Make EAR libraries available on the classpath of the EAR modules
Summary: Make EAR libraries available on the classpath of the EAR modules
Status: NEW
Alias: None
Product: javaee
Classification: Unclassified
Component: Persistence (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@javaee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-29 13:36 UTC by brettbergquist
Modified: 2008-01-15 16:14 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description brettbergquist 2007-08-29 13:36:38 UTC 
When developing an EAR application, one of the persistence packaging schemes is to have the entity classes in a separate
JAR that is located in top level of the EAR.  This is to allow the entity classes and persistence unit to be accessible
for EJB modules as well as WAR modules.  

When the persistence unit is packaged as such, it is not possible to use the "Create Session Bean for Entity Class"
feature in the EJB project.  The wizard indicates that there is no persistence unit and does not see the entity classes.
 This is true even though the JAR that contains the entity classes is listed as a library of the EJB project.
Comment 1 Erno Mononen 2007-10-30 17:50:26 UTC 
This is a valid issue, but unfortunately there is no time to do this for 6.0. Thanks for reporting in any case.
Comment 2 Andrei Badea 2008-01-15 16:14:34 UTC 
When the Java library project with library classes is listed as a library of the EJB project, then I can generate
session beans successfully. 

Making the EAR libraries available to the EAR modules is a whole feature, which was never planned, so there is no point
in tracking this issue as a defect.