[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-5087) NullPointerException when do JBoss server publish once the name of the project is changed
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Mon Dec 21 18:31:31 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker resolved JBIDE-5087.
--------------------------------
Fix Version/s: 3.1.0.CR1
Resolution: Done
I'll mark this as resolved now. I've avoided the NPE. The problem was in some wtp code (the project refactor code) it manually makes a new Module(etc) with its OWN assumptions about what the name / id of the module are, and adds that to the server.
So, I've added a double-check that if the querried module fits that form, I convert it into our form and provide it's delegate. Look at the svn patch for details I guess.
> NullPointerException when do JBoss server publish once the name of the project is changed
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-5087
> URL: https://jira.jboss.org/jira/browse/JBIDE-5087
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS, UpStream
> Affects Versions: 3.1.0.M4
> Reporter: Denny Xu
> Assignee: Max Rydahl Andersen
> Fix For: 3.1.0.CR1, 3.1.0.CR2
>
>
> To produce:
> 1. create a WTP project, such as Web project, add to JBoss Server adapter and then publish it, it works.
> 2. rename the project and republish the project, got the NullPointerException:
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:171)
> at org.jboss.ide.eclipse.as.core.publishers.PublishUtil.getResources(PublishUtil.java:175)
> at org.jboss.ide.eclipse.archives.webtools.modules.LocalZippedPublisherUtil.fullPublish(LocalZippedPublisherUtil.java:186)
> at org.jboss.ide.eclipse.archives.webtools.modules.LocalZippedPublisherUtil.publishModule(LocalZippedPublisherUtil.java:62)
> at org.jboss.ide.eclipse.archives.webtools.modules.WTPZippedPublisher.publishModule(WTPZippedPublisher.java:50)
> at org.jboss.ide.eclipse.as.core.publishers.LocalPublishMethod.publishModule(LocalPublishMethod.java:71)
> at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:65)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1038)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872)
> at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
> at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
> at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list