October 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-657) Transformation validation incorretly requires an updatable model element in an INSERT transformation.

by John Doyle (JIRA)

Transformation validation incorretly requires an updatable model element in an INSERT transformation. ------------------------------------------------------------------------------------------------------ Key: TEIIDDES-657 URL: https://jira.jboss.org/browse/TEIIDDES-657 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.1 Reporter: John Doyle See: http://community.jboss.org/message/566009#566009 Update and Insert transformations could be implemented in many ways, not all require an updatable model element. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-654) NPE while deleting dynamic web project

by Lukas Jungmann (JIRA)

NPE while deleting dynamic web project -------------------------------------- Key: TEIIDDES-654 URL: https://jira.jboss.org/browse/TEIIDDES-654 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 7.1 Reporter: Lukas Jungmann -create an empty dynamic web project in JBDS (4.0.0.v201010061543R-H31-Beta1) -delete it including sources => error log says: java.lang.NullPointerException at com.metamatrix.modeler.internal.ui.editors.ModelEditorProjectListener.resourceChanged(ModelEditorProjectListener.java:34) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:261) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:321) at org.eclipse.core.internal.resources.Resource.broadcastPreDeleteEvent(Resource.java:1993) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:771) at org.eclipse.core.internal.resources.Project.delete(Project.java:331) at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:130) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-686) Error Message for Failed VDB Deployment Refers to Previously Deployed VDB

by Ted Jones (JIRA)

Error Message for Failed VDB Deployment Refers to Previously Deployed VDB -------------------------------------------------------------------------- Key: TEIIDDES-686 URL: https://jira.jboss.org/browse/TEIIDDES-686 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.1 Reporter: Ted Jones Attachments: Screenshot-vdbdeploy .png I deployed a VDB successfully and later deployed a VDB that failed. The top-level error message referred to the successfully deployed VDB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-593) Release 7.1.1 Code-maintenance and cleanup. I18n, etc....

by Barry LaFond (JIRA)

Release 7.1.1 Code-maintenance and cleanup. I18n, etc.... --------------------------------------------------------- Key: TEIIDDES-593 URL: https://jira.jboss.org/browse/TEIIDDES-593 Project: Teiid Designer Issue Type: Task Components: Housekeeping Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 7.1.1 Bucket for I18n warning, unused variables, non-thrown exception warnings, etc... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-664) Creating XML doc model from XSD gets ugly error (big red X) instead of reasonable message

by Paul Nittel (JIRA)

Creating XML doc model from XSD gets ugly error (big red X) instead of reasonable message ----------------------------------------------------------------------------------------- Key: TEIIDDES-664 URL: https://jira.jboss.org/browse/TEIIDDES-664 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Paul Nittel Fix For: 7.1.1 Attachments: BigRedX.png, PartsXmlSchemaProject.zip, Screenshot-Confirm Multiple Resource Delete .png Using the attached Model Project Set, when I create a document model using the PartOrder root element, the result is a dialog consisting of a Big Red X (see attached screenshot). There is no accompanying exception or error message. When the dialog is dismissed, another dialog appears, asking if I'm sure I want to delete 0 resources (this screenshot is also attached). I have no idea what is causing this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-679) Operation Editor won't save Input Variables

by John Doyle (JIRA)

Operation Editor won't save Input Variables ------------------------------------------- Key: TEIIDDES-679 URL: https://jira.jboss.org/browse/TEIIDDES-679 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: JBDS 3.1 Beta 1, RHEL 5 Reporter: John Doyle Priority: Blocker I'm running the E2E Updatable Web Service script. When defining a the InsertProduct web service operation in the Operation Editor I got into a case where the SQL would not resolve because there were no Input Variables defined. I Added the Input Variables by clicking Edit variables and selecting all of the elements defined in the Product element. When returning to the Operation Editor I see that the selection I've made have been added as variables, but they disappear from view when I either save the model or click Save/Validate SQL. I've deleted and recreated operation several times, and unable to get past this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-666) Designer importer fails to correctly import metadata from Sybase when using the JConnect driver

by Paul Nittel (JIRA)

Designer importer fails to correctly import metadata from Sybase when using the JConnect driver ----------------------------------------------------------------------------------------------- Key: TEIIDDES-666 URL: https://jira.jboss.org/browse/TEIIDDES-666 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1.1 Reporter: Paul Nittel Fix For: 7.1.1 We have found that importing from sybase using their JConnect driver fails to correctly import metadata. (It doesn't see the user tables.) However, using DTP and the connection built by the import process, we can successfully query the database. So the connection is good and the database accessible. If I use the generic JTDS driver, it's all good (from what I've seen). I can provide drivers for your use, if necessary. Connection info: jdbc:sybase:Tds:slntds17.mm.atl2.redhat.com:5000/bqt2 jdbc:jtds:sybase://slntds17.mm.atl2.redhat.com:5000/bqt2 Username is bqt2; password is metamatrix -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
11
0 / 0

[JBoss JIRA] Created: (TEIIDDES-550) Import DDL to Relational Table misses columns for primary, foreign keys

by Paul Nittel (JIRA)

Import DDL to Relational Table misses columns for primary, foreign keys ----------------------------------------------------------------------- Key: TEIIDDES-550 URL: https://jira.jboss.org/browse/TEIIDDES-550 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, TeiidDesigner 7.1 M1 Reporter: Paul Nittel Attachments: motels.ddl I imported the motels.ddl example file to populate the foo model. When finished importing, I had a number of errors where the importer had created primary and foreign keys without specifying columns for those keys. In one case, here's the DDL: CREATE TABLE CustomerFamilyHistory ( customerfamilyhistoryid number(10) CONSTRAINT customerfamilyhistoryid_pk PRIMARY KEY, firstname varchar2(50) NOT NULL, lastname varchar2(50) NOT NULL, age number(3), sibling varchar2(20), customerid number(7) NOT NULL ); The primary key, customerfamilyhistoryid_pk, is created, but no reference to customerfamilyhistoryid is provided. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-678) Issues after Refactoring Source Model Name

by Ted Jones (JIRA)

Issues after Refactoring Source Model Name ------------------------------------------ Key: TEIIDDES-678 URL: https://jira.jboss.org/browse/TEIIDDES-678 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Reporter: Ted Jones I have three VDB's... all with the same three models in them with different combinations of visibility. 1. BQT (Source Model) 2. PART (Source Model) 3. VIRT (View Model) If I re-factor the PART model name to PARTS I see the following: 1. My transformation query changed from SELECT * FROM PART.PARTS to SELECT * FROM PARTS.PARTSS 2. I can't consistently produce this one, but the third or first VDB has the new model name added but leaves the old one as well. So I end up with a PART and a PARTS. 3. When I click the synch button on PART in the vdb editor, I get an illegal argument exception. 4. When I try to remove PART, the VIRT model gets removed to because the Designer thinks there is still a dependency on PART by VIRT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-541) Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview

by Paul Nittel (JIRA)

Table data preview requires all models in project to be without validation errors - should pertain only to models required for preview -------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-541 URL: https://jira.jboss.org/browse/TEIIDDES-541 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid 7.1M1 Reporter: Paul Nittel Attachments: LogWithPreviewErrors.log While in the middle of creating a virtual model, I attempted to preview data from an imported source model. Because the virtual model was incomplete, and thus failed validation, the preview was not possible. This is a valid use case. Preview of a model's tables should always work assuming invalid models are not required for the preview itself. Attaching the Designer's log file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2010