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 67928 - J2EE APIs should be on the project classpath
Summary: J2EE APIs should be on the project classpath
Status: VERIFIED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: EJB Freeform (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-01 15:33 UTC by Lukas Jungmann
Modified: 2007-10-23 22:55 UTC (History)
0 users

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 Lukas Jungmann 2005-11-01 15:33:44 UTC 
[build 200510301900]

-have sources for some project and let's assume that this project contains only
ejb-jar.xml (and optionally some server specific DD, eg for websphere)
-create new ejb ff project from these sources and set SJS appserver as target
server for this project

=> sun-ejb-jar.xml DD is created automatically but J2EE APIs are not added on
the classpath

   I think that in this case we should add J2EE APIs on the project classpath
(at least for editor - now imports of javax.ejb.* are red underlined there). I
mean something like iff sun-ejb-jar.xml is created then add server's J2EE APIs
on the classpath automatically otherwise do nothing
Comment 1 Andrei Badea 2005-11-02 09:42:45 UTC 
Works as designed => not a defect. But I agree this would be an useful enhancement.
Comment 2 Andrei Badea 2007-07-04 09:57:22 UTC 
The EJB freeform project has been dropped from NetBeans 6.0.
Comment 3 Lukas Jungmann 2007-10-23 22:55:28 UTC 
v.