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: | GlassFish blocker please | ||
|---|---|---|---|
| Product: | javaee | Reporter: | bht <bht> |
| Component: | Code | Assignee: | Petr Jiricka <pjiricka> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | mmirilovic, pjiricka, vkraemer |
| Priority: | P1 | Keywords: | RELNOTE |
| Version: | 7.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
|
Description
bht
2011-03-23 19:16:08 UTC
The engineer working on the GF integration plugin is not the correct assignee for a product packaging issue like this. I have assigned it to somebody who has some power to actually get something done about this. GlassFish bug http://java.net/jira/browse/GLASSFISH-13129, which is at the root of this, was reopened - the problem was acknowledged. I guess you should request it to be included in a patch for GF 3.1. There is nothing we can do about this on the NetBeans side, closhing as WONTFIX. Before this is addressed on the GlassFish side, you can continue using GF 3.0.1, which works with NetBeans 7. Thanks for your comments. However, while GF 3.0.1 works with NetBeans 7, it also contains this bug. The request of this was to include a patched version of GF 3.1 in the final NetBeans release. Can we be assured that this will happen? This bug is severe. I am quite confident that it violates the servlet specification. I apologise for this. It is an unfortunate scenario because the bug was actually closed where in fact it wasn't fixed. > Can we be assured that this will happen?
No. NetBeans schedule is independent of GlassFish, and I am not sure GlassFish plans to release an update release that will fix this bug in time for the NB 7.0 release. We are not going to wait with the NB 7.0 release for an update release of GF 3.1.
And if this bug is addressed in the form of a patch, then it will not be included in NetBeans either. A patch is something you download separately from the server, and the released server bits are not respinned when the patch is released. Same with the IDE - the bits included in the IDE are still the same, you download the patch separately.
Another workaround is to build GlassFish containing this patch yourself once the diff is available, and use this patched GF with NetBeans.
(In reply to comment #3) > It is an unfortunate scenario because the bug was actually closed where in fact > it wasn't fixed. WONTFIX means We will not fix this issue (we can't) ... see http://wiki.netbeans.org/IssueLifeCycle#Rejecting_Issues Of course I know about this one. Misunderstanding :) I mean the GlassFish bug was filed against GF3.01 which was never fixed, and GF3.1 was now not even fixed, but the GlassFish bug was closed as fixed nevertheless. I was thinking that an extraordinary condition like this would create an adequate response within Oracle. Sorry for taking your valuable time once again. I think this extraordinary case needs an extraordinary response - escalation to management. This is not a NetBeans issue, however the reputation of the tool is at risk. GlassFish will not function as web container where users have cookie support disabled in their browsers. In development, this scenario cannot be tested, either. The GlassFish engineer is apparently playing this down by giving it a 3.2 release target. Which brings us back to exactly the same situation at 3.01 when the fix was targeted for 3.1. So far there hasn't been a patch or a release where this bug was fixed. It would be naiive to think that things get better without an escalation. (In reply to comment #7) > This is not a NetBeans issue, however the reputation of the tool is at risk. Fully agree with escalation, we'll do our best and as you mentioned this is not NB issue, so please do not reopen this again. P1 means stopper for NB 7.0, and this is not stopper for NB 7.0 - Thanks for understanding. > I think this extraordinary case needs an extraordinary response - escalation to > management. I notified the GlassFish team about this. BTW, you can also escalate yourself - there is a formal escalation process available to GlassFish customers. See this page for information on the commercial distribution of GlassFish: http://www.oracle.com/us/products/middleware/application-server/oracle-glassfish-server/index.html > So far there hasn't been a patch or a release where this bug was fixed. Patches only include fixes that are specifically requested by customers, so this probably was not requested by any customer yet. Thanks a lot for filing the issue on GlassFish. The GlassFish issue you had filed has been fixed in trunk on March 24. You can verify the fix in your environment using the continuous builds running at http://hudson.glassfish.org/job/gf-trunk-build-continuous/ You can pick up the last successful build (ones with a blue button on the left hand nav) and download either the glassfish.zip file (for full Java EE profile) or the web.zip file (for web profile). Some clarifying notes : The GlassFish engineer marked the target release for this fix to 3.2 as that is the only release known as the next release for GlassFish at this point in time. If another release fructifies in between this fix would be included in it. Its not the intention to postpone fixing the issue. It is not possible to mark this fix for 3.1 as that product has already shipped as a release. For an official supported patch on top of 3.1, you can request the same through the escalation link Petr provided. |