[JBoss JIRA] (TEIIDDES-3013) Creating SOAP war causes java.lang.RuntimeException
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created TEIIDDES-3013:
----------------------------------------
Summary: Creating SOAP war causes java.lang.RuntimeException
Key: TEIIDDES-3013
URL: https://issues.jboss.org/browse/TEIIDDES-3013
Project: Teiid Designer
Issue Type: Bug
Components: Web Services Support
Affects Versions: 10.0.2
Reporter: Hisanobu Okuda
When 2 models in a vdb have a view/table of the same name, creating SOAP war causes java.lang.RuntimeException.
{code}
!MESSAGE An error occurred while creating WAR file, check log for detail
!STACK 0
java.lang.RuntimeException: Unable to generate WSDL
at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:732)
at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:239)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:437)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:353)
at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:481)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
at org.eclipse.jface.window.Window.open(Window.java:794)
at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:115)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
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:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
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:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1732.
------------------------------------
Resolution: Done
most of these improvements were added via TEIIDDES-2812. Marking as resolved
> Stream line steps to implement all the steps around materialization
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1732
> URL: https://issues.jboss.org/browse/TEIIDDES-1732
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
>
> Would like to stream line the steps to putting materialization to work. Example:
> - Right mouse click on view, select materialization
> - present wizard to walk thru the following options:
> - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created)
> - put name of mat table into the selected table/view to be materialized
> - [optional] export DDL (file system or clipboard)
> - [optional] create procedure that has the "select into" for refreshing
> Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table.
> Once thru this wizard, (I think) everything is in place to do materialization for the specified table.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1732:
-----------------------------------
Fix Version/s: 11.0.1
(was: 11.1)
> Stream line steps to implement all the steps around materialization
> --------------------------------------------------------------------
>
> Key: TEIIDDES-1732
> URL: https://issues.jboss.org/browse/TEIIDDES-1732
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
>
> Would like to stream line the steps to putting materialization to work. Example:
> - Right mouse click on view, select materialization
> - present wizard to walk thru the following options:
> - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created)
> - put name of mat table into the selected table/view to be materialized
> - [optional] export DDL (file system or clipboard)
> - [optional] create procedure that has the "select into" for refreshing
> Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table.
> Once thru this wizard, (I think) everything is in place to do materialization for the specified table.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2660) Add support in Designer for foreign keys cross models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2660?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2660.
------------------------------------
Resolution: Done
This was enabled as part of fix for TEIIDDES-2812. Allows FK/PK relationships across models in a common Model Project
> Add support in Designer for foreign keys cross models
> -----------------------------------------------------
>
> Key: TEIIDDES-2660
> URL: https://issues.jboss.org/browse/TEIIDDES-2660
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
>
> Add support in Designer for foreign keys cross models.
> In Designer you cannot have a FK cross models. That is not a limitation with DDL metadata in Teiid. It's a misstatement to relate that to optimization. If the PK/FK is present we'll use that information just as we would in a single source - we do not however enforce the FK. That can be done through the use of an update procedure though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2660) Add support in Designer for foreign keys cross models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2660?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2660:
-----------------------------------
Fix Version/s: 11.0.1
(was: 11.1)
> Add support in Designer for foreign keys cross models
> -----------------------------------------------------
>
> Key: TEIIDDES-2660
> URL: https://issues.jboss.org/browse/TEIIDDES-2660
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
>
> Add support in Designer for foreign keys cross models.
> In Designer you cannot have a FK cross models. That is not a limitation with DDL metadata in Teiid. It's a misstatement to relate that to optimization. If the PK/FK is present we'll use that information just as we would in a single source - we do not however enforce the FK. That can be done through the use of an update procedure though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2989) Missing UDF settings in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2989?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2989:
-----------------------------------
Fix Version/s: 11.0.1
(was: 11.1)
> Missing UDF settings in dynamic VDB
> -----------------------------------
>
> Key: TEIIDDES-2989
> URL: https://issues.jboss.org/browse/TEIIDDES-2989
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
> Attachments: MissingUDF.zip
>
>
> When I created UDF function, generate dynamic vdb and generate back view model some things missed there.
> When I set all checkboxes in properties on true in UDF dialog in view model, a lot of them missing in dynamic vdb and of course in view model after generating.
> Determistic checkbox: There is mention in dynamic vdb but wrong because after generating view model is false.
> "Returns null on null" and "Variable Arguments" are set correct
> Other checkboxes(Aggregate, Analytic, ...) are not mention in dynamic vdb and missing in view model after generating
> Update Count is always AUTO same as in srouce model.
> Missing Name in Source for parameters.
> And If I set direction for some column at RETURN, in dynamic vdb is changed on OUT.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-2989) Missing UDF settings in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2989?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2989.
------------------------------------
Resolution: Done
master: https://github.com/Teiid-Designer/teiid-designer/commit/58f21d9671d8747bc...
> Missing UDF settings in dynamic VDB
> -----------------------------------
>
> Key: TEIIDDES-2989
> URL: https://issues.jboss.org/browse/TEIIDDES-2989
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Assignee: Barry LaFond
> Fix For: 11.0.1
>
> Attachments: MissingUDF.zip
>
>
> When I created UDF function, generate dynamic vdb and generate back view model some things missed there.
> When I set all checkboxes in properties on true in UDF dialog in view model, a lot of them missing in dynamic vdb and of course in view model after generating.
> Determistic checkbox: There is mention in dynamic vdb but wrong because after generating view model is false.
> "Returns null on null" and "Variable Arguments" are set correct
> Other checkboxes(Aggregate, Analytic, ...) are not mention in dynamic vdb and missing in view model after generating
> Update Count is always AUTO same as in srouce model.
> Missing Name in Source for parameters.
> And If I set direction for some column at RETURN, in dynamic vdb is changed on OUT.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (TEIIDDES-3012) Update JBoss TP to 4.4.1
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-3012:
--------------------------------------
Summary: Update JBoss TP to 4.4.1
Key: TEIIDDES-3012
URL: https://issues.jboss.org/browse/TEIIDDES-3012
Project: Teiid Designer
Issue Type: Task
Components: Build
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 11.0.1
Next JBDSIS release: 10.1.0 - Neon is using JBoss TP 4.4.1
Upgrade 11.0.1 to use this TP
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months