[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-2479) NPE occured while adding a EAR-project to JBoss 4.2 Server in ServerView
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Tue Jul 15 17:17:54 EDT 2008
[ http://jira.jboss.com/jira/browse/JBIDE-2479?page=all ]
Rob Stryker resolved JBIDE-2479.
--------------------------------
Resolution: Done
added checks in the code and threw CoreExceptions as per API
> NPE occured while adding a EAR-project to JBoss 4.2 Server in ServerView
> ------------------------------------------------------------------------
>
> Key: JBIDE-2479
> URL: http://jira.jboss.com/jira/browse/JBIDE-2479
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: core
> Affects Versions: 2.1.0.GA
> Reporter: Georg Sendt
> Assigned To: Rob Stryker
> Priority: Critical
> Fix For: 3.0.0.alpha
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> NPE occured while adding a EAR-project to JBoss 4.2 Server in ServerView / org.eclipse.wst.server.ui (1.1.0.v20080515).
> Server is locally installed at C:\java\jboss-4.2.2.GA
> Environment:
> eclipse.buildId=I20080617-2000
> java.version=1.5.0_15
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType.getServerHome(AbstractJBossLaunchConfigType.java:186)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.JBossServerStartupLaunchConfiguration.forceDefaultsSet(JBossServerStartupLaunchConfiguration.java:73)
> at org.jboss.ide.eclipse.as.core.server.internal.launch.JBossServerStartupLaunchConfiguration.setupLaunchConfiguration(JBossServerStartupLaunchConfiguration.java:67)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServerBehavior.setupLaunchConfiguration(JBossServerBehavior.java:133)
> at org.eclipse.wst.server.core.internal.Server.setupLaunchConfiguration(Server.java:1419)
> at org.eclipse.wst.server.core.internal.Server.getLaunchConfiguration(Server.java:1462)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.getLaunchConfiguration(ServerWorkingCopy.java:691)
> at org.jboss.ide.eclipse.as.core.server.internal.JBossServer.saveConfiguration(JBossServer.java:69)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:436)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil.saveServer(WizardTaskUtil.java:112)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil$2.performFinish(WizardTaskUtil.java:53)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard.executeTask(TaskWizard.java:256)
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizard$2.run(TaskWizard.java:213)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
> at org.eclipse.wst.server.ui.internal.wizard.page.WorkspaceRunnableAdapter.run(WorkspaceRunnableAdapter.java:35)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list