[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2460.
----------------------------------
> JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2460
> URL: https://issues.jboss.org/browse/TEIIDDES-2460
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.0.3, 9.2
>
> Attachments: ErrorDialog.png, TEIIDDES2460.zip
>
>
> When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised
> Version-Release number of selected component (if applicable):
> Actual results:
> Imported schema has changed integer data type to biginteger data type.
> Expected results:
> Imported schema will be identical to original schema.
> Additional info:
> Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2480) LDAP importer fails silently when no location is explicitly entered for the new model
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2480?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2480:
-----------------------------------
Priority: Blocker (was: Major)
> LDAP importer fails silently when no location is explicitly entered for the new model
> -------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2480
> URL: https://issues.jboss.org/browse/TEIIDDES-2480
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Marc Shirley
> Assignee: Paul Richardson
> Priority: Blocker
> Fix For: 9.0.4, 9.2
>
>
> LDAP import fails silently when no location is entered for the "Source Model Definition" section's "Location" field on the first page of the wizard. This occurs even when using the context menu to initiate from a specific project or child object level. The wizard functions as expected until you finish, at which point the model is never generated. No error dialog or failure notification is presented to the user. checking error log shows:
> java.lang.NullPointerException
> at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.createNewModelResource(RelationalModelBuilder.java:65)
> at org.teiid.designer.modelgenerator.ldap.RelationalModelBuilder.modelEntries(RelationalModelBuilder.java:109)
> at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizardManager.createModel(LdapImportWizardManager.java:384)
> at org.teiid.designer.modelgenerator.ldap.ui.wizards.LdapImportWizard$1.run(LdapImportWizard.java:158)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months
[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2326:
-----------------------------------
Fix Version/s: 9.0.5
9.3
(was: 9.0.4)
> REST/SOAP importers - Re use of the connection profile after restart
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2326
> URL: https://issues.jboss.org/browse/TEIIDDES-2326
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.0.5, 9.3
>
> Attachments: nomodel.png
>
>
> Often times, as user I start the import of WSDL based or REST (with new one, or old with file and URL selection) service and go through the wizard, something does not work right. So, I typically remove the models generated, and then try the import process again. However, next time when I select the same connection profile I created before, I very seldom get same results. If I restarted the Designer for any reason, the previously created connection profile for sure does not work.
> It seems to me that, designer stores a temp XML/JSON file from where it starts processing, during the restart that gets deleted and import process instead of sending another request for the results document it fails with arbitrary error. There is no way to recover form it. IMO, REST and SOAP needs to be treated differently from XML File type sources and issue the query to get response document, not store it anywhere.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 10 months