[
https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu...
]
Paul Richardson commented on TEIIDDES-1885:
-------------------------------------------
Debugging this on linux (so not quite the right platform) ...
Placing a breakpoint on TeiidServerManager's constructor demonstrates that an instance
is being correctly instantiated once ModelerCore.getTeiidServerManager() is called.
Likewise, a subsequent breakpoint on TeiidServerManager.getTeiidServerVersion() indicates
a successful return of a version number.
[~lfabriko] are you able to apply similar breakpoints and test whether this is the case on
macOs?
DDL importer problems - TeiidServerManager initialization problem
------------------------------------------------------------------
Key: TEIIDDES-1885
URL:
https://issues.jboss.org/browse/TEIIDDES-1885
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 8.2
Reporter: Barry LaFond
Assignee: Mark Drilling
Fix For: 8.3
Attachments: ddl-import, stdcust.ddl
When Importing from DDL to create a new view model (DDL File >> Source or View
model), the following problems appear:
a) when choosing auto-select for dialect, the wizard raises the difference panel after
hitting Next with generic "Error encountered importing DDL" message and a
"No difference report was found" message.
b) when leaving auto-select unchecked for dialect, clicking Next produces a DDL failed to
parse error (as well as a 'No difference report was found" error.
The DDL in question works in JBDS 6 and earlier.
Version-Release number of selected component (if applicable):
JBDS 7 with JBDSIS 7 beta 4
How reproducible:
Consistent.
Steps to Reproduce:
Import attached DDL via importer.
see:
https://bugzilla.redhat.com/show_bug.cgi?id=1016553
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira