May 2014 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1037: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1093210 > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2138) Restrict "New VDB" wizard's "Add model" to the current project

by Marc Shirley (JIRA)

Marc Shirley created TEIIDDES-2138: -------------------------------------- Summary: Restrict "New VDB" wizard's "Add model" to the current project Key: TEIIDDES-2138 URL: https://issues.jboss.org/browse/TEIIDDES-2138 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 8.3.1 Reporter: Marc Shirley New VDB wizard behavior should be the same as the edit VDB behavior and restrict model selection to only the current project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2107?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2107: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1086107|https://bugzilla.redhat.com/show_bug.cgi?id=1086107] from NEW to MODIFIED > 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 > Assignee: Lucie Fabrikova > Fix For: 8.5 > > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2107?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2107: ---------------------------------- Fix Version/s: 8.5 > 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 > Assignee: Lucie Fabrikova > Fix For: 8.5 > > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1937) Create Relational View Procedure action missing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1937?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1937: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035468|https://bugzilla.redhat.com/show_bug.cgi?id=1035468] from NEW to MODIFIED > Create Relational View Procedure action missing > ----------------------------------------------- > > Key: TEIIDDES-1937 > URL: https://issues.jboss.org/browse/TEIIDDES-1937 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 8.3 > Reporter: Paul Richardson > Assignee: Barry LaFond > Fix For: 8.5 > > Attachments: E2eRESTEasyWarTestScript.odt > > > The test script 'E2eRESTEasyWarTestScript' requires creation of a virtual procedure using the 'Define relational view procedure' action, which does not exist in the Guides View. Has this action been removed from the Guides View or is the test script incorrect? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

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 commented on TEIIDDES-1945: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035019|https://bugzilla.redhat.com/show_bug.cgi?id=1035019] from NEW to MODIFIED > 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 was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2060) Cannot select encoding when file model execute preview data

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2060?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2060: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1066760|https://bugzilla.redhat.com/show_bug.cgi?id=1066760] from NEW to MODIFIED > Cannot select encoding when file model execute preview data > ----------------------------------------------------------- > > Key: TEIIDDES-2060 > URL: https://issues.jboss.org/browse/TEIIDDES-2060 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.5 > > > Teiid designer can select file encoding when create file model using import function. However, it does not effect preview data function and actual VDB. > Actual VDB can set encoding by overriding file translator property. However, VDB for preview data function is created by automatically in teiid designer, so we cannot set encoding. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2022) UDF Jar Path deleted from Create User Defined Function dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2022?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2022: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1056968|https://bugzilla.redhat.com/show_bug.cgi?id=1056968] from NEW to MODIFIED > UDF Jar Path deleted from Create User Defined Function dialog > ------------------------------------------------------------- > > Key: TEIIDDES-2022 > URL: https://issues.jboss.org/browse/TEIIDDES-2022 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Environment: JBDISIS 7.0.0.CR2, JBDS 7.1.0.GA, Fedora 19, Java oracle jdk 1.7.0_45 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.4 > > > In a Create User Defined Function dialog, the text (pointing to previously selected UDF jar) in field UDF Jar Path disappears after clicking the "..." and canceling then the dialog "Select UDF jar". -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2023) DDL import wizard shows Model name in field DDL file

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2023?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2023: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1056971|https://bugzilla.redhat.com/show_bug.cgi?id=1056971] from NEW to MODIFIED > DDL import wizard shows Model name in field DDL file > ---------------------------------------------------- > > Key: TEIIDDES-2023 > URL: https://issues.jboss.org/browse/TEIIDDES-2023 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Environment: JBDISIS 7.0.0.CR2, JBDS 7.1.0.GA, Fedora 19, Java oracle jdk 1.7.0_45 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Fix For: 8.4 > > > Launch the wizard: Import DDL File >> Source or View Model > > In the dialog Provide DDL source: > 1. For "Model name" text field, click on "Choose..." button > 2. Choose some model, click OK > 3. The text appears in the field "DDL file" -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2024) Designer should not add connection-jndi-name attribute in VDB.xml when no jndi is being referenced

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2024?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2024: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1056974|https://bugzilla.redhat.com/show_bug.cgi?id=1056974] from NEW to MODIFIED > Designer should not add connection-jndi-name attribute in VDB.xml when no jndi is being referenced > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2024 > URL: https://issues.jboss.org/browse/TEIIDDES-2024 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Environment: JBDISIS 7.0.0.CR2, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19, Java oracle jdk 1.7.0_45 > Reporter: Lucie Fabrikova > Assignee: Barry LaFond > Fix For: 8.4 > > Attachments: MarketData.zip, yahoo.zip, YahooStocksXML.xml > > > If I try to execute a VDB with metadata model created from teiid designer file, with translator set to "yahoo" and JNDI set to "java:jboss/datasources/ExampleDS", I get following error: > TEIID30504 MarketData: org.jboss.jca.adapters.jdbc.WrapperDataSource is was not a ConnectionFactory implementation -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2014