[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:
-------------------------------------------
I debugged Teiid Designer on MacOS, applied given breakpoints - and the model was imported correctly. The error message didn't occur at all; and TeiidServerManager wasn't null.
> 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-1929) View model is changed by attempting to delete dependent source model and previewing delete
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1929?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1929:
-----------------------------------
Attachment: TEIIDDES-1929.zip
model project set
> View model is changed by attempting to delete dependent source model and previewing delete
> ------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1929
> URL: https://issues.jboss.org/browse/TEIIDDES-1929
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.3
>
> Attachments: TEIIDDES-1929.zip
>
>
> 1) Import attached project set
> 2) Open ProductViews model in editor to show package diagram
> 3) Select ProductsDB2_VDB model and click DELETE
> 4) In Delete refactor wizard click *Preview>* button
> 5) Cancel all and the ProductViews editor tab will be dirty (requires saving) and the package diagram is cleared out.
> Wondering what EMF data is getting set/changed to cause the dirty editor?
--
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-1929) View model is changed by attempting to delete dependent source model and previewing delete
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1929:
--------------------------------------
Summary: View model is changed by attempting to delete dependent source model and previewing delete
Key: TEIIDDES-1929
URL: https://issues.jboss.org/browse/TEIIDDES-1929
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 8.3
Reporter: Barry LaFond
Assignee: Paul Richardson
1) Import attached project set
2) Open ProductViews model in editor to show package diagram
3) Select ProductsDB2_VDB model and click DELETE
4) In Delete refactor wizard click *Preview>* button
5) Cancel all and the ProductViews editor tab will be dirty (requires saving) and the package diagram is cleared out.
Wondering what EMF data is getting set/changed to cause the dirty editor?
--
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:
-----------------------------------------
Please attach your model project set.
> 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
[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 resolved TEIIDDES-1920.
------------------------------------
Resolution: Rejected
Was able to create proper connection profile (attached), connect to sybase, sample data (data tools) and import 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
> 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: bqt2_sybase_ase_CP.xml, 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:
-----------------------------------
Attachment: bqt2_sybase_ase_CP.xml
Data Tools Connection Profile for jconn4-26502.jar
> 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: bqt2_sybase_ase_CP.xml, 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 Paul Richardson (JIRA)
[ 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
12 years, 5 months