Submitted by a user testing V3 ( see https://glassfish.dev.java.net/issues/show_bug.cgi?id=6107 ), 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.
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.
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....
Too complex & too late for 6.5 --> next version.
is this going to be fixed in 6.7?
assign outher half of pcw's issues
Please reevaluate this
this is a very corner case in 6.8 and 6.9... which include the FULL profile.
This seems to be a very old issue. Asked bug filer in GF Jira to verify this for 7.3.
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 126.96.36.199 and 4.0 web profile to see what will happen.