[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1657) Imported Project's classpath container assuming server exists

[Rob Stryker (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBIDE-1657?page=comments#action_12397202 ] 
            
Rob Stryker commented on JBIDE-1657:
------------------------------------

The previous container still exists and has not been deprecated. It is actually the delegate that is used when the WTP runtime classpath container path is used. It will remain in existence. There was no change to plugin.xml here so support for the container is in no way removed. If you insist, though, a unit test can be made. 

> Imported Project's classpath container assuming server exists
> -------------------------------------------------------------
>
>                 Key: JBIDE-1657
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-1657
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>            Reporter: Rob Stryker
>         Assigned To: Rob Stryker
>             Fix For: 2.0.1
>
>         Attachments: runtimecontainerbug.png
>
>
> java.lang.NullPointerException
> 	at org.jboss.ide.eclipse.as.classpath.core.runtime.ProjectRuntimeClasspathProvider$RuntimeClasspathContainer.getDescription(ProjectRuntimeClasspathProvider.java:120)
> 	at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getCPListElementText(CPListLabelProvider.java:261)
> 	at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListLabelProvider.getText(CPListLabelProvider.java:78)
> 	at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108)
> 	at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164)
> 	at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:135)
> 	at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:386)
> My guess is that your classpath container thinks the server exists...which it wont do in this case when he is creating a new project.
> That should be fixed in .0.1
> Workaround for user: delete the classpath entry about JBoss 4 server in classpath.

-- 
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