January 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1218) Modify Built-In MEDs To Have A Scheme And A Year

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1218: ------------------------------------- Summary: Modify Built-In MEDs To Have A Scheme And A Year Key: TEIIDDES-1218 URL: https://issues.jboss.org/browse/TEIIDDES-1218 Project: Teiid Designer Issue Type: Task Components: Extension Framework Affects Versions: 7.6 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.7 The built-in MEDs should include the "http" scheme to enable the MED to be viewed, downloaded online if we decide to make that available. Also add a year at the end of the URI to function like a version. Change URIs to indicate if they are a design-time or runtime MED. With that in mind, recommend the following: - change the "rest" namespace prefix URI to "http://www.jboss.org/teiiddesigner/ext/rest/2012" - change the "salesforce" namespace prefix URI to "http://www.teiid.org/translator/salesforce/2012" - change the "sourceFunction" namespace prefix URI to "http://www.teiid.org/ext/relational/2012" - change the "ext-custom" namespace prefix URI to "http://www.jboss.org/teiiddesigner/ext/deprecated/2012" The "http://www.teiid.org/translator" URI will prefix all Teiid translator MED URIs. The "http://www.teiid.org/ext" URI will prefix all Teiid non-translator MEDs. The "http://www.jboss.org/teiiddesigner" URI will prefix all Designer MED URIs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (TEIIDDES-1227) Exception starting Designer with Empty VDB

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1227: -------------------------------------- Summary: Exception starting Designer with Empty VDB Key: TEIIDDES-1227 URL: https://issues.jboss.org/browse/TEIIDDES-1227 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.6 Reporter: Barry LaFond Assignee: Dan Florian Fix For: 7.7 Create project in workspace, create an EMPTY VDB, save and exit. Restart Designer and get following: !ENTRY org.teiid.designer.dqp 4 0 2012-01-25 10:45:42.647 !MESSAGE An error deleting orphaned Preview VDBs in "Project_A" occurred. !STACK 0 java.lang.RuntimeException: java.util.zip.ZipException: error in opening zip file at com.metamatrix.core.modeler.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:75) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:48) at org.teiid.designer.vdb.VdbUtil.isPreviewVdb(VdbUtil.java:71) at org.teiid.designer.runtime.preview.PreviewManager.isPreviewVdb(PreviewManager.java:248) at org.teiid.designer.runtime.preview.PreviewManager.findPvdbs(PreviewManager.java:595) at org.teiid.designer.runtime.preview.PreviewManager.handleModelProjectOpened(PreviewManager.java:809) at org.teiid.designer.runtime.preview.PreviewManager.done(PreviewManager.java:422) at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:39) at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:112) at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:152) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:647) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:71) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:127) at java.util.zip.ZipFile.<init>(ZipFile.java:88) at org.teiid.designer.vdb.VdbUtil$1.tryToDo(VdbUtil.java:88) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:38) ... 11 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1231) IllegalArgumentException on re-import of JDBC tables

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1231: -------------------------------------- Summary: IllegalArgumentException on re-import of JDBC tables Key: TEIIDDES-1231 URL: https://issues.jboss.org/browse/TEIIDDES-1231 Project: Teiid Designer Issue Type: Bug Components: Extension Framework, Import/Export Affects Versions: 7.6, 7.7 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.7 Received IllegalArgumentException while re-importing JDBC Source tables. The Compare part of the importer relies on both the existing Model and the Temporary model which is NOT in the basic workspace model container, so in this case the EmfModelObjectExtensionAssistant needs to be aware that ModelResource may be NULL at this point and is OK? java.lang.IllegalArgumentException: modelResource is null at com.metamatrix.core.util.CoreArgCheck.isNotNull(CoreArgCheck.java:139) at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.getModelResource(EmfModelObjectExtensionAssistant.java:62) at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.getSupportedNamespaces(EmfModelObjectExtensionAssistant.java:233) at org.teiid.designer.extension.ModelExtensionAssistantAggregator.getSupportedNamespacePrefixes(ModelExtensionAssistantAggregator.java:102) at org.teiid.designer.extension.ModelExtensionAssistantAggregator.getPropertyDefinitions(ModelExtensionAssistantAggregator.java:60) at org.teiid.designer.ui.properties.extension.ModelExtensionPropertySource.getPropertyDescriptors(ModelExtensionPropertySource.java:65) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getAllDescriptors(ModelObjectPropertySource.java:211) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getPropertyDescriptors(ModelObjectPropertySource.java:309) at com.metamatrix.modeler.compare.ui.tree.DifferenceDescriptorPanel$TableViewerLabelProvider.getColumnText(DifferenceDescriptorPanel.java:348) at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:70) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399) at org.eclipse.jface.viewers.CheckboxTableViewer.doUpdateItem(CheckboxTableViewer.java:168) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167) at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636) at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1508) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.CheckboxTableViewer.preservingSelection(CheckboxTableViewer.java:348) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465) at com.metamatrix.modeler.compare.ui.tree.DifferenceDescriptorPanel.updateTableRows(DifferenceDescriptorPanel.java:261) at com.metamatrix.modeler.compare.ui.tree.DifferenceDescriptorPanel.setDescriptor(DifferenceDescriptorPanel.java:238) at com.metamatrix.modeler.compare.ui.tree.DifferenceReportsPanel.updateDescriptorPanel(DifferenceReportsPanel.java:683) at com.metamatrix.modeler.compare.ui.tree.DifferenceReportsPanel$1.selectionChanged(DifferenceReportsPanel.java:406) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1725) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139) at com.metamatrix.modeler.compare.ui.tree.CompareTreePanel.doTreeSelection(CompareTreePanel.java:678) at com.metamatrix.modeler.compare.ui.tree.CompareTreePanel$6.run(CompareTreePanel.java:650) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1233: ---------------------------------------------- Bugzilla Update: Perform > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1233: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=785713 > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1233: ------------------------------------------ Looking at this a little more. I can confirm that the Teiid side works when the appropriate namespace settings are there. I can also see that the Designer logic is always checking for XSDComponents, which will not be present when hand generating a document model. > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1233: ------------------------------------- Assignee: (was: Steven Hawkins) Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema. > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1233: ------------------------------------- Attachment: foo.zip Model project zip with a simple document model. > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Attachments: foo.zip > > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1233) Teiid cannot handle child elements belonging to a different namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1233?page=com.atlassian.jira.plu... ] Steven Hawkins moved TEIID-1914 to TEIIDDES-1233: ------------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-1233 (was: TEIID-1914) Affects Version/s: 7.6 (was: 7.6) Component/s: Modeling (was: Server) > Teiid cannot handle child elements belonging to a different namespace > --------------------------------------------------------------------- > > Key: TEIIDDES-1233 > URL: https://issues.jboss.org/browse/TEIIDDES-1233 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.6 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > In the case where a web service is returning a response similar to the > following: > <ns1:searchMidbWSResponse ... > > < ns1:return> > < ns1:Site> > <ns2:PropOne>...</ ns2:PropOne> > < ns2:PropTwo>...</ ns2:PropTwo> > etc... > </ ns1:Site> > </ ns1:return> > </ ns1:searchMidbWSResponse> > Notice that all of the Site property elements belong to a different namespace > (alias=ns2) whereas the outer elements belong to the namespace with the ns1 > alias. It looks like EDS cannot handle child elements belonging to a different > namespace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1149: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a private comment on [bug 781108|https://bugzilla.redhat.com/show_bug.cgi?id=781108] > Managing multiple versions of models > ------------------------------------ > > Key: TEIIDDES-1149 > URL: https://issues.jboss.org/browse/TEIIDDES-1149 > Project: Teiid Designer > Issue Type: Feature Request > Components: Eclipse Integration, Modeling > Affects Versions: 7.1.1, 7.4.2 > Reporter: Tom Fonteyne > Assignee: Barry LaFond > > We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models. > We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB. > The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future. > Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2012