[JBoss JIRA] (TEIIDDES-2835) NullPointerException at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444) when "Create source model for JDBC Data Source" from the Guide UI
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2835?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2835:
-----------------------------------
Issue Type: Bug (was: Feature Request)
> NullPointerException at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444) when "Create source model for JDBC Data Source" from the Guide UI
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2835
> URL: https://issues.jboss.org/browse/TEIIDDES-2835
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs, Patch Release
> Affects Versions: 10.0
> Environment: Teiid Designed 10.0.0.Final.
> eclipse.buildId=4.5.2.M20160212-1500
> java.version=1.8.0_91
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -data file:/C:/Users/ggregory/workspaces/teiid-designer-mars/ -product org.eclipse.epp.package.jee.product
> Reporter: Gary Gregory
> Assignee: Barry LaFond
> Fix For: 10.0.1
>
> Attachments: npe.png, screenshot-1.png, teiid-mars-config.txt
>
>
> - Install stock plain Eclipse Mars (4.5.2)
> - Install Teiid Designer 10.0.0.Final per http://teiiddesigner.jboss.org/designer_summary/downloads
> - Following the guide http://docs.jboss.org/teiid/designer/10.0/user-guide/en-US/html/dive-righ...
> - Created MySQL 5.0 JDBC data source
> - Created Oracle 10g JDBC "thin" XE data source
> - On step 4 "Create source model for JDBC data source", launching the step from the guide causes an NPE:
> {{java.lang.NullPointerException
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionTab(JdbcImportOptionsPage.java:245)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createControl(JdbcImportOptionsPage.java:228)
> 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.jdbc.ui.wizards.JdbcImportWizard.createPageControls(JdbcImportWizard.java:250)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils$7.run(ModelerUiViewUtils.java:250)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils.launchWizard(ModelerUiViewUtils.java:240)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils$5.run(ModelerUiViewUtils.java:185)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils.launchWizard(ModelerUiViewUtils.java:167)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.launchWizard(AdvisorActionFactory.java:904)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:437)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.launchGuidesAction(TeiidGuidesSection.java:281)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.access$1(TeiidGuidesSection.java:271)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection$4.doubleClick(TeiidGuidesSection.java:174)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:832)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:829)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1470)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1263)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> 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)
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1197) Create Runtime Artifacts Configuration View or Editor
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1197?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1197.
------------------------------------
Fix Version/s: (was: Future)
Resolution: Won't Do
> Create Runtime Artifacts Configuration View or Editor
> -----------------------------------------------------
>
> Key: TEIIDDES-1197
> URL: https://issues.jboss.org/browse/TEIIDDES-1197
> Project: Teiid Designer
> Issue Type: Sub-task
> Affects Versions: 7.6
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Attachments: Initial Runtime Artifact Manager.bmml, Initial Runtime Artifact Manager.png
>
>
> Teiid Designer has a number of views, editors that allow management of various values, artifacts or properties of artifacts.
> This info includes:
> - Data Tools Project Connection Profiles
> - Teiid Data Sources and Translators
> - Translator Overrides (currently only in VDBs)
> - Re-usable Model Extension Definitions (MEDs)
> - VDB's
> Single view/editor containing the status of these items for a given workspace would help clarify what a user is working with and also better enable re-use across local projects
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1071) Improve usability for primary end-to-end use cases
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1071?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1071.
------------------------------------
Fix Version/s: (was: Future)
Resolution: Done
> Improve usability for primary end-to-end use cases
> --------------------------------------------------
>
> Key: TEIIDDES-1071
> URL: https://issues.jboss.org/browse/TEIIDDES-1071
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.5
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
>
> Basic modeling operations for Teiid Designer can confusing because of the wealth of options and lack of UI assistance.
> 1) Create Cheat Sheets for multi-step modeling processes
> 2) Create Advisor framework to assist user in monitoring progress through these steps
> 3) Create new customizable top-down view of workspace showing model dependencies and project/folder containment.
> - Allow drill-down editing ( EXAMPLE: Workspace > Project > Folder > Model > Table > Column )
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1111) Create a model(s) (view/source) based on the schema and type of data source provided
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1111?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1111.
------------------------------------
Fix Version/s: (was: Future)
Resolution: Won't Fix
WS and XML metamodels are now deprecated. won't fix
> Create a model(s) (view/source) based on the schema and type of data source provided
> ------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1111
> URL: https://issues.jboss.org/browse/TEIIDDES-1111
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Labels: importers, teiid, xml
>
> There have been many requests from users in the recent past to auto-generate source and view models that can consume the XML coming in the specified in a schema file. The current XML document model, take in a XSD and maps the relational data into XML data. This request is exact opposite of it in the consuming side. The data is coming in as XML, need to expose them as relational.
> I strongly believe that this needs to be done as part of TEIIDDES-1078, not create separate importers to minimize the user experience with modelling any XML data.
> The data sources can File, SOAP service or Rest service currently, but may not be restricted to those.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1402) Enable the diagram toolbar buttons, eg. Add Transformation Sources, by default
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1402?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1402.
------------------------------------
Fix Version/s: (was: Future)
Resolution: Won't Fix
> Enable the diagram toolbar buttons, eg. Add Transformation Sources, by default
> ------------------------------------------------------------------------------
>
> Key: TEIIDDES-1402
> URL: https://issues.jboss.org/browse/TEIIDDES-1402
> Project: Teiid Designer
> Issue Type: Sub-task
> Components: Diagrams
> Reporter: Paul Richardson
> Assignee: Paul Richardson
>
> At the moment, the toolbar diagram actions depend upon selection in the Model Explorer tree.
> Better to enable the buttons by default.
> If selection is made in Model Explorer tree then button uses that as before. If there is no selection then throw up wizard asking the user to select which models to add. So in the case of 'Add Transformation Source(s), all source and view model transformation diagrams nodes will be selectable.
> Just helps the user avoid being confused as to why the buttons are disabled. Also helps with the view being the starting point for the use case. Maybe, consider New... buttons that would allow new sources to be created, ie. user starting from top-down approach with the view and working back to their sources.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1216) New View Table Wizard
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1216?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1216.
------------------------------------
Resolution: Out of Date
New Komodo-based UI's will have join/union type wizard functionality
> New View Table Wizard
> ---------------------
>
> Key: TEIIDDES-1216
> URL: https://issues.jboss.org/browse/TEIIDDES-1216
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Transformations
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: Komodo
>
> Attachments: Create View Table Wizard.bmml, Create View Table Wizard.png, CreateViewTableWizard.png, View Easy Edit Mockup.bmml, View Easy Edit Mockup.bmml, View Easy Edit Mockup.png
>
>
> In our push to improve usability, a new "Create View Table" wizard could provide a new means to create views using the Join or Union concept.
> Result of the wizard would be a complete, valid SQL transformation that is reconciled, use "functions" in Symbol definition and include Criteria
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1149) Managing multiple versions of models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1149?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1149.
------------------------------------
Resolution: Out of Date
Will be handled as part of the Komodo design
> Managing multiple versions of models
> ------------------------------------
>
> Key: TEIIDDES-1149
> URL: https://issues.jboss.org/browse/TEIIDDES-1149
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Eclipse Integration, Modeling
> Affects Versions: 7.1.1, 7.4.2
> Reporter: Tom Fonteyne
> Fix For: Komodo
>
>
> We have a big requirement to more effectively manage multiple versions of models. In the future, we will have to maintain multiple versions of models and VDBs in order to guarantee compability for some clients while possibly providing new functionality for other clients using the same models.
> We will also have "core models" (again possibly multiple releases) of business concepts which will be included in VDBs for specific clients and systems, then changes will need to be merged in from this one core set to many models/VDBs in the future. I posted a question to the SME list about this a few months ago ("Effectively version controlling models"). Ramesh provided some helpful ideas, such as stacking of VDBs, which we would prefer not to do because of foreseen management and performance (query planning) problems, and also how we can deploy multiple versions of the same VDB.
> The problem remains however, that the only way we have at present to work with models is interactively through Teiid designer, and the only way to merge selectively (rather than replacing models) is manually. This process would potentially have to be repeated multiple times for each changeset. The customer is concerned that this approach will become unmanageable in the future.
> Being able to merge through the designer would be great, but also non-interactively and automatable in some way too. Ideally, we would like to see a greater seperation of model management from the designer (in the same that it was done in a set of reusable classes which the designer makes use of also) so we have the option of using automatable tools (ie. maven) or building or own tools to do this merging.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months
[JBoss JIRA] (TEIIDDES-1119) Need for global workspace location
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1119?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1119.
------------------------------------
Resolution: Won't Do
> Need for global workspace location
> ----------------------------------
>
> Key: TEIIDDES-1119
> URL: https://issues.jboss.org/browse/TEIIDDES-1119
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Eclipse Integration
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: Komodo
>
>
> With 7.6 Teiid Designer will be managing a new Model Extension framework which allows users to define Model Extension Definitions (MEDs) to inject additional properties into relational, web services, XML document and function models.
> Initial design is to maintain a registry or both built-in and user-defined MED's within the user's workspace/.metadata/org.teiid.designer.extension folder.
> Designer is also maintaining a similar Teiid Server registry in workspace/.metadata/org.teiid.designer.dqp
> The "Import VDB" feature will probably need a place to store a registry of "Translator Overrides" so user can re-use these across VDB's rather than re-inputing these properties manually each time in their VDB editors.
> The Data Tools Connection profile registry is also stored in a workspace/.metadata/org.eclipse.datatools.connectivity folder. Data Tool provides input/export features for persisting portions or all of the profile registry across workspace, but requires user to import/export each time.
> Eclipse's ".metadata" folder concept is good from a single workspace standpoint, but these registries are:
> 1) at risk of being deleted if workspace is cleared
> 2) registry data (i.e. files) are not available/exposed for proper version control
> So a solution might be to create the concept of a Global Workspace Location. This location would be set by the user if they choose. This location would contain folders for Teiid Server, Model Extension, Translator Overrides, Connection Profiles such that if a user changes workspaces they wouldn't necessarily have to re-import all of this data.
> Maybe provide a "Global Workspace Explorer" view that would have some features/actions to do some appropriate management of the artifacts.
> This would be a Usability
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 9 months