April 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-419) Create notion of Set Default Server action to be used for VDB execution and Preview

by Barry LaFond (JIRA)

Create notion of Set Default Server action to be used for VDB execution and Preview ----------------------------------------------------------------------------------- Key: TEIIDDES-419 URL: https://jira.jboss.org/jira/browse/TEIIDDES-419 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Blocker Fix For: 7.0 Because ability to have multiple servers in Designer for 7.0 AND the requirement to utilize VDB's for both preview and execution AND the fact that VDB's require a "Server" to be deployed and queried from, its become apparent that we need a notion of a "Default" server from which these actions are performed. 1) Create a "Set Default Server" action 2) Persist this server (can be null) with the Server Manager 3) Decorate this "Server" in Connectors View differently than other servers -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-235) Order of operations problem in Designer

by Mark Drilling (JIRA)

Order of operations problem in Designer --------------------------------------- Key: TEIIDDES-235 URL: https://jira.jboss.org/jira/browse/TEIIDDES-235 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 6.0.0 Reporter: Mark Drilling The following query when entered into the transformation editor: select * from dips_view.cards LEFT OUTER JOIN CramerXRefData.CardTypes ON card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE IS NULL OR card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE = device_pk is parsed as; SELECT * FROM DIPS_View.Cards LEFT OUTER JOIN CramerXRefData.CardTypes ON ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE IS NULL)) OR ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE = Device_PK)) The ordering of different variations of CompoundCriteria are not preserved correctly. -- 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, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-429) NPE selecting file in explorer that has no file extension

by Barry LaFond (JIRA)

NPE selecting file in explorer that has no file extension --------------------------------------------------------- Key: TEIIDDES-429 URL: https://jira.jboss.org/jira/browse/TEIIDDES-429 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Create File resource under some Model Project in Desginer Select that file in explorer and receive the following NPE: java.lang.NullPointerException at com.metamatrix.modeler.internal.ui.actions.DeleteResourceAction.isValidSelection(DeleteResourceAction.java:861) at com.metamatrix.modeler.internal.ui.actions.DeleteResourceAction.selectionChanged(DeleteResourceAction.java:799) at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156) at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) Simple code fix in DeleteResourceAction -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-296) XSD to Relational importer fails on simple schema import.

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-296?page=com.atlassian.jira.p... ] John Doyle updated TEIIDDES-296: -------------------------------- Fix Version/s: 7.0 > XSD to Relational importer fails on simple schema import. > --------------------------------------------------------- > > Key: TEIIDDES-296 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-296 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Environment: Linux Designer on RHEL-CSB > Reporter: John Doyle > Assignee: John Doyle > Fix For: 7.0 > > Attachments: XSDImportFailure.zip > > > Use the XML Schema as relational source model importer on pos.xsd in the attached model set. It produces this exception when generating the model. > java.lang.NullPointerException > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicSet(BasicEObjectImpl.java:558) > at com.metamatrix.modeler.internal.core.ObjectExtension.eDynamicSet(ObjectExtension.java:90) > at com.metamatrix.modeler.modelgenerator.xml.modelextension.impl.BaseXMLRelationalExtensionManagerImpl.setNamespacePrefixesAttribute(BaseXMLRelationalExtensionManagerImpl.java:38) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNamespacePrefixesAttribute(XmlSchemaAsRelationalModelProcessor.java:327) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setTableNamespacePrefixes(XmlSchemaAsRelationalModelProcessor.java:273) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewTable(XmlSchemaAsRelationalModelProcessor.java:96) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewEntity(XmlSchemaAsRelationalModelProcessor.java:75) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNameAndNameInSource(XmlSchemaAsRelationalModelProcessor.java:65) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1058) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:804) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:326) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:547) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:587) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:333) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:311) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.modelgenerator.xml.wizards.XsdAsRelationalImportWizard$1.run(XsdAsRelationalImportWizard.java:504) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Work stopped: (TEIIDDES-296) XSD to Relational importer fails on simple schema import.

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-296?page=com.atlassian.jira.p... ] Work on TEIIDDES-296 stopped by John Doyle. > XSD to Relational importer fails on simple schema import. > --------------------------------------------------------- > > Key: TEIIDDES-296 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-296 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Environment: Linux Designer on RHEL-CSB > Reporter: John Doyle > Assignee: John Doyle > Fix For: 7.0 > > Attachments: XSDImportFailure.zip > > > Use the XML Schema as relational source model importer on pos.xsd in the attached model set. It produces this exception when generating the model. > java.lang.NullPointerException > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicSet(BasicEObjectImpl.java:558) > at com.metamatrix.modeler.internal.core.ObjectExtension.eDynamicSet(ObjectExtension.java:90) > at com.metamatrix.modeler.modelgenerator.xml.modelextension.impl.BaseXMLRelationalExtensionManagerImpl.setNamespacePrefixesAttribute(BaseXMLRelationalExtensionManagerImpl.java:38) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNamespacePrefixesAttribute(XmlSchemaAsRelationalModelProcessor.java:327) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setTableNamespacePrefixes(XmlSchemaAsRelationalModelProcessor.java:273) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewTable(XmlSchemaAsRelationalModelProcessor.java:96) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewEntity(XmlSchemaAsRelationalModelProcessor.java:75) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNameAndNameInSource(XmlSchemaAsRelationalModelProcessor.java:65) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1058) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:804) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:326) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:547) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:587) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:333) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:311) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.modelgenerator.xml.wizards.XsdAsRelationalImportWizard$1.run(XsdAsRelationalImportWizard.java:504) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-317) MetaMatrix Deisgner error: Save All Failed: provider net.sf.saxon. TransformerFactoryImpl not found

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-317?page=com.atlassian.jira.p... ] Barry LaFond closed TEIIDDES-317. --------------------------------- Resolution: Cannot Reproduce Bug This JIRA was created when Teiid Designer was in limbo and before 6.0 open source release. Have not been able to reproduce since. > MetaMatrix Deisgner error: Save All Failed: provider net.sf.saxon. TransformerFactoryImpl not found > ------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-317 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-317 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: Future > Environment: Designer build 3045 > Reporter: Warren Gibson > Assignee: Barry LaFond > Attachments: ScreenShot017.JPG, Staging.zip > > > 1.Deleted a previously created VDB (StagingVDB) in Designer. > 2.Deleted the old project in the Repository. > 3.Did some modeling and created a new VDB (StagingVDB) in Designer. > 4.Added new project to the Repository. > 5.Forgot to save the VDB before attempting to add project to Repository. VDB was not added. > 6.Attempted to save the VDB so I could add it to the repository. > 7.Received the error: Save All Failed: Provider net.sf.saxon. TransformerFactoryImpl not found. > 8.The Problem Tab shows "The VDB has no models" but the Overview Tab shows models. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-309) Designer: Improve the XML Results Viewer

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-309?page=com.atlassian.jira.p... ] Barry LaFond updated TEIIDDES-309: ---------------------------------- Summary: Designer: Improve the XML Results Viewer (was: Designer: Improve the XML Viewer) > Designer: Improve the XML Results Viewer > ---------------------------------------- > > Key: TEIIDDES-309 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-309 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Mark Drilling > Assignee: Dan Florian > Priority: Minor > > Request to improve the XML results view in Designer to have collapsible elements like a browser view. Also, buttons to expand all / collapse all nodes. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-289) Designer shows view for Cheat Sheets which no longer exists

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-289?page=com.atlassian.jira.p... ] Barry LaFond closed TEIIDDES-289. --------------------------------- Resolution: Done Teiid 7.0 Feature set will make this JIRA irrelevant. Designer will be integrated into basic Eclipse environments and cheat sheets will always be available. Won't Fix > Designer shows view for Cheat Sheets which no longer exists > ----------------------------------------------------------- > > Key: TEIIDDES-289 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-289 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: Designer RC2 Windows environment > Reporter: Warren Gibson > Priority: Minor > > Designer still shows a view for Cheat Sheet. You can get to it via: Windows/Show View/Other/Cheat Sheet -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-318) VDB Sync - Thinks model has not been validated and produces errors after Rebuild All

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-318?page=com.atlassian.jira.p... ] Barry LaFond closed TEIIDDES-318. --------------------------------- Resolution: Won't Fix Teiid 7.0 Feature set will make this JIRA irrelevant. VDB editor validation and management has been totally rewritten. > VDB Sync - Thinks model has not been validated and produces errors after Rebuild All > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-318 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-318 > Project: Teiid Designer > Issue Type: Bug > Components: Build > Affects Versions: Future > Environment: Designer build 3045 > Reporter: Warren Gibson > Assignee: Barry LaFond > Attachments: Parts.zip, ScreenShot019.JPG, ScreenShot021.JPG, workspace-13_45_58_Jul_09_1.log > > > 1. Testing E2E Virtual Procedures Test Script > 2. Added Parts Project from examples folder. > 3. Added several new procedures to PartsVirtual.xmi per > the test script. > 4. Validated each procedure as they were added and did a save all. > 5. Once all procedures were completed the PartsVirtual had no errors. > 6. Opened PartsSupplier_VDB to Sync it per the script. > 7. When attempting to Sync the VDB I got: The model Parts Project/PartsVirtual.xmi has not > been validated. Use Project -> Rebuild All to validate. Adding Models to VDB halted. See attached screen shot. > 8. When I attempted the Rebuild All it produced several errors in the Problems tab and put PartsVirtual > in an error state. See attachment screen shot. > 9. The only log I could find is attached along with a zip of the project. -- 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, 6 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 April 2010