March 2009 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-42) Searching By Type In Relationship Search Does Not Return Results

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-42?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-42: --------------------------------- Fix Version/s: 6.1.0 Assignee: (was: Dan Florian) > Searching By Type In Relationship Search Does Not Return Results > ---------------------------------------------------------------- > > Key: TEIIDDES-42 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-42 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Reporter: Dan Florian > Fix For: 6.1.0 > > > Executing a Relationship search with a type selected does not return results. I created a model with 2 base tables. I created a "Generic" relationship type association between those tables. When I do a relationship search trying to find all "Generic" relationships I get no results. When I search to find all relationships I get this relationship. This is also a problem in release 5.5.3. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-44) invalid Menu Extension (Path: 'org.eclipse.search.menu' is invalid): com.metamatrix.modeler.internal.ui.actions.FindModelObjectAction

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-44?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-44: --------------------------------- Fix Version/s: 6.0.0 Assignee: Dan Florian > invalid Menu Extension (Path: 'org.eclipse.search.menu' is invalid): com.metamatrix.modeler.internal.ui.actions.FindModelObjectAction > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-44 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-44 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 6.0.0 > Environment: Designer running in IDE on Windows > Reporter: Warren Gibson > Assignee: Dan Florian > Priority: Minor > Fix For: 6.0.0 > > Attachments: invalidMenuExtension.zip > > > Found this in Designer Message log but unfortunately the log was deleted later. Don't know if this will be of much help. > Plug-in 'com.metamatrix.modeler.ui' contributed an invalid Menu Extension (Path: 'org.eclipse.search.menu' is invalid): com.metamatrix.modeler.internal.ui.actions.FindModelObjectAction -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-30) Saving the "Model" does not save un-saved transformation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-30?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-30: --------------------------------- Fix Version/s: 6.1.0 > Saving the "Model" does not save un-saved transformation > -------------------------------------------------------- > > Key: TEIIDDES-30 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-30 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Fix For: 6.1.0 > > > When you added a transformation, there is "save/validate" button on the transformation editor for saving the transformation. However, instead of that button you used the model save button on the top tool bar, this does not save the transformation. > 1) At this point if you exit the designer it does not warn you that I have a unsaved transformation > 2) once the designer re-started the transformation is gone. > I think saving the model should save any other editors underneath that model. > (IGNORE...) -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-31) Creating a model containing only a procedure does not create the required IMPORTs

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-31?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-31: --------------------------------- Fix Version/s: Future > Creating a model containing only a procedure does not create the required IMPORTs > --------------------------------------------------------------------------------- > > Key: TEIIDDES-31 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-31 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 6.0.0 > Environment: fedora 10 > Reporter: Paul Nittel > Priority: Minor > Fix For: Future > > Attachments: FedTools58_MPS.zip > > > Excuse this one if it's being carried over from the Trakka where it may still reside... > Modeling the Dynamic SQL test goes like this: > Import Physical source > Create a View model of the Customer > Create a View model containing the procedure > Create a VDB > Add the View model that has the procedure. > That's all that winds up in the VDB. You must manually add the required models. > Model project set is attached for your convenience. > Barry took a look at this and noticed the model was missing imports, which is why the VDB acted as it did. UPDATE IMPORTS had no effect, 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-28) Upgrade Designer's connection framework to latest GEF behavior

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-28?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-28: --------------------------------- Fix Version/s: Future Affects Version/s: 6.0.0 (was: Future) > Upgrade Designer's connection framework to latest GEF behavior > -------------------------------------------------------------- > > Key: TEIIDDES-28 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-28 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Barry LaFond > Fix For: Future > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Eclipse's GEF AbstractGraphicalEditPart.addTargetConnection() & addSourceConnection() were changed since Eclipse 3.1.2 timeframe to include calls to remove the connection if it already exists. > Initial/temp fix was to override these latest methods in AbstractDefaultEditPart to revert to 3.1.2 GEF code. > We need to investigate and adapt to the new/changed GEF connection framework and behavior -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-28) Upgrade Designer's connection framework to latest GEF behavior

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-28?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-28: --------------------------------- Affects Version/s: Future (was: 6.0.0) > Upgrade Designer's connection framework to latest GEF behavior > -------------------------------------------------------------- > > Key: TEIIDDES-28 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-28 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: Future > Reporter: Barry LaFond > Original Estimate: 1 week > Remaining Estimate: 1 week > > Eclipse's GEF AbstractGraphicalEditPart.addTargetConnection() & addSourceConnection() were changed since Eclipse 3.1.2 timeframe to include calls to remove the connection if it already exists. > Initial/temp fix was to override these latest methods in AbstractDefaultEditPart to revert to 3.1.2 GEF code. > We need to investigate and adapt to the new/changed GEF connection framework and behavior -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-18) UnsupportedOperationException when importing from Rose

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-18?page=com.atlassian.jira.pl... ] Barry LaFond updated TEIIDDES-18: --------------------------------- Fix Version/s: 6.1.0 > UnsupportedOperationException when importing from Rose > ------------------------------------------------------ > > Key: TEIIDDES-18 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-18 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Environment: fedora 10 > Reporter: Paul Nittel > Assignee: Johnny Verhaeg > Fix For: 6.1.0 > > Attachments: PartsSupplierLogical.mdl > > > I tried to import PartsSupplierLogical.mdl (attached) and received this exception: > !ENTRY com.metamatrix.rose 4 0 2008-12-15 10:55:10.304 > !MESSAGE java.lang.UnsupportedOperationException > !STACK 0 > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > Dec 15, 2008 10:55:09.870 [ModalContext|0] ERROR <com.metamatrix.rose|0> java.lang.UnsupportedOperationException > java.lang.UnsupportedOperationException > at org.eclipse.uml2.common.util.DerivedEObjectEList$DerivedListIterator.add(DerivedEObjectEList.java:278) > at java.util.AbstractSequentialList.add(AbstractSequentialList.java:129) > at org.eclipse.uml2.common.util.DerivedEObjectEList.addUnique(DerivedEObjectEList.java:636) > at org.eclipse.uml2.common.util.DerivedEObjectEList.add(DerivedEObjectEList.java:623) > at java.util.AbstractList.add(AbstractList.java:91) > at com.metamatrix.rose.internal.handler.UmlHandler.createPackage(UmlHandler.java:773) > at com.metamatrix.rose.internal.handler.AbstractRoseHandler.visitObject(AbstractRoseHandler.java:261) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:45) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseList(RoseWalker.java:52) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:67) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:63) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverseObject(RoseWalker.java:46) > at org.eclipse.emf.importer.rose.builder.RoseWalker.traverse(RoseWalker.java:40) > at com.metamatrix.rose.internal.RoseImporter.parseUnits(RoseImporter.java:876) > at com.metamatrix.rose.internal.RoseImporter.parseSelectedUnits(RoseImporter.java:605) > at com.metamatrix.rose.internal.ui.wizard.RoseImportWizard$4.run(RoseImportWizard.java:362) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > While it appears to continue, if you clickpast the exception, it just hangs. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-110) Preview does not allow leaving fields null for nullable columns in an access pattern

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-110?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-110: ---------------------------------- Component/s: Data Preview Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Preview does not allow leaving fields null for nullable columns in an access pattern > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-110 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-110 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 6.0.0 > Environment: 5.5.3GA Designer on Linux > Reporter: Greg Haber > Assignee: Dan Florian > Fix For: 6.0.0 > > Attachments: oracleTest_20081210_1.zip > > > If an access pattern contains a nullable column (and this probably also holds for procedure input parameters), then Preview doesn't have an option to leave the value blank (to specify null). If you enter the string "null" into the field for that column, it will send the string "null". Not sure on how semantics of this should work (whether leaving the field blank should be the equivalent of specifying null, or whether we should use the string "null", or whether there should be a checkbox for saying that the value is null), so whatever makes sense. > However regardless on how the UI works this should result in a WHERE colname IS NULL criteria in the resulting query. > I know we aren't trying to tackle all edge cases with preview, but this is a common case with web service parameters (it is common to have required and nillable parameters). > This one depends on JBEDSP-855 getting resolved first. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-19) WSDL to Relational Importer is throwing ClassCastEx

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-19?page=com.atlassian.jira.pl... ] John Doyle closed TEIIDDES-19. ------------------------------ Confirmed > WSDL to Relational Importer is throwing ClassCastEx > --------------------------------------------------- > > Key: TEIIDDES-19 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-19 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: 6.0.0 > Environment: CSB Dev build > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.0.0 > > > The WSDl to Relational importer is throwing a ClassCastEx when modeling operations. It is getting different versions of the javax.xml.namespace.QName class loded from different plugins. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-40) WSDL to Relational Importer dies upon startup.

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-40?page=com.atlassian.jira.pl... ] John Doyle closed TEIIDDES-40. ------------------------------ Validated > WSDL to Relational Importer dies upon startup. > ---------------------------------------------- > > Key: TEIIDDES-40 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-40 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: 6.0.0 > > -- 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

15 years, 9 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