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 158753 - Glassfish v3 library doesn't pick up EJB library
Summary: Glassfish v3 library doesn't pick up EJB library
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-18 16:00 UTC by cayhorstmann
Modified: 2013-01-04 11:59 UTC (History)
1 user (show)

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 cayhorstmann 2009-02-18 16:00:50 UTC
1. Make a "Web project with existing sources", pointing to an app such as http://horstmann.com/elvis/SimpleQuiz.zip and
using Glassfish v3. This app contains a JSF 2.0 managed bean, a session bean, and an entity bean, all packaged in a WAR,
as permitted in EJB 3.1.

2. Realize that GFv3 doesn't have the EJB container or JSF 2.0 installed by default.

3. Install those into Glassfish

4. The Glassfish libraries do not contain the EJB and JSF 2.0 JARs, making it impossible to use Netbeans to work on this
project.

Please note: (1) With EJB 3.1, plain web projects can contain EJB (2) The Glassfish v3 libraries can change dynamically
Comment 1 Petr Jiricka 2009-04-08 13:47:16 UTC
Cay, thanks for the report. This sounds like something that should be handled on the GF plugin side. 

Which build of GlassFish did you try - are you using the recent nightly builds? Note that NetBeans 6.5 and 6.7 by
default only support the "Prelude" version released last fall, not any post-prelude builds. There is a way to make this
work, see Vince Kraemer's blog: http://blogs.sun.com/vkraemer/entry/7_0_and_glassfish_v3

Hopefully things work better now in the 6.7 dev builds with the (post-Prelude) v3 support enabled.
Comment 2 Vince Kraemer 2009-04-08 15:59:06 UTC
to use the ejb stuff in 6.7... use the enableExperimentalFeatures flag described in my blog entry.

We plan on having a more 'dynamic' solution for the release of NetBeans that will ship about the same time the v3 bits
go final.
Comment 3 Vince Kraemer 2009-09-16 19:59:08 UTC
this should get fixed for 6.8
Comment 4 Vince Kraemer 2009-09-23 07:18:51 UTC
updating the libraries due to an external change is kind of tricky to do right.

Comment 5 Quality Engineering 2009-09-25 09:13:31 UTC
Integrated into 'main-golden', will be available in build *200909241442* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/9d195f6c9d96
User: vince kraemer <vkraemer@netbeans.org>
Log: #158753: update libraries if modules directory gets updated.  Force an update when the v3 update center app is triggered.
Comment 6 Vince Kraemer 2009-09-28 06:49:49 UTC
since the update is not always detected in a timely manner, I am not going to close this issue... but will lower it to p4
Comment 7 Vince Kraemer 2010-03-08 09:34:53 UTC
i am not active on this issue right now.
Comment 8 TomasKraus 2013-01-04 11:50:38 UTC
This seems to not make sense with Glassfish 3.1.2.2 in NetBeans 7.3 which contains both EJB and JSF jars.
I opened this SimpleQuiz application in NB 7.3 + GF 3.1.2.2.
EJB is standard part of GlassFish JavaEE library imported into netbeans project as a server dependency. JSF 2.1 is also included in GlassFish modules.

Bean packages were changed in JSF 2.1 to
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
Comment 9 TomasKraus 2013-01-04 11:59:48 UTC
I'm closing this bug now. It's very marginal case related to first V3 versions.