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.
Build: NetBeans IDE Dev (Build 20130218-2db966432258) VM: Java HotSpot(TM) 64-Bit Server VM, 20.1-b02, Java(TM) SE Runtime Environment, 1.6.0_26-b03 OS: Linux User Comments: GUEST: creating a new Glassfish Server 3 with new domain Stacktrace: java.lang.NullPointerException at org.glassfish.tools.ide.server.config.ConfigBuilderProvider.getBuilder(ConfigBuilderProvider.java:104) at org.netbeans.modules.glassfish.javaee.Hk2LibraryProvider.getLibraryClassPathURLs(Hk2LibraryProvider.java:441) at org.netbeans.modules.glassfish.javaee.Hk2LibraryProvider.getJavaEEClassPathURLs(Hk2LibraryProvider.java:339) at org.netbeans.modules.glassfish.javaee.JavaEEServerModuleFactory.ensureGlassFishApiSupport(JavaEEServerModuleFactory.java:274) at org.netbeans.modules.glassfish.javaee.JavaEEServerModuleFactory.access$200(JavaEEServerModuleFactory.java:79) at org.netbeans.modules.glassfish.javaee.JavaEEServerModuleFactory$1.run(JavaEEServerModuleFactory.java:150)
Created attachment 131509 [details] stacktrace
OK. exception message will be fixed. :) I just registered 2 GlassFish 3 servers (one with existing and one with new domain) using trunk sources from Friday that I considered as safe and working and I can't reproduce this problem. What build did you use? javaee7 branch or trunk?
I was finally able to reproduce this during an attempt to reproduce bug# 226246. Looks like both issues have the same cause - in GlassFishInstanceProvider/GlassFishInstance there was a change in javaee7 branch which sets local GlassFish version when GlassFishInstance instance is being initialised. This was not yet merged into trunk and we got an inconsistency between plugin and GF Tooling SDK library. javaee7 branch is being merged into trunk now so I'll check this scenario after merge will be done.
Fixed after javaee7 branch merge. Please let me know if it works for you too.
*** Bug 226232 has been marked as a duplicate of this bug. ***