February 2014 - teiid-designer-issues

[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: --------------------------------------------------- Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1047930|https://bugzilla.redhat.com/show_bug.cgi?id=1047930] from ON_QA to VERIFIED > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1982?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1982: ---------------------------------------- Initial commit to master branch: https://github.com/Teiid-Designer/teiid-designer/commit/27f5a7bb80d403222... > Improve Error Dialog message for VDB deployment where source doesnt exist > ------------------------------------------------------------------------- > > Key: TEIIDDES-1982 > URL: https://issues.jboss.org/browse/TEIIDDES-1982 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.4 > > Attachments: ErrorDialog.png, ExecutionAdmin_77.java, ExecutionAdmin_83.java, ExecutionAdmin_84.java, MongoProjectSet.zip > > > In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source. > I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available. > Attaching model project set to reproduce, and a screen shot of the dialog. > Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1982) Improve Error Dialog message for VDB deployment where source doesnt exist

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1982?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1982: ----------------------------------- Attachment: ExecutionAdmin_77.java ExecutionAdmin_83.java ExecutionAdmin_84.java Modified source files to commit to respective client plugins (remove version suffix first) > Improve Error Dialog message for VDB deployment where source doesnt exist > ------------------------------------------------------------------------- > > Key: TEIIDDES-1982 > URL: https://issues.jboss.org/browse/TEIIDDES-1982 > Project: Teiid Designer > Issue Type: Enhancement > Components: VDB & Execution > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.4 > > Attachments: ErrorDialog.png, ExecutionAdmin_77.java, ExecutionAdmin_83.java, ExecutionAdmin_84.java, MongoProjectSet.zip > > > In some cases, when a user tries to deploy a VDB where one of the SourceModel DS does not exist, the user is prompted whether to create the source. > I encountered a case though where an Error Dialog was displayed instead, with the message "No Connection Information in model xxx.xmi". For this case(Mongo) there is no CP available. > Attaching model project set to reproduce, and a screen shot of the dialog. > Message could be more informative, e.g. "The Data Source for model xxx.xmi cannot be found on server, and no CP information is available" or similar. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1778) Change the Teiid Server version in the preferences to 8.4

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1778?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1778: --------------------------------------------------- Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 982648|https://bugzilla.redhat.com/show_bug.cgi?id=982648] from ON_QA to VERIFIED > Change the Teiid Server version in the preferences to 8.4 > --------------------------------------------------------- > > Key: TEIIDDES-1778 > URL: https://issues.jboss.org/browse/TEIIDDES-1778 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Paul Richardson > Attachments: teiid-default-server-version.png > > > The Teiid Designer preference for Teiid Server version is defaulting to 8.3, this should be 8.4 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1777) Unable to connect to a remote domain server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1777?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1777: --------------------------------------------------- Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 982648|https://bugzilla.redhat.com/show_bug.cgi?id=982648] from ON_QA to VERIFIED > Unable to connect to a remote domain server > ------------------------------------------- > > Key: TEIIDDES-1777 > URL: https://issues.jboss.org/browse/TEIIDDES-1777 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 8.2 > Reporter: Van Halbert > Priority: Critical > > Unable to connect to a remote domain server. Getting the following exception: > !ENTRY org.teiid.designer.dqp 4 0 2013-07-08 16:58:31.613 > !MESSAGE TEIID70036 java.lang.IllegalArgumentException > !STACK 0 > org.teiid.adminapi.AdminProcessingException: TEIID70036 java.lang.IllegalArgumentException > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1433) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1) > at org.teiid83.runtime.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:659) > at org.teiid83.runtime.ExecutionAdmin.init(ExecutionAdmin.java:576) > at org.teiid83.runtime.ExecutionAdmin.<init>(ExecutionAdmin.java:137) > at org.teiid83.runtime.ExecutionAdminFactory.createExecutionAdmin(ExecutionAdminFactory.java:29) > at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getExecutionAdmin(TeiidRuntimeRegistry.java:102) > at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:212) > at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:232) > at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:58) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159) > at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116) > at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:54) > at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) > 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.Display.sendEvent(Display.java:4166) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4012) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3651) > 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) > Caused by: java.lang.IllegalArgumentException > at org.jboss.dmr.ModelValue.getKeys(ModelValue.java:124) > at org.jboss.dmr.ModelNode.keys(ModelNode.java:1194) > at org.teiid.adminapi.AdminFactory$AdminImpl.getDomainAwareList(AdminFactory.java:1349) > at org.teiid.adminapi.AdminFactory$AdminImpl.getVDBs(AdminFactory.java:1430) > ... 51 more -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1863) Add native type to procedure parameters

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1863?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1863: ---------------------------------------- New entry for relationl.mxd extensions file {code:xml|title=relationl.mxd (fragment)|borderStyle=solid} <p:extendedMetaclass name="org.teiid.designer.metamodels.relational.impl.ProcedureParameterImpl"> <p:property advanced="false" index="true" masked="false" name="native-type" required="false" type="string"> <p:display locale="en">Native Type</p:display> </p:property> </p:extendedMetaclass> {code} > Add native type to procedure parameters > --------------------------------------- > > Key: TEIIDDES-1863 > URL: https://issues.jboss.org/browse/TEIIDDES-1863 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.4 > > > TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2036) Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2036?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2036: ---------------------------------------- Fix is to add the following to each of the 3 teiid clients build.properties files so the build includes them at the location in the plugin defined in the plugin.xml (above) rather than change the plugin.xml: org.teiid.7.7.x: *designer/org/teiid772/internal/teiid/database/teiidDB.xmi* org.teiid.7.7.x: *designer/org/teiid83/internal/teiid/database/teiidDB.xmi* org.teiid.8.4.x: *designer/org/teiid84/internal/teiid/database/teiidDB.xmi* > Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-2036 > URL: https://issues.jboss.org/browse/TEIIDDES-2036 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3.1 > Environment: JBDS 7.x + TDesigner 8.3 and 8.2 > Reporter: Hisanobu Okuda > Assignee: Barry LaFond > Fix For: 8.4 > > > When you create a new connection profile in JBDS Data Source Manager using teiid 8.2/8.3 driver and access teiid server via Data Source Manager, a dialog appears and mentions:- > 'Loading Core Provider' has encountered a problem. > An internal error occurred during: "Loading Core provider". -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2036) Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2036?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2036: ----------------------------------- Fix Version/s: 8.3.2 > Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-2036 > URL: https://issues.jboss.org/browse/TEIIDDES-2036 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3.1 > Environment: JBDS 7.x + TDesigner 8.3 and 8.2 > Reporter: Hisanobu Okuda > Assignee: Mark Drilling > Fix For: 8.4, 8.3.2 > > > When you create a new connection profile in JBDS Data Source Manager using teiid 8.2/8.3 driver and access teiid server via Data Source Manager, a dialog appears and mentions:- > 'Loading Core Provider' has encountered a problem. > An internal error occurred during: "Loading Core provider". -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2036) Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2036?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2036: ----------------------------------- Assignee: Mark Drilling (was: Barry LaFond) > Internal Error of Teiid Server JDBC Driver when accessing via Data Source Expolorer > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-2036 > URL: https://issues.jboss.org/browse/TEIIDDES-2036 > Project: Teiid Designer > Issue Type: Bug > Components: Datatools Integration > Affects Versions: 8.3.1 > Environment: JBDS 7.x + TDesigner 8.3 and 8.2 > Reporter: Hisanobu Okuda > Assignee: Mark Drilling > Fix For: 8.4 > > > When you create a new connection profile in JBDS Data Source Manager using teiid 8.2/8.3 driver and access teiid server via Data Source Manager, a dialog appears and mentions:- > 'Loading Core Provider' has encountered a problem. > An internal error occurred during: "Loading Core provider". -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-690) Refactor > Move source model produces preview errors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-690?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on TEIIDDES-690: -------------------------------------------------- Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 780131|https://bugzilla.redhat.com/show_bug.cgi?id=780131] from ON_QA to VERIFIED > Refactor > Move source model produces preview errors > ---------------------------------------------------- > > Key: TEIIDDES-690 > URL: https://issues.jboss.org/browse/TEIIDDES-690 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.1.1 > Environment: Windows, JBDS 4.0 Beta 1 > Reporter: Paul Nittel > Assignee: Dan Florian > Fix For: 7.7.1, 7.8 > > Attachments: org.teiid.designer.dqp.patch, org.teiid.designer.vdb.patch, RefactoringBoofsVdb.log, RefactorMove_HosePreview.jpg > > > When I refactor > move a source model I get an error proclaiming problems creating the preview VDB. See the attached screenshot to see the dialog box presented to the user. -- 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, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2014