[JBoss JIRA] (TEIIDDES-2842) NPE when trying to edit Data Role created during importing of dynamic VDB
by Matus Makovy (JIRA)
Matus Makovy created TEIIDDES-2842:
--------------------------------------
Summary: NPE when trying to edit Data Role created during importing of dynamic VDB
Key: TEIIDDES-2842
URL: https://issues.jboss.org/browse/TEIIDDES-2842
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 10.0
Environment: MAC
Reporter: Matus Makovy
Priority: Blocker
Attachments: importexport-vdb(1).xml
I got a NPE after importing attached VDB and trying to edit one existing data role.
Stack trace:
{code:java}
java.lang.NullPointerException
at org.teiid.designer.roles.ui.wizard.DataRoleWizard.<init>(DataRoleWizard.java:164)
at org.teiid.designer.vdb.ui.editor.panels.DataRolesPanel$1.selected(DataRolesPanel.java:175)
at org.teiid.designer.vdb.ui.editor.panels.DataRolesPanel$2.doubleClicked(DataRolesPanel.java:218)
at org.teiid.designer.vdb.ui.editor.panels.DataRolesPanel$2.doubleClicked(DataRolesPanel.java:1)
at org.teiid.designer.ui.common.table.TableAndToolBar$1.doubleClick(TableAndToolBar.java:79)
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.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1150)
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:4230)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
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(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
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)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2810) Import/Export Dynamic VDB utility doesn't transfer model descriptions
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2810?page=com.atlassian.jira.plu... ]
Matus Makovy edited comment on TEIIDDES-2810 at 5/16/16 11:29 AM:
------------------------------------------------------------------
After import descriptions of models are transferred, but description of VDB is not.
was (Author: mmakovy):
After import descriptions of models are transferred, however description of VDB is not.
> Import/Export Dynamic VDB utility doesn't transfer model descriptions
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2810
> URL: https://issues.jboss.org/browse/TEIIDDES-2810
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0, 9.0.7
>
> Attachments: DynamicVdb.patch
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the descriptions are not taken into account properly. We expect to see the description in the Teiid designer.
> Same goes when we export a Teiid vdb to a vdb xml: the descriptions are not generated as xml elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2810) Import/Export Dynamic VDB utility doesn't transfer model descriptions
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2810?page=com.atlassian.jira.plu... ]
Matus Makovy reopened TEIIDDES-2810:
------------------------------------
After import descriptions of models are transferred, however description of VDB is not.
> Import/Export Dynamic VDB utility doesn't transfer model descriptions
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2810
> URL: https://issues.jboss.org/browse/TEIIDDES-2810
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0, 9.0.7
>
> Attachments: DynamicVdb.patch
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the descriptions are not taken into account properly. We expect to see the description in the Teiid designer.
> Same goes when we export a Teiid vdb to a vdb xml: the descriptions are not generated as xml elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2809) Import/Export Dynamic VDB utility ignores visibility flag and always sets to true
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2809?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2809:
-----------------------------------
Labels: release_notes verified_jbdsis-8.0.7 (was: )
> Import/Export Dynamic VDB utility ignores visibility flag and always sets to true
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2809
> URL: https://issues.jboss.org/browse/TEIIDDES-2809
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.7
> Fix For: 10.0, 9.0.7
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the visibility flags are not taken into account properly: all models have the visible flag enabled in the vdb, however, i expect models with visbile="false" to have the visible flag disabled.
> Same goes when we export a Teiid vdb to a vdb xml: the visibilty flags are not taken into account properly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2809) Import/Export Dynamic VDB utility ignores visibility flag and always sets to true
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2809?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2809.
----------------------------------
> Import/Export Dynamic VDB utility ignores visibility flag and always sets to true
> ---------------------------------------------------------------------------------
>
> Key: TEIIDDES-2809
> URL: https://issues.jboss.org/browse/TEIIDDES-2809
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Patch Release
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.7
> Fix For: 10.0, 9.0.7
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the visibility flags are not taken into account properly: all models have the visible flag enabled in the vdb, however, i expect models with visbile="false" to have the visible flag disabled.
> Same goes when we export a Teiid vdb to a vdb xml: the visibilty flags are not taken into account properly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2727) SQL Queries generated via "Generate REST Virtual Procedures" do not work when executed directly in JBoss Developer Studio
by Joao Viragine (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2727?page=com.atlassian.jira.plu... ]
Joao Viragine commented on TEIIDDES-2727:
-----------------------------------------
The same error occurs for "Create Web Services"
> SQL Queries generated via "Generate REST Virtual Procedures" do not work when executed directly in JBoss Developer Studio
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2727
> URL: https://issues.jboss.org/browse/TEIIDDES-2727
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution, Web Services Support
> Affects Versions: 9.2
> Reporter: sw vajanyatek
>
> The following procedure was generated via right-clicking a view model --> "Generate REST Virtual Procedures":
> {code:sql}
> BEGIN
> SELECT XMLELEMENT(NAME elems, XMLATTRIBUTES(ss4_view.stockRestProc.pk_stockid_in AS pk_stockid_in), XMLAGG(XMLELEMENT(NAME elem, XMLFOREST(ss4_view.stock.stockid, ss4_view.stock.exchangeid, ss4_view.stock.ticker, ss4_view.stock.name, ss4_view.stock.description, ss4_view.stock.notes)))) AS xml_out FROM ss4_view.stock WHERE ss4_view.stockRestProc.pk_stockid_in = ss4_view.stock.stockid;
> END
> {code}
> The resulting REST service (../json/stock/{stockid}) produces the expected results and appears fine. However, executing the following in a sql script connected to the same teiid server via jdbc produces an exception:
> {code:sql}
> SELECT XMLELEMENT(NAME elems
> , XMLAGG(XMLELEMENT(NAME elem,
> XMLFOREST(ss4_view.stock.stockid
> , ss4_view.stock.exchangeid
> , ss4_view.stock.ticker
> , ss4_view.stock.name
> , ss4_view.stock.description
> , ss4_view.stock.notes)
> )
> )
> ) AS xml_out
> FROM ss4_view.stock
> WHERE 4 = ss4_view.stock.stockid;
> {code}
> {{org.teiid.net.socket.SingleInstanceCommunicationException: java.io.OptionalDataException}}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2817) Unable to export DDL for table/view for a selected database type
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2817?page=com.atlassian.jira.plu... ]
Matus Makovy closed TEIIDDES-2817.
----------------------------------
> Unable to export DDL for table/view for a selected database type
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2817
> URL: https://issues.jboss.org/browse/TEIIDDES-2817
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.2, 9.0.6, 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-8.0.7
> Fix For: 10.0, 9.0.7
>
>
> At one time, was able to export a view/table to DDL. As part of the export process, select the database dialect to have the syntax based on. The resulting file should be a ddl file that can be executed on the database. This is important to the external materialization process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2817) Unable to export DDL for table/view for a selected database type
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2817?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2817:
-----------------------------------
Labels: release_notes verified_jbdsis-8.0.7 (was: )
> Unable to export DDL for table/view for a selected database type
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2817
> URL: https://issues.jboss.org/browse/TEIIDDES-2817
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Affects Versions: 9.2, 9.0.6, 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-8.0.7
> Fix For: 10.0, 9.0.7
>
>
> At one time, was able to export a view/table to DDL. As part of the export process, select the database dialect to have the syntax based on. The resulting file should be a ddl file that can be executed on the database. This is important to the external materialization process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-2779) Error message needs to be more descriptive
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2779?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2779:
-----------------------------------
Summary: Error message needs to be more descriptive (was: Error message needs to more descriptive)
> Error message needs to be more descriptive
> ------------------------------------------
>
> Key: TEIIDDES-2779
> URL: https://issues.jboss.org/browse/TEIIDDES-2779
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.2
> Reporter: Matus Makovy
> Attachments: FinancialsVDB(1).vdb, FinancialsVDB.vdb, Screen Shot 2015-08-10 at 20.47.59.png
>
>
> Issue coppied from BZ (original reporter is cojan(a)redhat.com)
> An exception occurred while performing a VDB operation * null while trying a export an unsupported VDB to dynamic VDB
> Document URL:
> N/A
> Section Number and Name:
> Describe the issue:
> Installed jbosstools-teiid-designer-9.0.2.Final-SNAPSHOT-POC-v7.zip in JBDS 8.1.0.GA
> to have the functionality (pre-production) of being able to generate Dynamic VDB out of VDBs.
> Error message is not descriptive when trying to export a VDB to a Dynamic VDB
> An exception occurred while performing a VDB operation
> * null
> See attachment for screenshot. Trying to export the FinancialsVDB
> Suggestions for improvement:
> null should be something like unsupported VDB
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Matej Kralik reopened TEIIDDES-2493:
------------------------------------
When I create a flat file CP I set direction to folder which contains empty space (error message is appeared and I cannot continue) but when I click on "Test Connection" button, error message is disappeared and I can continue.
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0, 9.2.1
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months