Community
Participate
Working Groups
Steps to reproduce: 1. Create a Web 2.5 project. Target it on JBoss v4.2. 2. Right click on the project > Run As > Run On Server. Publishing starts, but crashes with NullPointerException - see below. After a quick look it seems that the problem is in the J2EEFlexProjDeployable, but I cannot be sure. Tim, please have a look, too. java.lang.NullPointerException at org.eclipse.wst.common.componentcore.internal.util.ComponentUtilities.getDeployUriOfComponent(ComponentUtilities.java:327) at org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.getURI(J2EEFlexProjDeployable.java:439) at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.guessModuleName(AntPublisher.java:282) at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.getPublishProperties(AntPublisher.java:247) at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.publish(AntPublisher.java:115) at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:82) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:742) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:828) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:659) at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:985) at org.eclipse.wst.server.core.internal.Server.publish(Server.java:935) at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:73) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Gorkem develops the generic server, but I don't see any obvious problem with calling getURI().
I have exactly the same problem consistently. Everything is OK after a clean installation of Eclipse EE 3.3. Then I run an update and install all the available DTP and WST updates. The NullPointerException occurs after installing those updates. Workaround: revert to previous configuration.
Is this problem still occurring? (I know a lot of work has been done in this area.)
This is not reproducible in 3.0.x and 3.1 codelines any more.
Closing.