[JBoss JIRA] (TEIIDDES-2271) JBDS (+TD) shows only one translator (Win 7)
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2271?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2271:
---------------------------------------
The space in path issue strikes again. We had seen similar issues when starting the server. But had not seen this impact behavior post startup, until now.
> JBDS (+TD) shows only one translator (Win 7)
> --------------------------------------------
>
> Key: TEIIDDES-2271
> URL: https://issues.jboss.org/browse/TEIIDDES-2271
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Attachments: server.log, translator.png
>
>
> I don't know, if I am doing something wrong, but after I install JBDS + Teiid Designer and try to connect to some JBoss server, Teiid Designer shows only one translator(oracle) [screenshot]
> After some "googling" I have found this: https://community.jboss.org/thread/239714
> But the process described as a solution in this thread isn't working for me...
> Windows 7 Unltimate N SP1 64bit
> JBDS 7.1.1.GA
> Teiid Designer 8.3.3.Final-v20140613-1202-B88
> jdk1.7.0_60
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIIDDES-2271) JBDS (+TD) shows only one translator (Win 7)
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2271?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2271:
----------------------------------------
I think I have found the solution. There was a problem with the blank space in the path to JBoss EAP, the path was "C:\Users\Matus Makovy\jboss**". I reinstalled the server to "C:\jboss**" and all works.
There is no problem with blank space in path to JBDS (or workspace).
> JBDS (+TD) shows only one translator (Win 7)
> --------------------------------------------
>
> Key: TEIIDDES-2271
> URL: https://issues.jboss.org/browse/TEIIDDES-2271
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Attachments: server.log, translator.png
>
>
> I don't know, if I am doing something wrong, but after I install JBDS + Teiid Designer and try to connect to some JBoss server, Teiid Designer shows only one translator(oracle) [screenshot]
> After some "googling" I have found this: https://community.jboss.org/thread/239714
> But the process described as a solution in this thread isn't working for me...
> Windows 7 Unltimate N SP1 64bit
> JBDS 7.1.1.GA
> Teiid Designer 8.3.3.Final-v20140613-1202-B88
> jdk1.7.0_60
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIIDDES-2271) JBDS (+TD) shows only one translator (Win 7)
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2271?page=com.atlassian.jira.plu... ]
Matus Makovy edited comment on TEIIDDES-2271 at 8/12/14 4:58 AM:
-----------------------------------------------------------------
I think I have found the solution. There was a problem with the blank space in the path to JBoss EAP, the path was "C:\Users\Matus Makovy\jboss**". I reinstalled the server to "C:\jboss**" and all works.
There is no problem with blank space in path to JBDS (or workspace).
was (Author: mmakovy):
I think I have found the solution. There was a problem with the blank space in the path to JBoss EAP, the path was "C:\Users\Matus Makovy\jboss**". I reinstalled the server to "C:\jboss**" and all works.
There is no problem with blank space in path to JBDS (or workspace).
> JBDS (+TD) shows only one translator (Win 7)
> --------------------------------------------
>
> Key: TEIIDDES-2271
> URL: https://issues.jboss.org/browse/TEIIDDES-2271
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 8.3.3
> Reporter: Matus Makovy
> Attachments: server.log, translator.png
>
>
> I don't know, if I am doing something wrong, but after I install JBDS + Teiid Designer and try to connect to some JBoss server, Teiid Designer shows only one translator(oracle) [screenshot]
> After some "googling" I have found this: https://community.jboss.org/thread/239714
> But the process described as a solution in this thread isn't working for me...
> Windows 7 Unltimate N SP1 64bit
> JBDS 7.1.1.GA
> Teiid Designer 8.3.3.Final-v20140613-1202-B88
> jdk1.7.0_60
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (TEIIDDES-2268) NPE An internal error occurred during: "Loading Core provider".
by Greg MacKinnon (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2268?page=com.atlassian.jira.plu... ]
Greg MacKinnon commented on TEIIDDES-2268:
------------------------------------------
Hi Paul,
Your committed change fixed the NPE! Thanks for taking the time to think about this and to devise a fix.
Best Regards,
Greg
> 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)
11 years, 8 months
[JBoss JIRA] (TEIIDDES-1151) Model Extension Definition Version History Should Be Persisted Along With The Registry
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1151?page=com.atlassian.jira.plu... ]
Dan Florian updated TEIIDDES-1151:
----------------------------------
Assignee: Barry LaFond (was: Dan Florian)
Not sure if these issues are still valid or not. Assigning to Barry to edit and reassign.
> Model Extension Definition Version History Should Be Persisted Along With The Registry
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1151
> URL: https://issues.jboss.org/browse/TEIIDDES-1151
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Modeling
> Affects Versions: 7.6
> Reporter: Dan Florian
> Assignee: Barry LaFond
> Fix For: Future
>
>
> Persisting a version history of MED stored in the registry will help determine if the MED the user wants to register is newer or older than the one in already in the registry. The MED business object does have a version number but there are problems with using that to determine if one MED is newer/older than another MED. For instance, in a multi-user environment the same MED could be updated by different users. Each user could end up with a MED with the same version but with different content. And those MEDs could end up in the hands of other users who could also create new versions. Of course an enterprise could be diligent about controlling MED versioning using their own version-control system and possibly get around this issue. With that said, persisting a MED version history by using something like a checksum/sha-1 would remove the problems associated with relying on the version number at least for a workspace. We might also look at writing an exporter/importer to export the version history and then import into another workspace.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months