Community
Participate
Working Groups
build: M-3.0.1-20080717094056 I have the following NullPointerException logged when starting Glassfish from the Servers view: Error calling delegate setupLaunchConfiguration() GlassFish V2 Java EE 5 at localhost java.lang.NullPointerException at org.eclipse.jst.server.generic.internal.xml.Resolver.skipToProperty(Resolver.java:103) at org.eclipse.jst.server.generic.internal.xml.Resolver.resolvePropertiesFromCache(Resolver.java:90) at org.eclipse.jst.server.generic.internal.xml.Resolver.resolveProperties(Resolver.java:68) at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.getStartClassName(GenericServerBehaviour.java:259) at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.setupLaunchConfiguration(GenericServerBehaviour.java:354) at org.eclipse.wst.server.core.internal.Server.setupLaunchConfiguration(Server.java:1415) at org.eclipse.wst.server.core.internal.Server.getLaunchConfiguration(Server.java:1458) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:2766) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:2719) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:306) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
The exception is coming from the Generic Server adapter. It seems that the class name for glassfish is missconfigured in the xml. Passing to Gorken for proper analysis.
The Glassfish server adapter is not provided by WTP. If this is a bug in the adapter we should close and ask the user to open a bug against the vendor that provided it.
I think this is actually a problem with the Glassfish adapter itself. It looks like it is missing a mandatory field. I have added a safe guard to the generic server framework for this just in case. The fix is released to 3.1 builds.
Fixed on 3.1
New Gerrit change created: https://git.eclipse.org/r/108696