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 54996 - J2EE Server classes as Library
Summary: J2EE Server classes as Library
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 4.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ ludo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-15 17:56 UTC by Martin Schovanek
Modified: 2006-04-10 16:16 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 Martin Schovanek 2005-02-15 17:56:53 UTC 
Would be nice to have 'J2EE Server classes' as
Class Library in the Library Manager.

Motivation: have J2EE stuff in J2SE class library
project.
Comment 1 _ ludo 2006-04-10 02:53:23 UTC 
in 5.5 to do that, you can use the app client project type.
Also for standalone JPAs persistence apps, you have the toplink lib registered
as well.
So closing this enh.
Comment 2 Martin Schovanek 2006-04-10 11:24:50 UTC 
The app client project type is a workaround but not solution for this issue,
because:

- the app client project is designed for different purposes than e.g. tag library
- I do not expect that users will discover it
Comment 3 _ ludo 2006-04-10 16:16:31 UTC 
Reopne with a real use case. Why an app would need only the j2ee spec API jar
without an implementation.
With a use case, we can consider an RFE or not. I do not have tis use case.

Also, please, see if this use case complies with the J2EE specification, and rules.