January 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1958) Hang generating war

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1958?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1958: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035478|https://bugzilla.redhat.com/show_bug.cgi?id=1035478] from MODIFIED to ON_QA > Hang generating war > ------------------- > > Key: TEIIDDES-1958 > URL: https://issues.jboss.org/browse/TEIIDDES-1958 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.3 > Environment: Fedora 17, KDE, runing the DV ER4 tooling/server > Reporter: Steven Hawkins > Assignee: Ted Jones > Fix For: 8.3 > > Attachments: error.png, threaddump.txt > > > Working through the web test script to the point where generating a war was called for. Eclipse shows a processing dialog, but goes all grey and unresponsive. See the attached thread dump. > Not this is in the same workspace as TEIIDDES-1957 so something else could be lingering. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1989) Unable to deploy VDB because use Source Name didn't match datasource Pool Name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1989?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1989: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1042914|https://bugzilla.redhat.com/show_bug.cgi?id=1042914] from MODIFIED to ON_QA > Unable to deploy VDB because use Source Name didn't match datasource Pool Name > ------------------------------------------------------------------------------ > > Key: TEIIDDES-1989 > URL: https://issues.jboss.org/browse/TEIIDDES-1989 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.3.1 > > > Created a VDB and used the defaults for the Source Name for the model when creating the bindings. However, unable to deploy the VDB until the Source Name was changed to match the Pool Name for the JNDI data source that is being used. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1986) When pasting text into StyledText widget fields it always is pasted twice

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1986?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1986: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1042910|https://bugzilla.redhat.com/show_bug.cgi?id=1042910] from MODIFIED to ON_QA > When pasting text into StyledText widget fields it always is pasted twice > ------------------------------------------------------------------------- > > Key: TEIIDDES-1986 > URL: https://issues.jboss.org/browse/TEIIDDES-1986 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 8.3.1 > > > On the new role conditions functionality if you paste a value into the text box it is always pasted twice. > Same issue with the column masking text box, VDB Editor Description text box, etc... -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2008) When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2008?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2008: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1046501|https://bugzilla.redhat.com/show_bug.cgi?id=1046501] from MODIFIED to ON_QA > When using Teiid Connection importer, add jdbc warnings and disable ability to import using ModeShape > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2008 > URL: https://issues.jboss.org/browse/TEIIDDES-2008 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.4 > Reporter: Van Halbert > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.3.1 > > > - For the new Teiid Connection importer, add a warning if the user is trying > to use it for specific JDBC translator types. In this warning, make the > recommendation that they should use our standard JBDC importer. However, if > they wish to proceed to use this importer, that they should reference the > documentation as to the source model properties that can be used to control > the importing. > - As is being done for translator types MongoDB and LDAP, we will also exclude the ability to import using ModeShape. If ModeShape, then indicate they should use the ModeShape importer. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1992) Designer generates wrong view model transformations for some services

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1992?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1992: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1041220|https://bugzilla.redhat.com/show_bug.cgi?id=1041220] from MODIFIED to ON_QA > Designer generates wrong view model transformations for some services > --------------------------------------------------------------------- > > Key: TEIIDDES-1992 > URL: https://issues.jboss.org/browse/TEIIDDES-1992 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Ted Jones > Priority: Critical > Fix For: 8.3.1 > > > When generating web service view from WSDL, the designer incorrectly adds the namespace to the request. The request [1] declares the "tns" prefix but since the namespace is not added to the actual request it generates [2]. > User can workaround this by directly modifying the request [3]. > [1] > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT XMLELEMENT(NAME getPeopleByName, XMLNAMESPACES('http://www.jboss.org/jbossas/dv/PeopleJaxws' AS tns)) AS xml_out; > END > [2] Caused by: javax.xml.ws.ProtocolException: Remote javax.xml.ws.soap.SOAPFaultException: Unexpected wrapper element getPeopleByName found. Expected {http://www.jboss.org/jbossas/dv/PeopleJaxws}getPeopleByName. > [3] > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT XMLELEMENT(NAME getPeopleByName, XMLNAMESPACES(DEFAULT 'http://www.jboss.org/jbossas/dv/PeopleJaxws')) AS xml_out; > END -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1971) Connection Reset by Peer messages appearing in JBoss log

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1971?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1971: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1035002|https://bugzilla.redhat.com/show_bug.cgi?id=1035002] from MODIFIED to ON_QA > Connection Reset by Peer messages appearing in JBoss log > -------------------------------------------------------- > > Key: TEIIDDES-1971 > URL: https://issues.jboss.org/browse/TEIIDDES-1971 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Paul Richardson > Priority: Critical > Labels: jbds711, jbdsis701 > Fix For: 8.3.1 > > Attachments: retransmission-packet.png, server.log > > > Running Developer Studio 7.1.0.CR1 and using either the server auto-detection or manually defining a server -and using an incorrect management password- results in a console log entry: > 14:00:54,966 ERROR [org.jboss.remoting.remote.connection] (Remoting "..." read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer > On server startup without any indication of what it means. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2011) Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2011?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-2011: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1047930|https://bugzilla.redhat.com/show_bug.cgi?id=1047930] from ASSIGNED to ON_QA > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2011 > URL: https://issues.jboss.org/browse/TEIIDDES-2011 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.3.1 > > Attachments: modeshape-client-3.3.6.GA-redhat-3.jar, modeshape-roles.properties, modeshape-users.properties, module.xml > > > Designer connectivity feature needs include org.apache.commons.logging for Modeshape connection profile. > Results in java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory trying to connect to MS repo via JDBC. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2017: ---------------------------------------- No I did not see any thing reported in log there > NPE while using Teiid Connection Importer > ----------------------------------------- > > Key: TEIIDDES-2017 > URL: https://issues.jboss.org/browse/TEIIDDES-2017 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3 > Reporter: Ramesh Reddy > > While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered > {code} > java.lang.NullPointerException > at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > 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.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.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279) > 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.GeneratedMethodAccessor49.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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$5.handleEvent(ActionContributionItem.java:411) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > {code} > The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2017: ---------------------------------------- Could you check your server log and attach if there's something logged there too? > NPE while using Teiid Connection Importer > ----------------------------------------- > > Key: TEIIDDES-2017 > URL: https://issues.jboss.org/browse/TEIIDDES-2017 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3 > Reporter: Ramesh Reddy > > While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered > {code} > java.lang.NullPointerException > at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201) > at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259) > at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238) > at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) > 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.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.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279) > 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.GeneratedMethodAccessor49.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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$5.handleEvent(ActionContributionItem.java:411) > 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:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > {code} > The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-2018: -------------------------------------- Summary: DDL importer creates wrong data type for "integer" Key: TEIIDDES-2018 URL: https://issues.jboss.org/browse/TEIIDDES-2018 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 8.3 Reporter: Ramesh Reddy When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model", * if the DDL supplied is "Teiid" dialect * if the data type supplied is "integer" Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time. This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long" -- 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, 5 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 2014