[JBoss JIRA] (TEIIDDES-530) Include LDAP Modeling section in Designer User Guide
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-530?page=com.atlassian.jira.plug... ]
Mark Drilling updated TEIIDDES-530:
-----------------------------------
Summary: Include LDAP Modeling section in Designer User Guide (was: The LDAP documentation in MMx that relates to designer activity, needs to be included in the designer documentation)
Fix Version/s: 8.2.GA
We don't have an LDAP Importer, but maybe add a subsection in section 5 that includes some guidance about how to model LDAP sources.
> Include LDAP Modeling section in Designer User Guide
> ----------------------------------------------------
>
> Key: TEIIDDES-530
> URL: https://issues.jboss.org/browse/TEIIDDES-530
> Project: Teiid Designer
> Issue Type: Task
> Components: Documentation
> Affects Versions: 7.0
> Reporter: Van Halbert
> Fix For: 8.2.GA
>
>
> There is MMx LDAP documentation that relates to what has to be done in the designer in order to model a LDAP data source. This documentation needs to be brought over into designer 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, 8 months
[JBoss JIRA] (TEIIDDES-1399) REST Extensions properties collapses everytime you leave the edited field - Leave it alone, please
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1399?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1399.
-------------------------------------
Resolution: Duplicate Issue
closing, duplicate of TEIIDDES-1578
> REST Extensions properties collapses everytime you leave the edited field - Leave it alone, please
> --------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1399
> URL: https://issues.jboss.org/browse/TEIIDDES-1399
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.7.1
> Environment: JBDS 5.0 SOA-tooling Beta 2
> Reporter: Paul Nittel
> Priority: Minor
>
> When creating a RESTful WAR, two extended properties are added to the model containing the procedure. After editing the first, changing focus to the second causes the Extension property "group" to collapse. This forces the user to, once again, expand the group. Not much impact, but really annoying.
> Once expanded, it should remain expanded until explicitly collapsed by 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
12 years, 8 months
[JBoss JIRA] (TEIIDDES-1419) Improve UDF usage documentation
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1419?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1419:
------------------------------------
Summary: Improve UDF usage documentation (was: Docs - Need to clarify UDF usage in 7.7.2)
Fix Version/s: 8.2.GA
(was: 7.7.3)
Description:
The Designer UserGuide contains very little information about how to create a UDF, etc. Should probably add a section or refer to another document.
In the current user guide,
section 9.5 http://docs.jboss.org/teiid/designer/8.2/user-guide/en-US/html/managing-v...
shows FunctionModels and should be updated.
was:
It is confusing in 7.7.1 how the user should create UDFs.
The process is the same in 7.7.1, but you get a deprecation warning when you create a function model. There is still work to be done with the MEDs for UDF creation - I think that is planned for 8.0.
In the meantime we should make it clear in the docs, that the process is the same re UDFs until 8.0 - even though you get a deprecation warning saying not to use the FunctionModel.
> Improve UDF usage documentation
> -------------------------------
>
> Key: TEIIDDES-1419
> URL: https://issues.jboss.org/browse/TEIIDDES-1419
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Documentation
> Affects Versions: 7.7.1
> Reporter: Mark Drilling
> Fix For: 8.2.GA
>
>
> The Designer UserGuide contains very little information about how to create a UDF, etc. Should probably add a section or refer to another document.
> In the current user guide,
> section 9.5 http://docs.jboss.org/teiid/designer/8.2/user-guide/en-US/html/managing-v...
> shows FunctionModels and should be updated.
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1820) Nullpointer exception when opening Teiid importer
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1820?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-1820.
-------------------------------------
Assignee: Mark Drilling
Resolution: Cannot Reproduce Bug
I could not reproduce with Designer 8.2Beta1. Please retest and re-open if this is still a problem.
The Teiid Connection importer requires a running Teiid 8.3 or higher instance to launch.
> Nullpointer exception when opening Teiid importer
> -------------------------------------------------
>
> Key: TEIIDDES-1820
> URL: https://issues.jboss.org/browse/TEIIDDES-1820
> Project: Teiid Designer
> Issue Type: Bug
> Environment: Juno Service Release 1
> JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4)
> Teiid Designer 8.1.1
> Reporter: Filip Nguyen
> Assignee: Mark Drilling
>
> I have added a JBoss 7.1 server. After hitting "Teiid Connection >> Source Model" I get NullPointerException:
> {noformat}
> java.lang.NullPointerException
> at org.teiid.designer.teiidimporter.ui.wizard.SelectTranslatorAndTargetPage.createTargetModelGroup(SelectTranslatorAndTargetPage.java:276)
> at org.teiid.designer.teiidimporter.ui.wizard.SelectTranslatorAndTargetPage.createControl(SelectTranslatorAndTargetPage.java:114)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.createPageControls(AbstractWizard.java:153)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.createPageControls(AbstractWizard.java:138)
> at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.createPageControls(TeiidImportWizard.java:170)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1182)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1241)
> 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.ui.internal.dialogs.ImportExportPage.treeDoubleClicked(ImportExportPage.java:250)
> at org.eclipse.ui.internal.dialogs.ImportPage$2.doubleClick(ImportPage.java:72)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:845)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:843)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1477)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1246)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:246)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:307)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> 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:76)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:229)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:210)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:500)
> 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:1276)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
> {noformat}
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1826) Designer doesn't yet support Flat File Connection Profile URL input option
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1826?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1826:
------------------------------------
Fix Version/s: 8.2.GA
(was: 8.2)
> Designer doesn't yet support Flat File Connection Profile URL input option
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-1826
> URL: https://issues.jboss.org/browse/TEIIDDES-1826
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Datatools Integration
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.2.GA
>
>
> Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files.
> Teiid Designer's Flat File importer only expects the "folder" version.
> Need to work with a single file URI
> Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported.
> Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d...
> Note that Teiid's File data source is expecting a Folder location in it's properties. The Source model will contain a tag like: key="connection:FlatFileHomeUrl" value="/home/blafond/Testing/Test Data/FlatFileData/employee-data"/> and the file name will be injected into the generated SQL for the virtual table.
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1826) Designer doesn't yet support Flat File Connection Profile URL input option
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1826?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-1826:
-----------------------------------------
- The user is allowed to choose a single file in the Flat File Connection Profile, but we were not handling that case. Now setting the 'ParentDirectory' property successfully for this case.
- The user is also allowed to enter a remote file URI in the Flat File connection profile. More work is required in Designer for this scenario (need to utilize WebService RA instead of File RA, same as we do with XML).
- Added checks for the URI case to let user know the local dir was not found
Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/227
> Designer doesn't yet support Flat File Connection Profile URL input option
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-1826
> URL: https://issues.jboss.org/browse/TEIIDDES-1826
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Datatools Integration
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.2
>
>
> Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files.
> Teiid Designer's Flat File importer only expects the "folder" version.
> Need to work with a single file URI
> Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported.
> Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d...
> Note that Teiid's File data source is expecting a Folder location in it's properties. The Source model will contain a tag like: key="connection:FlatFileHomeUrl" value="/home/blafond/Testing/Test Data/FlatFileData/employee-data"/> and the file name will be injected into the generated SQL for the virtual table.
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1829) Add Dynamic Parameter Capability to REST Importer
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-1829:
-----------------------------------
Summary: Add Dynamic Parameter Capability to REST Importer
Key: TEIIDDES-1829
URL: https://issues.jboss.org/browse/TEIIDDES-1829
Project: Teiid Designer
Issue Type: Feature Request
Components: Web Services Support
Affects Versions: 8.2
Reporter: Ted Jones
Assignee: Ted Jones
Fix For: 8.2.GA
Currently the REST importer just takes a URL with parameters included. Need to add an option for dynamic parameters. This will mean generating a procedure instead of a table and building the URL dynamically using the passed in values.
--
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, 8 months
[JBoss JIRA] (TEIIDDES-1826) Designer doesn't yet support Flat File Connection Profile URL input option
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1826?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1826:
-----------------------------------
Description:
Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files.
Teiid Designer's Flat File importer only expects the "folder" version.
Need to work with a single file URI
Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported.
Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d...
Note that Teiid's File data source is expecting a Folder location in it's properties. The Source model will contain a tag like: key="connection:FlatFileHomeUrl" value="/home/blafond/Testing/Test Data/FlatFileData/employee-data"/> and the file name will be injected into the generated SQL for the virtual table.
was:
Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files.
Teiid Designer's Flat File importer only expects the "folder" version.
Need to work with a single file URI
Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported.
Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d...
> Designer doesn't yet support Flat File Connection Profile URL input option
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-1826
> URL: https://issues.jboss.org/browse/TEIIDDES-1826
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Datatools Integration
> Affects Versions: 8.2
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Priority: Critical
> Fix For: 8.2
>
>
> Flat File connection profile wizard includes a "Enter File URI:" input field. The intention is to select a specific data file (.txt, .csv, etc.) instead of a data "folder" containing one or more of these files.
> Teiid Designer's Flat File importer only expects the "folder" version.
> Need to work with a single file URI
> Don't know if remote URI or just a local file URI is implied. The "Browse..." button only searches local/remote file system connections. Not sure if HTTP is supported.
> Test with product data at: http://download.jboss.org/teiid/designer/data/products/file/productdata_d...
> Note that Teiid's File data source is expecting a Folder location in it's properties. The Source model will contain a tag like: key="connection:FlatFileHomeUrl" value="/home/blafond/Testing/Test Data/FlatFileData/employee-data"/> and the file name will be injected into the generated SQL for the virtual table.
--
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, 8 months