[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-3502) org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager at e94c62 exception using tomcat and JBossAS at the same time
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Sat Jan 10 13:20:04 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Snjezana Peco resolved JBIDE-3502.
----------------------------------
Resolution: Done
This issue happens when adding any non JBossTools server.
The jboss.as plugin was registering listeners for all servers (UnitedServerListenerManager). Now, they are registered only for JBoss Tools servers.
> org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager at e94c62 exception using tomcat and JBossAS at the same time
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-3502
> URL: https://jira.jboss.org/jira/browse/JBIDE-3502
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 3.0.0.CR2
> Environment: JBossTools-3.0.0.CR2-N200901060611-ALL-win32
> Reporter: Yura Zhishko
> Assignee: Snjezana Peco
> Attachments: xh.zip
>
>
> 1) Start JBoss Dev Studio from new clear WorkSpace
> 2) Create new Seam 1.2 project in he same workspace using JBossAS
> 3) Run JBossAS
> ASSERT: Everything is OK
> 4) Import xh (attached) Web project into workspace (configure it for JBossAS)
> ASSERT: Exception occurs in console (that is Ok)
> 5) Go to JBoss server view
> 6) Right mouse click -> New -> Server
> 7) Configure Tomcat 6.0 server (add xh project into Tomcat server but do not start it)
> java.lang.NullPointerException
> at org.jboss.ide.eclipse.as.core.server.internal.ServerListener.serverAdded(ServerListener.java:46)
> at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverAdded(UnitedServerListenerManager.java:85)
> at org.eclipse.wst.server.core.internal.ResourceManager.fireServerEvent(ResourceManager.java:492)
> at org.eclipse.wst.server.core.internal.ResourceManager.registerServer(ResourceManager.java:1055)
> at org.eclipse.wst.server.core.internal.ResourceManager.addServer(ResourceManager.java:629)
> at org.eclipse.wst.server.core.internal.Server.saveToMetadata(Server.java:422)
> at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264)
> at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:411)
> at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:421)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil.tempSaveServer(WizardTaskUtil.java:149)
> at org.eclipse.wst.server.ui.internal.wizard.WizardTaskUtil$4.performFinish(WizardTaskUtil.java:65)
> 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: 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