[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1920:
----------------------------------------
I was able to test connection and import into Teiid Designer using
1) jconn4-26502.jar and....
2) used the Sybase JDBC Driver for Sybase ASA 10.x driver definition option
3) specified the driver class as: com.sybase.jbdc4.jdbc.SybDriver
4) Used a QE Sybase instance for BQT2, with port == 5000
There are 2 groups of Sybase connection profiles (ASE and ASA) and multiple flavors/versions for each of those.
So I think you'll need to be clear/concise with your driver type in this test.
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1885:
---------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> made a comment on [bug 1032157|https://bugzilla.redhat.com/show_bug.cgi?id=1032157]
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
> 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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1920:
-----------------------------------
Component/s: Import/Export
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1920:
-----------------------------------
Fix Version/s: 8.3
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-1885:
-------------------------------------------
No, the server wasn't configured (this test case didn't require the server)
> 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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-1920:
---------------------------------------
Lucie,
Have you been able to get any sybase driver to work that allows you to import and create the source model?
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1927) Need to test scenarios where vdb source translators are changed.
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1927?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1927.
-------------------------------------
Resolution: Done
Found that "Execute VDB" action was not always causing a re-deploy. So in cases where the translator was changed, etc, the 'old' VDB was getting re-used. Changed so that the VDB always gets re-deployed if the Execute VDB action is used.
https://github.com/Teiid-Designer/teiid-designer/pull/261
> Need to test scenarios where vdb source translators are changed.
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1927
> URL: https://issues.jboss.org/browse/TEIIDDES-1927
> Project: Teiid Designer
> Issue Type: Task
> Components: VDB & Execution
> Affects Versions: 8.2
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> I encountered a couple confusing scenarios where I changed the translator on a vdb source, but had no change on execution in designer. We need to test to ensure that vdb is picking up translator changes as expected.
> Scenario
> - Import a source Model (in my case it was SF).
> - Create a VDB and add the source model to it.
> - Deploy VDB, execute query to verify can query ok.
> - Change source translator in VDB to 'loopback'. Save VDB
> - Redeploy VDB, then run query. Loopback was expected, but I still got SF data back
> 1) the scenario above changes the translator in the VDB, but there is still an annotation in the source model with 'translator=salesforce'. So they are in conflict.
> 2) Changed the source model annotation translator to 'loopback', resync'd the vdb, redeployed and queried again. Still got SF results instead of loopback. The re-deployment is not picking up the translator change.
> 3) Finally, in the server view, manually 'un-deployed' the vdb. then went back to model exployer and deployed again. Then I got loopback results.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1885) DDL importer problems - TeiidServerManager initialization problem
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1885?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1885:
-------------------------------------------
[~lfabriko],
When you observed this error, did you have a server configured? Seems your setup never initialised the server manager.
> 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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1914) Recursive element - mismatch column names between mapping classes
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1914?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1914:
-----------------------------------------
I see what you're referring to - the columns get copied into the Supervisor table in the order that you select them from the Employees table. But, I don't see the "Mismatch" error anywhere. Where do you get the mismatch error?
> Recursive element - mismatch column names between mapping classes
> -----------------------------------------------------------------
>
> Key: TEIIDDES-1914
> URL: https://issues.jboss.org/browse/TEIIDDES-1914
> Project: Teiid Designer
> Issue Type: Feature Request
> Affects Versions: 8.2
> Environment: JBDS 7.0.1.GA, Teiid Designer 8.2Final
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> I run the E2eRecursiveXmlTextSourceTestScript; the XML view model from XSD contains mapping classes Employee and Supervisor. Next I copy the attributes from Employee to Supervisor. If the order of columns in Supervisor isn't the same as in Employee, I get
> "Mismatch column name between mapping class Employee and Supervisor"
> I am not sure if this is bug or if the message error is considered self-explanatory.
--
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
12 years, 5 months