June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-407) Replace Designer's workspace source binding management framework with Server-managed framework

by Barry LaFond (JIRA)

Replace Designer's workspace source binding management framework with Server-managed framework ---------------------------------------------------------------------------------------------- Key: TEIIDDES-407 URL: https://jira.jboss.org/jira/browse/TEIIDDES-407 Project: Teiid Designer Issue Type: Sub-task Components: Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Source bindings were managed in 6.3 Designer. The Teiid API provides assignBindingToModel() method for VDB's deployed to Teiid. By creating a "hidden" VDB for each running Server, we can manager these source bindings via that hidden VDB. This will required Creating the hidden VDB, managing it's life cycle, providing utility methods to assign/remove source bindings based on model edits (Delete/Rename) etc.. -- 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

14 years, 6 months

1
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-486) NPE creating new Model Project with a Vdb Editor open for VDB from another project.

by Barry LaFond (JIRA)

NPE creating new Model Project with a Vdb Editor open for VDB from another project. ----------------------------------------------------------------------------------- Key: TEIIDDES-486 URL: https://jira.jboss.org/browse/TEIIDDES-486 Project: Teiid Designer Issue Type: Bug Reporter: Barry LaFond Priority: Critical Fix For: 7.1 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". !STACK 0 java.lang.NullPointerException at org.teiid.designer.vdb.VdbEntry$1.resourceChanged(VdbEntry.java:76) 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:249) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:307) at org.eclipse.core.internal.resources.Project.close(Project.java:165) at com.metamatrix.modeler.ui.wizards.NewModelProjectWizard.performFinish(NewModelProjectWizard.java:104) -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-485) VDB is marked "dirty" if a model contained in the VDB is changed and saved

by Paul Nittel (JIRA)

VDB is marked "dirty" if a model contained in the VDB is changed and saved -------------------------------------------------------------------------- Key: TEIIDDES-485 URL: https://jira.jboss.org/browse/TEIIDDES-485 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: Fedora 12, OpenJDK, Designer 6/28 Reporter: Paul Nittel Attachments: SynchronizeThis.zip With a VDB open in its editor, modify and save one of the models contained in the VDB. When the model is saved, the VDB will be shown as "dirty". While the VDB should show that model as needing synchronization, the VDB should not be "dirty" until it's been changed. A model project set will be attached for your debugging convenience. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-483) Saving a modification to a workspace model that has been added to a VDB causes VDB to be modified

by John Verhaeg (JIRA)

Saving a modification to a workspace model that has been added to a VDB causes VDB to be modified ------------------------------------------------------------------------------------------------- Key: TEIIDDES-483 URL: https://jira.jboss.org/browse/TEIIDDES-483 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.0 Reporter: John Verhaeg Fix For: 7.1 Once I save a model that has been added to a VDB, the VDB becomes dirty. -- 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

14 years, 6 months

2
1
0 / 0

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

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-296?page=com.atlassian.jira.plugin... ] Barry LaFond updated TEIIDDES-296: ---------------------------------- Fix Version/s: 7.1 (was: 7.0) > XSD to Relational importer fails on simple schema import. > --------------------------------------------------------- > > Key: TEIIDDES-296 > URL: https://jira.jboss.org/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.1 > > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-460) Convert Legacy Web Services to CXF

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-460?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIIDDES-460: ------------------------------- Fix Version/s: 7.1 (was: 7.0) > Convert Legacy Web Services to CXF > ---------------------------------- > > Key: TEIIDDES-460 > URL: https://jira.jboss.org/browse/TEIIDDES-460 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 6.2.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.1 > > > Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-412) Expose Bound Workspace models in Execution View for each Teiid Server

by Barry LaFond (JIRA)

Expose Bound Workspace models in Execution View for each Teiid Server --------------------------------------------------------------------- Key: TEIIDDES-412 URL: https://jira.jboss.org/jira/browse/TEIIDDES-412 Project: Teiid Designer Issue Type: Sub-task Components: VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 To assist the user in both creating/changing and viewing workspace source-to-connector bindings, show a "workspace models" root under each Teiid Server root showing each bound model and it's current connector binding. The reverse of this is to maintain a "connector-to-source" binding object in the Model Explorer view for each source model. (if bound) -- 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

14 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-408) Adapt Designer's Connector framework to Teiid JCA connector changes

by Barry LaFond (JIRA)

Adapt Designer's Connector framework to Teiid JCA connector changes ------------------------------------------------------------------- Key: TEIIDDES-408 URL: https://jira.jboss.org/jira/browse/TEIIDDES-408 Project: Teiid Designer Issue Type: Sub-task Components: Import/Export, Teiid Integration, VDB & Execution Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Designer's access to old Teiid "ConnectorBinding","ComponentType" and "ComponentTypeID" are now gone and replaced with: ConnectorBinding ConnectorType Need to re-place with new classes and utilize direct access to Teiid via API. - Replace ConfigurationManager with Server Manager and Execution Manager classes - Wrap Connector Bindings and Connector Types to faciliate re-use of some of existing framework. - (minimum impact) - Create and manage "Server" objects - Remove all "Jar" management functionality from Designer (UDF's and JDBC Drivers (see 9)) - Connector Validation - Reimplement binding creation for the WSDL to Relational importer around new admin API. (TEIIDDES-265) -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-312) Modeler Help appears to not be "wired up"

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-312?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-312. ----------------------------------- Resolution: Cannot Reproduce Bug Latest 7.0 CR1 kit seems to work. Marking as NOT reproduceable. > Modeler Help appears to not be "wired up" > ----------------------------------------- > > Key: TEIIDDES-312 > URL: https://jira.jboss.org/browse/TEIIDDES-312 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Environment: fedora 10 through Eclipse IDE > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 7.0 > > > Clicking on the various Help menu items provides little to no help. > Help > Search for "Transformation" brings up a possible list of topics (what does "[MMHeader]" mean?). Clicking on them brings up a dialog proclaiming the connection was refused when it tried to connect to 127.0.0.1. > Help > Help Contents has no visible effect. Not even an exception. > Help > Dynamic Help, like Contents, appears to work until you click the link and can't connect to 127.0.0.1. -- 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

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-263) Perform general housekeeping duties on 7.0 Codebase. Remove unnecessary code (class, methods and fields) refactor, repackage, etc.

by Barry LaFond (JIRA)

Perform general housekeeping duties on 7.0 Codebase. Remove unnecessary code (class, methods and fields) refactor, repackage, etc. ---------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-263 URL: https://jira.jboss.org/jira/browse/TEIIDDES-263 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 Teiid Designer code-base is basically 10 years old. Included are recent inherited code from Teiid. We need to perform basic house-cleaning duties to make sure we don't carry forward any more code than we need to. So: 1) Remove unnecessary code 2) Repackage code into plugins and packages that make sense 3) Clarify "internal" code in our packaging scheme -- 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

14 years, 6 months

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010