April 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2108) Allow managing translator override properties on a source model

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2108: -------------------------------------- Summary: Allow managing translator override properties on a source model Key: TEIIDDES-2108 URL: https://issues.jboss.org/browse/TEIIDDES-2108 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview, Modeling, VDB & Execution Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.5 User requests ability to select a source model and edit/manage Translator Override properties as well as maybe set/inject these TOPs into the source model at import time. * new *Edit Translator Properties* action * new *Edit Translator Properties* dialog editor] * need framework/logic to pull TO definitions from Teiid server * need framework/logic to extract/inject these override properties into the source model XMI file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-305) Create an importer for the LDAP Connector

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-305?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-305: ---------------------------------- Fix Version/s: 8.3.3 (was: 8.3.2) > Create an importer for the LDAP Connector > ----------------------------------------- > > Key: TEIIDDES-305 > URL: https://issues.jboss.org/browse/TEIIDDES-305 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: Future > Reporter: Michael Walker > Assignee: Barry LaFond > Fix For: 8.3, 8.3.3 > > > Designer should be able to import LDAP metadata and auto-generate a relational model. This would remove the manual effort of creating models, which is error-prone. > The importer should support the ability to gather cost statistics, as it greatly enhances overall query performance, and is always recommended for use with LDAP data source connections. > The importer could also create normalized tables to represent multi-valued attributes of a given DN. See linked issue for more info on this request. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1195) Enable the coping of translator overrides for use in other VDB's with same translator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1195?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1195: ----------------------------------- Fix Version/s: 8.5 (was: Future) > Enable the coping of translator overrides for use in other VDB's with same translator > ------------------------------------------------------------------------------------- > > Key: TEIIDDES-1195 > URL: https://issues.jboss.org/browse/TEIIDDES-1195 > Project: Teiid Designer > Issue Type: Sub-task > Components: VDB & Execution > Affects Versions: 7.4.2 > Reporter: Van Halbert > Assignee: Dan Florian > Fix For: 8.5 > > > Building multiple vdb's in a single project and the same data sources, assigned the same translator, are used. It would be good to enable the extracting/copying of Translator property overrides for ease of setting up/updating VDB's that need the same overrides. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1251) Allow preview translators to have their properties changed

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1251?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1251: ----------------------------------- Fix Version/s: 8.5 (was: Komodo) > Allow preview translators to have their properties changed > ---------------------------------------------------------- > > Key: TEIIDDES-1251 > URL: https://issues.jboss.org/browse/TEIIDDES-1251 > Project: Teiid Designer > Issue Type: Enhancement > Components: Teiid Integration > Affects Versions: 7.6 > Reporter: Ramesh Reddy > Fix For: 8.5 > > > Previewing may not represent what the user wants or in some situations may not work, such as needed MESSAGE vs. PAYLOAD settings for the WS translator. The user should be able to tweak the preview to match their desired settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2005) Unable to set translator override properties when doing Teiid Connection Importing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2005?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2005: ----------------------------------- Fix Version/s: 8.5 (was: Future) > Unable to set translator override properties when doing Teiid Connection Importing > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-2005 > URL: https://issues.jboss.org/browse/TEIIDDES-2005 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.3.1 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.5 > > > When using the Teiid Connection import option, there is no option to set the translator override properties to control the behavior of the translator, similar to the VDB editor translator overrides. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2101) Query resolution fails on procedure that references XmlDocument

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2101?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-2101: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1085516 > Query resolution fails on procedure that references XmlDocument > --------------------------------------------------------------- > > Key: TEIIDDES-2101 > URL: https://issues.jboss.org/browse/TEIIDDES-2101 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.3.1, 8.5 > > > Procedure from customer case fails to validate, with no description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1945) Unable to deploy and test a VDB with same name models with different extensions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1945?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1945: ---------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1035019, https://bugzilla.redhat.com/show_bug.cgi?id=1085514 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1035019) > Unable to deploy and test a VDB with same name models with different extensions > ------------------------------------------------------------------------------- > > Key: TEIIDDES-1945 > URL: https://issues.jboss.org/browse/TEIIDDES-1945 > Project: Teiid Designer > Issue Type: Bug > Components: Validation, VDB & Execution > Affects Versions: 8.3 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.4, 8.5 > > Attachments: duplicate-file-names-problems-view.png, RecursiveXMLTest.tar.gz > > > Followed the E2eRecursiveXmlTextSourceTestScript_Teiid7.odt test and created various models. When it came to creating the VDB on step 5.23 the vdb creation failed with below exception. > There is no way to further proceed with the test without a VDB. I will also attach the MPS. > Employees.xmi and Emloyees.xmi are both entered as "Employee" in the VDB's model name element. SAX parser validation will fail since the element names are not unique. > {code} > java.lang.RuntimeException: javax.xml.bind.MarshalException > - with linked exception: > [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".] > at org.teiid.core.designer.CoreModelerPlugin.toRuntimeException(CoreModelerPlugin.java:76) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:50) > at org.teiid.designer.vdb.Vdb.save(Vdb.java:919) > at org.teiid.designer.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:1768) > at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:150) > at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:276) > at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) > at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:1818) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1815) > at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284) > at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:263) > at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:155) > at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3769) > at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3782) > at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:53) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > Caused by: javax.xml.bind.MarshalException > - with linked exception: > [org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb".] > at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317) > at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243) > at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75) > at org.teiid.designer.vdb.Vdb$4.tryToDo(Vdb.java:948) > at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40) > ... 60 more > Caused by: org.xml.sax.SAXParseException: Duplicate unique value [Employees] declared for identity constraint of element "vdb". > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) > at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) > at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:423) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3188) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$UniqueValueStore.checkDuplicateValues(XMLSchemaValidator.java:3823) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$ValueStoreBase.addValue(XMLSchemaValidator.java:3549) > at com.sun.org.apache.xerces.internal.impl.xs.identity.Field$Matcher.matched(Field.java:178) > at com.sun.org.apache.xerces.internal.impl.xs.identity.XPathMatcher.startElement(XPathMatcher.java:331) > at com.sun.org.apache.xerces.internal.impl.xs.identity.Selector$Matcher.startElement(Selector.java:225) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2083) > at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:711) > at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:551) > at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) > at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113) > at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91) > at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:274) > at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:663) > at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54) > at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157) > at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141) > at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:306) > at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:561) > at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:290) > at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:462) > at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:314) > ... 64 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2107) Virtual documents in XML view model build from XSD have incorrect namespaces

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2107?page=com.atlassian.jira.plu... ] Lucie Fabrikova updated TEIIDDES-2107: -------------------------------------- Attachment: UpdatesSchema.xsd > Virtual documents in XML view model build from XSD have incorrect namespaces > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2107 > URL: https://issues.jboss.org/browse/TEIIDDES-2107 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Reporter: Lucie Fabrikova > Attachments: UpdatesSchema.xsd, xmlviewNS.png > > > When creating new metadata model (XML, View model, Build XML documents from XML schema), namespaces are set correctly only for one of the virtual documents. If you choose multiple virtual documents from schema root elements table, the others would have namespace set to null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2107) Virtual documents in XML view model build from XSD have incorrect namespaces

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2107?page=com.atlassian.jira.plu... ] Lucie Fabrikova edited comment on TEIIDDES-2107 at 4/8/14 10:44 AM: -------------------------------------------------------------------- The problem arises there: org.teiid.designer.metamodels.xml.XmlDocumentBuilderImpl.java ... final String uri = (String)next.getValue(); [line 1715] if (!schemaUris.contains(uri)) { final XmlNamespace ns = docFactory.createXmlNamespace(); if ("this".equals(prefix) || prefix == null || prefix.trim().length() == 0) ns.setPrefix(XmlDocumentUtil.createXmlPrefixFromUri(uri)); //$NON-NLS-1$ else ns.setPrefix(prefix); ns.setUri(uri); ns.setElement(root); schemaUris.add(uri); this.uriToNamespaceMap.put(uri, ns); } was (Author: lfabriko): The problem arises there: org.teiid.designer.metamodels.xml.XmlDocumentBuilderImpl.java line 1715 if (!schemaUris.contains(uri)) { final XmlNamespace ns = docFactory.createXmlNamespace(); if ("this".equals(prefix) || prefix == null || prefix.trim().length() == 0) ns.setPrefix(XmlDocumentUtil.createXmlPrefixFromUri(uri)); //$NON-NLS-1$ else ns.setPrefix(prefix); ns.setUri(uri); ns.setElement(root); schemaUris.add(uri); this.uriToNamespaceMap.put(uri, ns); } > Virtual documents in XML view model build from XSD have incorrect namespaces > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2107 > URL: https://issues.jboss.org/browse/TEIIDDES-2107 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Reporter: Lucie Fabrikova > Attachments: UpdatesSchema.xsd, xmlviewNS.png > > > When creating new metadata model (XML, View model, Build XML documents from XML schema), namespaces are set correctly only for one of the virtual documents. If you choose multiple virtual documents from schema root elements table, the others would have namespace set to null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2107) Virtual documents in XML view model build from XSD have incorrect namespaces

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2107?page=com.atlassian.jira.plu... ] Lucie Fabrikova commented on TEIIDDES-2107: ------------------------------------------- Proposed fix: ... final String uri = (String)next.getValue(); final XmlNamespace ns = docFactory.createXmlNamespace(); if ("this".equals(prefix) || prefix == null || prefix.trim().length() == 0) ns.setPrefix(XmlDocumentUtil.createXmlPrefixFromUri(uri)); //$NON-NLS-1$ else ns.setPrefix(prefix); ns.setUri(uri); ns.setElement(root); if (!schemaUris.contains(uri)) { schemaUris.add(uri); this.uriToNamespaceMap.put(uri, ns); } > Virtual documents in XML view model build from XSD have incorrect namespaces > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2107 > URL: https://issues.jboss.org/browse/TEIIDDES-2107 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Reporter: Lucie Fabrikova > Attachments: xmlviewNS.png > > > When creating new metadata model (XML, View model, Build XML documents from XML schema), namespaces are set correctly only for one of the virtual documents. If you choose multiple virtual documents from schema root elements table, the others would have namespace set to null. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2014