July 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2888) Default value is not correctly parsed

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-2888: -------------------------------------- Summary: Default value is not correctly parsed Key: TEIIDDES-2888 URL: https://issues.jboss.org/browse/TEIIDDES-2888 Project: Teiid Designer Issue Type: Bug Components: Data Preview, Dynamic VDBs Affects Versions: 10.0.1 Environment: Fedora 24 Reporter: Matej Kralik Attachments: ProductProject.zip, screenshot1.png, screenshot2.png When I want preview data from my table (productdata in the project which is in the attachment), server shows me this error: TEIID31100 Parsing error: Encountered ") DEFAULT '('[*]Stock[*]')' OPTIONS" In one column I have default value ('Stock') (screenshot1) I am not sure whether it is the correct form of default value or not but in the old version of teiid designer preview this table works fine. I think that ddl parser is not able to parse this. (screenshot2) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2886) JDBC Stored Procedure Import adds ; 1 to name

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2886?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2886: ----------------------------------- Affects Version/s: 10.0.1 > JDBC Stored Procedure Import adds ;1 to name > -------------------------------------------- > > Key: TEIIDDES-2886 > URL: https://issues.jboss.org/browse/TEIIDDES-2886 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3, 10.0.1 > Environment: All > Reporter: Steve Tran > Attachments: sp_bug.PNG > > > When using the JDBC Importer (SQL Server in this example), the stored procedure name in source gets appended with a ";1". If you don't specifically go back into the XMI file and remove it, calling the stored procedure will result in an error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2886) JDBC Stored Procedure Import adds ; 1 to name

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2886?page=com.atlassian.jira.plu... ] Matus Makovy commented on TEIIDDES-2886: ---------------------------------------- I can reproduce this also with TD 10.0.1 > JDBC Stored Procedure Import adds ;1 to name > -------------------------------------------- > > Key: TEIIDDES-2886 > URL: https://issues.jboss.org/browse/TEIIDDES-2886 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Environment: All > Reporter: Steve Tran > Attachments: sp_bug.PNG > > > When using the JDBC Importer (SQL Server in this example), the stored procedure name in source gets appended with a ";1". If you don't specifically go back into the XMI file and remove it, calling the stored procedure will result in an error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2887) Unable to edit the admin port on the Teiid Instance Tab

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-2887: ------------------------------------- Summary: Unable to edit the admin port on the Teiid Instance Tab Key: TEIIDDES-2887 URL: https://issues.jboss.org/browse/TEIIDDES-2887 Project: Teiid Designer Issue Type: Bug Components: Usability Affects Versions: 10.0.2 Reporter: Van Halbert Priority: Critical When the DV server is started with port offsets means that in Teiid Designer, the Teiid Instance tab, the admin port needs to be adjusted accordingly. However, its not editable and doesn't pull its info from the Overview tab when port offsets are configured. This issue arises in cases where the server is externally administered and you don't wan to have to install a local EAP instance in order to manage it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2886) JDBC Stored Procedure Import adds ; 1 to name

by Steve Tran (JIRA)

Steve Tran created TEIIDDES-2886: ------------------------------------ Summary: JDBC Stored Procedure Import adds ;1 to name Key: TEIIDDES-2886 URL: https://issues.jboss.org/browse/TEIIDDES-2886 Project: Teiid Designer Issue Type: Bug Affects Versions: 9.0.3 Environment: All Reporter: Steve Tran Attachments: sp_bug.PNG When using the JDBC Importer (SQL Server in this example), the stored procedure name in source gets appended with a ";1". If you don't specifically go back into the XMI file and remove it, calling the stored procedure will result in an error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2408: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.1 (was: ) > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Task > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0, 9.2.1 > > > Teiid added support for: > XMLTEXT - just a regular function > XMLEXISTS - a predicate with syntax similar to XMLQUERY > XMLCAST - similar to CAST > All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2408. ---------------------------------- This is included in TD 10.0.1 > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Task > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0, 9.2.1 > > > Teiid added support for: > XMLTEXT - just a regular function > XMLEXISTS - a predicate with syntax similar to XMLQUERY > XMLCAST - similar to CAST > All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2885) Non workspace project doesnt generate web service from XML document

by Mario Majernik (JIRA)

Mario Majernik created TEIIDDES-2885: ---------------------------------------- Summary: Non workspace project doesnt generate web service from XML document Key: TEIIDDES-2885 URL: https://issues.jboss.org/browse/TEIIDDES-2885 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 10.0.1 Environment: Fedora 23 Reporter: Mario Majernik Attachments: ProductsProjectXML.zip, Screenshot1.png, Screenshot2.png When I create web service from XML document designer shows me this error: "TransformationHelper.getTransformationMappingRoot:null or invalid target." This happens only when I have not project in workspace and only when I want generate web service from XML document. This is stacktrace: java.lang.IllegalArgumentException: TransformationHelper.getTransformationMappingRoot:null or invalid target. at org.teiid.designer.transformation.util.TransformationHelper.getMappingRoot(TransformationHelper.java:2546) at org.teiid.designer.transformation.util.TransformationHelper.getMappingRoot(TransformationHelper.java:2592) at org.teiid.designer.webservice.util.WebServiceBuilderHelper$TransformationFinisher.finish(WebServiceBuilderHelper.java:1249) at org.teiid.designer.webservice.util.WebServiceBuilderHelper.createWebService(WebServiceBuilderHelper.java:674) at org.teiid.designer.webservice.ui.wizard.GenerateWebServiceModelWizard.doFinish(GenerateWebServiceModelWizard.java:130) at org.teiid.designer.webservice.ui.wizard.GenerateWebServiceModelWizard$1.run(GenerateWebServiceModelWizard.java:92) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:500) at org.teiid.designer.webservice.ui.wizard.GenerateWebServiceModelWizard.finish(GenerateWebServiceModelWizard.java:101) at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) at org.eclipse.jface.window.Window.open(Window.java:803) at org.teiid.designer.webservice.ui.actions.GenerateWebServiceModelAction2.run(GenerateWebServiceModelAction2.java:206) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2712) Support GET & POST methods together on REST procedures

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2712?page=com.atlassian.jira.plu... ] Matus Makovy updated TEIIDDES-2712: ----------------------------------- Labels: release_notes verified_jbdsis-9.0.1 (was: ) > Support GET & POST methods together on REST procedures > ------------------------------------------------------ > > Key: TEIIDDES-2712 > URL: https://issues.jboss.org/browse/TEIIDDES-2712 > Project: Teiid Designer > Issue Type: Feature Request > Components: Patch Release, Web Services Support > Reporter: Matus Makovy > Assignee: Ted Jones > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0.1 > > > Copied from BZ: > Description of request: > We can choose only one HTTP Request type for REST virtual procedures. Is it possible to combine GET & POST as one type ? > Rationale: > POST requests are more easy to create for client programmers.On the other hand GET method simplifies testing. Since it's easy to handle both request types on the server side, supporting both method at the same time may help to improve usability of services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2712) Support GET & POST methods together on REST procedures

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2712?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2712. ---------------------------------- This is included in TD 10.0.1 and covered by testing > Support GET & POST methods together on REST procedures > ------------------------------------------------------ > > Key: TEIIDDES-2712 > URL: https://issues.jboss.org/browse/TEIIDDES-2712 > Project: Teiid Designer > Issue Type: Feature Request > Components: Patch Release, Web Services Support > Reporter: Matus Makovy > Assignee: Ted Jones > Labels: release_notes, verified_jbdsis-9.0.1 > Fix For: 10.0.1 > > > Copied from BZ: > Description of request: > We can choose only one HTTP Request type for REST virtual procedures. Is it possible to combine GET & POST as one type ? > Rationale: > POST requests are more easy to create for client programmers.On the other hand GET method simplifies testing. Since it's easy to handle both request types on the server side, supporting both method at the same time may help to improve usability of services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2016