Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 148773 - Deploy failure if ejbs in web app and v3 doesn't have ejb container installed.
Deploy failure if ejbs in web app and v3 doesn't have ejb container installed.
Product: serverplugins
Classification: Unclassified
Component: GlassFish
All All
: P4 (vote)
: 7.4
Assigned To: TomasKraus
Depends on:
  Show dependency treegraph
Reported: 2008-09-30 17:36 UTC by _ pcw
Modified: 2013-07-24 23:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2008-09-30 17:36:28 UTC
Submitted by a user testing V3 ( see ), quoted here.

Netbeans 6.5 Dev (Build 200809130201)
GF v3 Prelude b24
OS: Vista Ultimate 32 bit

Deployment of a WAR with an EJB 3.1 fails. Reason: The EJB 3.1 container is not
installed yet. This is, however, a disadvantage comparing it to GF v2.

1. Support for EJB 3.1 comes bundled with GF v3 [preferred]
2. GF v3 recognizes the lack of EJB 3.1 package and installs the package lazily 
3. Netbeans 6.5 should not allow the deployment of an EJB 3, in case
glassfish-ejb package is not installed yet.
Comment 1 _ pcw 2008-09-30 17:40:12 UTC
Summary of my comments in 6107

My understanding is Option #1 is not in scope for V3 Prelude and Option #2, while it would be nice, is not in scope for
V3 Prelude either.  That leaves option #3.

The V3 plugin can determine if there are ejb's in a web app, using either the descriptor file or annotation support, but
especially in the latter case, it can be somewhat slow.  Slow enough that we probably don't want to do this every deploy
(which is the naive way to implement this).

I'm still thinking about it.  There may be a better way.
Comment 2 Vince Kraemer 2008-10-01 00:07:53 UTC
What are the steps necessary to reproduce this issue.... from the point where you create a new empty web app project?

I think the user has to do enough work-arounds to get their web-app with ejbs to compile... that they could figure out
that there is "something missing" long before they hit deploy or run....

Comment 3 _ pcw 2008-10-09 23:27:14 UTC
Too complex & too late for 6.5 --> next version.
Comment 4 Vince Kraemer 2009-03-30 17:50:47 UTC
is this going to be fixed in 6.7?
Comment 5 _ pcw 2009-05-19 23:31:57 UTC
Comment 6 Vince Kraemer 2009-09-16 23:59:51 UTC
assign outher half of pcw's issues
Comment 7 Michal Mocnak 2009-09-22 10:11:21 UTC
Please reevaluate this
Comment 8 Vince Kraemer 2010-04-05 21:52:19 UTC
this is a very corner case in 6.8 and 6.9... which include the FULL profile.
Comment 9 TomasKraus 2013-01-04 10:51:14 UTC
This seems to be a very old issue. Asked bug filer in GF Jira to verify this for 7.3.
Comment 10 TomasKraus 2013-07-24 23:00:05 UTC
I should check this in 7.4.

GF v3 Prelude support was dropped in 7.3.1 but currently all GF v3/4 servers are being checked forweb/full profile.

I'll try to deploy WAR with EJB on GF and 4.0 web profile to see what will happen.

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo