March 2009 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-102) Using clear transformation button causes refresh/repaint issues in transformation diagram

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-102?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-102: ---------------------------------- Fix Version/s: Future Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Using clear transformation button causes refresh/repaint issues in transformation diagram > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-102 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-102 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: Future > > > After using the clear transformation button, all changes require the refresh button to be manually pressed to update the transformation diagram. This affects all models/diagrams, not just the model whose transformation was cleared. > Tested during E2eYahooUdfTestScript.odt by clearing transformation of MyPortfolio.Positions and then pasting new transformation into editor. Renaming the column directly in the diagram did not cause a refresh. Tried to create a new model with a new base table, and the changes would not update correctly there either. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-103) Model is still created when canceling the creation of new web service model from WSDL

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-103?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-103: ---------------------------------- Component/s: Import/Export Fix Version/s: Future Affects Version/s: 6.0.0 > Model is still created when canceling the creation of new web service model from WSDL > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-103 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-103 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Reporter: Li Liang > Fix For: Future > > > Follow Web Service Model Wizard Test Spec. > 1. Start the New Model Wizard: File -> New -> Metadata Model. > 2. Select a location and create a file name for the new model. > 3. Choose the "Web Service" metamodel and the "Virtual Model" model type. > 4. Select the "Build from existing WSDL file(s)" model builder. > 5. Click "Next." This will take you to the first page of the Web Service model builder's contribution to the new model wizard. > 6. Click the "Cancel" button > Model should not be created in the workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-104) In Web Service Operation Editor, using F2 to rename the selected Input Variable renames the Operation instead

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-104?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-104: ---------------------------------- Component/s: Modeling Fix Version/s: Future Affects Version/s: 6.0.0 > In Web Service Operation Editor, using F2 to rename the selected Input Variable renames the Operation instead > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-104 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-104 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Environment: 5.5.3 Designer > Reporter: Jerry Helbling > Priority: Minor > Fix For: Future > > > In Web Service Operation Editor, using F2 to rename the selected Input Variable renames the Operation instead. Right click - Rename works fine, but many users are used to using F2 to rename. If we do not choose to support F2 when we have selected a variable in Input Variables, or an Operation in the Operations tree, then we should make sure it does nothing. If we do want to support F2 for renaming, then it should rename the selected object, not the Operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-99) Web Service View model transformation diagram does not paint correctly.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-99?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-99: --------------------------------- Component/s: Diagrams Fix Version/s: Future > Web Service View model transformation diagram does not paint correctly. > ----------------------------------------------------------------------- > > Key: TEIIDDES-99 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-99 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: 6.0.0 > Environment: Designer on Windows, Linux > Reporter: John Doyle > Priority: Minor > Fix For: Future > > Attachments: WS_transformation.bmp > > > After creating a new Web Service model, adding an Interface, operation, and IN/Out params, open the transformation diagram. The XML Document is placed on the wrong side of the diagram. See attachment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-96) "Connector Binding Automatically Assigned" Dialog Appears Multiple Times When Autoassigning Multiple Bindings

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-96?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-96: --------------------------------- Component/s: VDB & Execution Affects Version/s: 6.0.0 > "Connector Binding Automatically Assigned" Dialog Appears Multiple Times When Autoassigning Multiple Bindings > ------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-96 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-96 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Dan Florian > Priority: Minor > Fix For: 6.1.0 > > > In the E2E XML Book Catalog Test Script when adding the XML model to the newly created VDB, the "Connector Binding Automatically Assigned" Dialog appears twice (one on top of the other); once for each automatically assigned binding. This dialog should only appear once. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-93) Designer: ConnectorBindings panel - Combine import action icons into one

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-93?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-93: --------------------------------- Component/s: Views Fix Version/s: Future (was: 6.1.0) Affects Version/s: 6.0.0 > Designer: ConnectorBindings panel - Combine import action icons into one > ------------------------------------------------------------------------- > > Key: TEIIDDES-93 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-93 > Project: Teiid Designer > Issue Type: Feature Request > Components: Views > Affects Versions: 6.0.0 > Reporter: Mark Drilling > Priority: Minor > Fix For: Future > > > Implementation for 5.5.3 release has two separate import actions on the connector bindings panel. Request is to combine the 2 actions into a single action that can access either type of import. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-91) Designer - Deleting a project does not clean up all editors associated with that project.

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-91?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-91: --------------------------------- Component/s: Eclipse Integration Affects Version/s: 6.0.0 > Designer - Deleting a project does not clean up all editors associated with that project. > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-91 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-91 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 6.0.0 > Environment: Designer build 3045 running on Windows > Reporter: Warren Gibson > Assignee: Dan Florian > Priority: Minor > Fix For: 6.0.0 > > Attachments: ScreenShot024.JPG > > > 1. Deleted Parts project in Model Explorer. > 2. As can be seen in ScreenShot024 the PartsSupplier vdb editor is still open > and showing a query for PartsSupplier. > 3. I would suggest when a project is closed or deleted all the associated editors should also be closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-89) Designer hangs when executing a Web Service Operation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-89?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-89: --------------------------------- Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Designer hangs when executing a Web Service Operation > ----------------------------------------------------- > > Key: TEIIDDES-89 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-89 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: 6.1.0 > > Attachments: PartsProjectWebSvc.zip > > > Using the attached Model Project Set, I executed the Web service and used S101 and P304 as the Supplier and Part ids. When executed, it appears to hang and required the use of the System Monitor to kill it. > I _was_ able to successfully query the underlying virtual table and the XML document. And it works when deployed on a server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-83) Refactor > Move then UNDO getting Unable to execute Command : SetCommand

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-83?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-83: --------------------------------- Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Refactor > Move then UNDO getting Unable to execute Command : SetCommand > ------------------------------------------------------------------------ > > Key: TEIIDDES-83 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-83 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: 6.1.0 > > Attachments: SetCommandError_MPS.zip, UglyError.txt > > > I created a simple project with one source model and a view model. I'm doing Refactor > Move of the source model to ensure the view model remains viable. While doing this I'm getting hideous errors in the Message Log. Here's the top of the exception--the rest is attached, along with a Model Project Set. > Error 2008-04-30 14:26:51.321 Unable to execute Command : SetCommand (label: Set) (description: Set the value to the feature of the owner) (isPrepared: true) (isExecutable: false) (domain: com.metamatrix.modeler.internal.core.container.ContainerEditingDomain@165d9bd) (overrideCommand: null) (owner: com.metamatrix.metamodels.transformation.impl.SqlTransformationMappingRootImpl@1e3e4c5(inputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@30c68b (eProxyURI: file:/home/pnittel/mmx/553d080430/des/workspace/RefactorFolderFiles/F1/Parts_Supplier_Sybase_12_5.xmi#mmuuid/31e7e641-5e1e-10c9-a439-94c90911f2fb)], outputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)]) (outputReadOnly: false, topToBottom: false, commandStack: null)) (feature: org.eclipse.emf.ecore.impl.EReferenceImpl@cbffde (name: target) (ordered: true, unique: true, lowerBound: 0, upperBound: 1) (changeable: true, volatile: false, transient: false, defaultValueLiteral: null, unsettable: false, derived: false) (containment: false, resolveProxies: true)) (value: [/RefactorFolderFiles/F1/F11/Parts_Supplier_Sybase_12_5.xmi]) (oldValue: com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)) > Modeler Core Exception: Status ERROR: com.metamatrix.core code=0 Unable to execute Command : SetCommand (label: Set) (description: Set the value to the feature of the owner) (isPrepared: true) (isExecutable: false) (domain: com.metamatrix.modeler.internal.core.container.ContainerEditingDomain@165d9bd) (overrideCommand: null) (owner: com.metamatrix.metamodels.transformation.impl.SqlTransformationMappingRootImpl@1e3e4c5(inputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@30c68b (eProxyURI: file:/home/pnittel/mmx/553d080430/des/workspace/RefactorFolderFiles/F1/Parts_Supplier_Sybase_12_5.xmi#mmuuid/31e7e641-5e1e-10c9-a439-94c90911f2fb)], outputs: [com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)]) (outputReadOnly: false, topToBottom: false, commandStack: null)) (feature: org.eclipse.emf.ecore.impl.EReferenceImpl@cbffde (name: target) (ordered: true, unique: true, lowerBound: 0, upperBound: 1) (changeable: true, volatile: false, transient: false, defaultValueLiteral: null, unsettable: false, derived: false) (containment: false, resolveProxies: true)) (value: [/RefactorFolderFiles/F1/F11/Parts_Supplier_Sybase_12_5.xmi]) (oldValue: com.metamatrix.metamodels.relational.impl.BaseTableImpl@19b8858 (name: SUPPLIER_PARTS, nameInSource: SUPPLIER_PARTS) (system: false, cardinality: 227, supportsUpdate: false, materialized: false)) null > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeCommandInTransaction(ModelEditorImpl.java:1699) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-81) Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-81?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-81: --------------------------------- Component/s: VDB & Execution Affects Version/s: 6.0.0 Assignee: (was: Barry LaFond) > Importing a VDB into the Designer should add the Connector bindings to the Configuration Manager > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-81 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-81 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Enterprise Designer in Linux and Windows > Reporter: Debbie Steigner > Fix For: 6.1.0 > > > If you bring an existing VDB with Connector bindings assigned into the Designer, those bindings are never added to the Configuration Manager. They appear as if they are there when you look at the Execute screen but they are not and you have to create new. This will be very confusing for any evaluation customers that we are sending the training materials with existing vdbs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2009