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.
Summary: | Deploy failure if ejbs in web app and v3 doesn't have ejb container installed. | ||
---|---|---|---|
Product: | serverplugins | Reporter: | _ pcw <pcw> |
Component: | GlassFish | Assignee: | TomasKraus |
Status: | STARTED --- | ||
Severity: | blocker | CC: | vkraemer |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ pcw
2008-09-30 17:36:28 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. 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? No. 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 3.1.2.2 and 4.0 web profile to see what will happen. |