[
https://issues.jboss.org/browse/TEIIDDES-2268?page=com.atlassian.jira.plu...
]
Greg MacKinnon commented on TEIIDDES-2268:
------------------------------------------
I successfully executed a VDB (created from another non-teiid relational data source). I
think I'm using the same teiid driver for the teiid profile connection.
I see an incident on Eclipse BZ where someone was having the very same problem with a DB2
model (i.e., the NPE with an identical stack trace as shown in this issue). They
recommended a workaround of upgrading some Datatools support to Luna. I tried this but it
didn't appear to work. I'll probably append a comment to or open an issue on
Eclipse BZ to see what they have to say.
To be clear, I can connect to a VDB. It is when I try to expand the VDB in Data Source
Explorer that the NPE occurs.
NPE An internal error occurred during: "Loading Core
provider".
---------------------------------------------------------------
Key: TEIIDDES-2268
URL:
https://issues.jboss.org/browse/TEIIDDES-2268
Project: Teiid Designer
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Datatools Integration
Affects Versions: 8.5, 8.6
Environment: windows 7, eclipse kepler 4.3.2, teiid designer 8.5/8.6
Reporter: Greg MacKinnon
Here is a representative stack trace. This had been observed in teiid designer 8.5. I
fetched the 8.6 teiid designer code, built and installed in on eclipse to workaround an
AuthenticationType issue and have observed this NPE there as well.
!ENTRY org.eclipse.core.jobs 4 2 2014-07-24 15:34:22.685
!MESSAGE An internal error occurred during: "Loading Core provider".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.datatools.connectivity.sqm.internal.core.definition.isAuthorizationIdentifierSupported(DatabaseDefinitionImpl.java:2014)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.vnode.ServerExplorerVNodeContentProviderNav.displayDatabaseChildren(ServerExplorerVNodeContentProviderNav.java:391)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:116)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractOnDemandContentProviderNav.getChildren(AbstractOnDemandContentProviderNav.java:239)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.layout.AbstractLayoutProviderNav.getChildren(AbstractLayoutProviderNav.java:85)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.providers.content.impl.ServerExplorerContentProviderNav.load(ServerExplorerContentProviderNav.java:153)
at
org.eclipse.datatools.connectivity.sqm.server.internal.ui.explorer.loading.LoadingJob.run(LoadingJob.java:43)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
This occurs right after a call is made to load the definition.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)