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.
Based on the conversation in bug 151748 it appears that the version of Glassfish V2 UR2 is quite dated compared to the patched version. (It is this version https://glassfish.dev.java.net/downloads/v2ur2-b04.html rather than this version http://blogs.sun.com/theaquarium/entry/gfv2u2_patch_4_now_available or this version https://glassfish.dev.java.net/servlets/NewsItemView?newsItemID=6635) Please bundle the latest version of Glassfish v2 with NetBeans enterprise to eliminate NetBeans users from having to deal with bugs in Glassfish that have already been fixed.
Assign to correct component.
The latest V2 version that is available publically is V2 UR2 (build b04). All the patches for V2 are available only through the paid support. The only thing that we can do is to include V2.1 when it would be ready. Unfortunately this desicion is not the one the installer team can make itself. BTW, what is "NetBeans enterprise"?
"The latest V2 version that is available publically is V2 UR2 (build b04). All the patches for V2 are available only through the paid support." This concerns me greatly. It really devalues the benefit of using Glassfish for development and feels like a "bait and switch" tactic. Other open source projects like NetBeans, MySQL and JBoss don't do this. How about the build 58 version? I had thought paid support help for problems found in largish corporate enterprise installations and quick turn around of patches. "The only thing that we can do is to include V2.1 when it would be ready. Unfortunately this decision is not the one the installer team can make itself." Perhaps the NetBeans and Glassfish team should get together to discuss releases and what patches the recent build has in it compared to the FCS version and the production version. "BTW, what is "NetBeans enterprise"?" The "All" download.
> This concerns me greatly. It really devalues the benefit of using Glassfish for development and feels like a "bait and switch" tactic. > Other open source projects like NetBeans, MySQL and JBoss don't do this. How about the build 58 version? Including glassfish V2.1 in 6.5 is not under discussion, I will explain why (in my understanding, certainly). The reason is that V2.1 will not be in FCS quality when NB6.5 FCS will be out. http://wiki.glassfish.java.net/Wiki.jsp?page=PlanForGlassFishV2.1 http://wiki.netbeans.org/NB65Milestones As far as I understand, NB (6.5) can`t be shiped FCS version with non-fcs version of GlassFish (2.1). That`s why V2.1 is not in 6.5. We can consider adding v2.1 (development builds and fcs later, for now, you are right - b58 is the latest) in NetBeans development builds (http://bits.netbeans.org/download/trunk/nightly/latest/). > "The only thing that we can do is to include V2.1 when it would be ready. Unfortunately this decision is not the one the installer team can make itself." > Perhaps the NetBeans and Glassfish team should get together to discuss releases and what patches the recent build has in it compared to the FCS version and the production version. We`ll do. I will let you know the results once I have it and I can share it.
BTW, I noticed that the RMI serialization is not compatible between the older Glassfish 2.1 and the newest release. I had to update the local copy in NetBeans in order to communicate with the JMS service remotely running inside the latest Glassfish 2.1 release.
wobster, Unfortunately it is out of installer control to resolve such issues. If you wish this incompatibility to be resolved/addressed, please file a separate issue. If you think that the issue is in the NetBeans plugin, please file it against serverplugins/sunappserv9. If the issue seems to be on the GlassFish side, please file it in the GlassFish IssueZilla. https://glassfish.dev.java.net/servlets/ProjectIssues Thanks, Dmitry
I think it could be an installer issue since the old version of v2.1 is bundled with NetBeans. I don't know if they are supposed to be compatible from a RMI/IIOP serialization standpoint, but they aren't right now so remote communication with a JMS service using the default version of Glassfish bundled with NetBeans will not work with the newest 2.1 version.
At this moment, we still bundle v2ur2 (not 2.1) but it hopefully change in the next couple of days. We`ll use the latest public version of 2.1 which is b60e https://glassfish.dev.java.net/public/downloadsindex.html https://glassfish.dev.java.net/downloads/v2.1-b60e.html If the issue that you are referring to is fixed in that build of glassfish, then it would be also fixed in the NetBeans/ GlassFish bundle (as soon as we have it with glassfish v2.1). If the issue is fixed in some not public "patches" build then unfortunately we can`t do anything about that since we are not allowed to release glassfish "patch" builds (again, they are only available via paid support, afaik).
V2.1 is now included in daily builds and it will be also the part of 6.7 M2 which comes next week. Thanks, Yulia!
*** Issue 156390 has been marked as a duplicate of this issue. ***