[JBoss JIRA] (TEIIDDES-2013) Preview with SalesForce data source does not work
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2013?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2013:
------------------------------------
Fix Version/s: 8.3.2
Assignee: Mark Drilling
> Preview with SalesForce data source does not work
> -------------------------------------------------
>
> Key: TEIIDDES-2013
> URL: https://issues.jboss.org/browse/TEIIDDES-2013
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Fix For: 8.3.2
>
>
> 1) start my external jboss running teiid 8.6 and my teiid instance within the designer
> 2) create a teiid model project
> 3) import a salesforce model
> 4) supply un, pw, and url
> 5) test connection...
> 6) select a table from the model, e.g., Account
> 6) select preview data
> See exception
> EIID70006 {"JBAS014671: Failed services" => {"jboss.ra.deployment.PREVIEW_7ca3b12a-7296-455f-a6a3-2ccc75fd3819_SFTest_SFTestModel_1" => "org.jboss.msc.service.StartException in service jboss.ra.deployment.PREVIEW_7ca3b12a-7296-455f-a6a3-2ccc75fd3819_SFTest_SFTestModel_1: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [PREVIEW_7ca3b12a-7296-455f-a6a3-2ccc75fd3819_SFTest_SFTestModel]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010446: Failed to start RA deployment [PREVIEW_7ca3b12a-7296-455f-a6a3-2ccc75fd3819_SFTest_SFTestModel]
> Caused by: org.jboss.jca.deployers.common.DeployException: IJ020060: Unable to inject: org.teiid.resource.adapter.salesforce.SalesForceManagedConnectionFactory property: url value: https://cs30.salesforce.com/services/Soap/u/29.0"}}
>
> The issue I see is the URL property "name" needs to be uppercase.
--
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
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1811:
-----------------------------------
Fix Version/s: 8.5
(was: 8.4)
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Minor
> Fix For: 8.5
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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
12 years, 2 months
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2018.
------------------------------------
Resolution: Done
Done
> 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
> Assignee: Barry LaFond
> Fix For: 8.4
>
> Attachments: all_type_jdbc_import_from_vdb.png, types_comparison.png
>
>
> 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
12 years, 2 months
[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 updated TEIIDDES-2017:
-----------------------------------
Issue Type: Bug (was: Feature Request)
Fix Version/s: 8.5
(was: 8.4)
Cannot actually test until 8.5 when we upgrade to 8.7 Teiid server when solr is supported as a translator.
> NPE while using Teiid Connection Importer
> -----------------------------------------
>
> Key: TEIIDDES-2017
> URL: https://issues.jboss.org/browse/TEIIDDES-2017
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.5
>
>
> 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
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1250) Need to improve the concept of how we're using and presenting the standard File and Web Service procedures
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1250?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1250:
-----------------------------------
Fix Version/s: Future
(was: 8.4)
> Need to improve the concept of how we're using and presenting the standard File and Web Service procedures
> ----------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1250
> URL: https://issues.jboss.org/browse/TEIIDDES-1250
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: Future
>
> Attachments: TEIIDDES-1250.txt
>
>
> As we're developing more and more importers and model generators that utilize or require a source model containing getText(), getTextFiles(), invoke() or invokeHTTP(), it seems that we're spending a lot of time:
> 1) Re-coding the logic to generate them to utilize the "Source" or connection profile stored in them
> 2) Explaining to the user that this is "Required" and how/why it's happening.
> The ONLY reason user-intervention is required is because currently, a Source model is needed as the carrier of the specific FILE or WSDL URL information. (Used to create "Data Source")
> If this File/WSDL URL info was NOT included in these source models, then we could create a Built-in FileFunctions.xmi Source model that's delivered with the product and included in a VDB ANY time it's required.
> To make this happen, we'd need another mechanism to persist the connection information and that might be the "View Model" that contains the SQL that contains the actual "File" or "URL" definition. This sort of makes sense.
> I know our current "Preview Data" and "Create Data Source" framework only works with Source models, but if we could change this behavior we would save a LOT of pain and anguish for the user AND us developers in the future.
> Currently this would simplify 3 different import wizards, remove a couple of Options in the "New > Teiid Metadata Model > Relational" wizard use case and remove a step or two from EACH cheat sheet or section in the documentation.
--
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
12 years, 2 months
[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 edited comment on TEIIDDES-1982 at 2/4/14 12:30 PM:
-----------------------------------------------------------------
Attached modified source files to commit to respective client plugins (remove version suffix first). These instantiate a new SPI *TeiidExecutionException* class which allows model info and reason code to perculate up to vdb actions and workers rather than straight *Exception*
was (Author: blafond):
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
12 years, 2 months
[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:
-----------------------------------
Assignee: Mark Drilling (was: Barry LaFond)
> 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: Mark Drilling
> 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
12 years, 2 months
[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... ]
Work on TEIIDDES-1982 started by Barry LaFond.
> 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
12 years, 2 months