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.
I use: Product Version: NetBeans IDE 7.0 RC1 (Build 201103280000) Java: 1.7.0-ea; Java HotSpot(TM) 64-Bit Server VM 21.0-b02 System: Linux version 2.6.18-194.32.1.el5.centos.plus running on amd64; UTF-8; de_DE (nb) Userdir: /home/didi/.netbeans/7.0rc1 When I add an existing gf in version 2.1 I get only a prefilled option/text for version 3.x --> if this is what it mean I say this is not ok, because the ide has also support old glassfish versions like version 2. The old versions are also supportet for tomcat. When I choose the gf2.1 dir I see on the lower left side a message icon without any text. I'll add a screenshot. I ide.log I see only: INFO [glassfish]: Requested Entity: public id = -//Sun Microsystems Inc.//DTD Application Server 9.1 Domain//EN, system id = http://www.sun.com/software/appserver/dtds/sun-domain_1_3.dtd Further, in beta2 from netbeans V7 Glassfish Version 2.1 works like expected. And there I have also the option for version 2.x and 1.x Product Version: NetBeans IDE 7.0 Beta 2 (Build 201102140001) Java: 1.6.0_15; Java HotSpot(TM) 64-Bit Server VM 14.1-b02 System: Linux version 2.6.18-194.32.1.el5.centos.plus running on amd64; UTF-8; de_DE (nb) Userdir: /home/didi/.netbeans/7.0beta2
Created attachment 107466 [details] add gf v2.1 error msg
=== Comment removed per user request! ===
The user is trying to register a gf 2.1 domain as a 3.x domain. the error message that this is invalid is not correct... appears to be overwritten by something. The poor error message is p3. The missing registration wizard for gf 2.x may be from issue 195117 OR is a user error (they have not installed the support for gf 2.x from the update center). We may want to make it clearer to users that older GF releases are not supported out of the box.
they have not installed the support for gf 2.x from the update center --> this was the problem! Additionally I run into a new one: Primary on installtion I use an inport from installed 6.9 Version with gf 2.1. I'm sure, that I get offered gf2.1 on servers after first startup the ide. On 2nd startup the ide I don't see the gf2.1 any more. Now I install the plugin for old gf version. Then I see, when I try to add an new server, only gf in version 1 and 3 as option. loking into the netbeans.conf I see: netbeans_default_options="-J-Dcom.sun.aas.installRoot=\"/opt/appserver/glassfish-v2.1\" -J-client -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=384m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true" --> after remove the -J-Dcom.sun.aas.installRoot=\"/opt/appserver/glassfish-v2.1\" option I get offered also gf v2 in add server.
(In reply to comment #4) > they have not installed the support for gf 2.x from the update center --> this > was the problem! > > Additionally I run into a new one: > > Primary on installtion I use an inport from installed 6.9 Version with gf 2.1. > I'm sure, that I get offered gf2.1 on servers after first startup the ide. > On 2nd startup the ide I don't see the gf2.1 any more. > > Now I install the plugin for old gf version. > Then I see, when I try to add an new server, only gf in version 1 and 3 as > option. That sounds like issue 195117 to me. > > loking into the netbeans.conf I see: > netbeans_default_options="-J-Dcom.sun.aas.installRoot=\"/opt/appserver/glassfish-v2.1\" > -J-client -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=384m > -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true > -J-Dsun.java2d.noddraw=true" > > --> after remove the > -J-Dcom.sun.aas.installRoot=\"/opt/appserver/glassfish-v2.1\" option I get > offered also gf v2 in add server. This also sounds like how issue 195117 works... since you had to exit and restart the IDE... which is the work-around for issue 195117. Note: the fix for issue 195117 is in the dev builds... not the RC1 build. I am going to resolve this as a dup of 195117... *** This bug has been marked as a duplicate of bug 195117 ***