[JBoss JIRA] (TEIIDDES-2155) Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
by Ted Jones (JIRA)
Ted Jones created TEIIDDES-2155:
-----------------------------------
Summary: Generating WS From Source Procedure Fails when Direction Type for Column is RETURN
Key: TEIIDDES-2155
URL: https://issues.jboss.org/browse/TEIIDDES-2155
Project: Teiid Designer
Issue Type: Bug
Components: Web Services Support
Affects Versions: 8.3.2
Reporter: Ted Jones
Assignee: Ted Jones
Priority: Critical
Fix For: 8.5, 8.3.3
When generating a web service for a source model, we check for direction types of OUT and IN/OUT, but do not check for a type of RETURN. This cause the ws model generation to fail with an error stating their is no root.
Need to add check for RETURN direction type.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2052) 'Mark as Deployable' on a war not working for remote (OpenShift) server
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2052?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2052:
------------------------------------
Fix Version/s: 8.6
(was: 8.5)
push to next release - see related JIRA
> 'Mark as Deployable' on a war not working for remote (OpenShift) server
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2052
> URL: https://issues.jboss.org/browse/TEIIDDES-2052
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.6
>
>
> I created a war (using Rest War generator) in Designer and added it to my project. Then to deploy it, I selected it and used the 'Mark as Deployable" action.
> This worked fine on my local server (both deploy and undeploy) but then I switched to an OpenShift external server instance (used port-forwarding).
> The 'Mark as Deployable' action doesnt work for the Openshift external server. Maybe the action is doing a copy of the war into the deployments folder?
> We don't provide the action, but we should either troubleshoot or potentially provide our own action which deploys a war using the admin api.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2052) 'Mark as Deployable' on a war not working for remote (OpenShift) server
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2052?page=com.atlassian.jira.plu... ]
Mark Drilling commented on TEIIDDES-2052:
-----------------------------------------
Related tools jira.
> 'Mark as Deployable' on a war not working for remote (OpenShift) server
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2052
> URL: https://issues.jboss.org/browse/TEIIDDES-2052
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.3.1
> Reporter: Mark Drilling
> Assignee: Mark Drilling
> Fix For: 8.5
>
>
> I created a war (using Rest War generator) in Designer and added it to my project. Then to deploy it, I selected it and used the 'Mark as Deployable" action.
> This worked fine on my local server (both deploy and undeploy) but then I switched to an OpenShift external server instance (used port-forwarding).
> The 'Mark as Deployable' action doesnt work for the Openshift external server. Maybe the action is doing a copy of the war into the deployments folder?
> We don't provide the action, but we should either troubleshoot or potentially provide our own action which deploys a war using the admin api.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-1024) Create separate icons for different types of models
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1024?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1024.
------------------------------------
Resolution: Out of Date
Already done in prior release
> Create separate icons for different types of models
> ---------------------------------------------------
>
> Key: TEIIDDES-1024
> URL: https://issues.jboss.org/browse/TEIIDDES-1024
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Ramesh Reddy
> Priority: Minor
> Fix For: Future
>
>
> Currently the Designer only shows blue (source models), orange(view models) cubes for the models. It would be useful to show different types of icons for each model type. For example, use DB icon for Relational Database, or file icon for file based sources, xml, web-service so on. This will help identify the sources quickly when combined with names.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-956) In Designer, when there is an error, provide context in project explorer view mouseover or table view mouseover
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-956?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-956:
----------------------------------
Fix Version/s: Komodo
> In Designer, when there is an error, provide context in project explorer view mouseover or table view mouseover
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-956
> URL: https://issues.jboss.org/browse/TEIIDDES-956
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 7.3
> Environment: JBDS 4.0.0 GA
> Reporter: Joel Tosi
> Fix For: Komodo
>
>
> When doing some modeling in Designer, create an error state - for example create a foreign key relationship with one side missing. You will get the error in the Message Log stating the error, but also a visual on the table in the model as well as the model in project view (red Xs).
> Please support a mouseover affect - i.e. if I mouseover the table (where the red X is) I would see the error. Same thing for the project explorer view. This would be more consistant with development in Eclipse
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-858) Cannot Print Metadata Model Diagram under Linix
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-858?page=com.atlassian.jira.plug... ]
Barry LaFond resolved TEIIDDES-858.
-----------------------------------
Resolution: Out of Date
Printing diagram feature has been removed
> Cannot Print Metadata Model Diagram under Linix
> -----------------------------------------------
>
> Key: TEIIDDES-858
> URL: https://issues.jboss.org/browse/TEIIDDES-858
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dialogs
> Affects Versions: 7.1
> Environment: Arch: Linux,GTK,x86
> Distr: Ubuntu 10.10
> Reporter: Denis Golovin
> Fix For: Future
>
>
> After creating diagram Select File->Print from bar menu. Then select printer and press Print button. It shows error dialog and reports exception in Error Log View:
> {noformat}org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4109)
> at org.eclipse.swt.SWT.error(SWT.java:3998)
> at org.eclipse.swt.SWT.error(SWT.java:3969)
> at org.eclipse.swt.printing.Printer.internal_new_GC(Printer.java:393)
> at org.eclipse.swt.graphics.GC.<init>(GC.java:159)
> at org.eclipse.swt.graphics.GC.<init>(GC.java:125)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getPrinterGC(DiagramPrintingAnalyzer.java:228)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getFreshPrinterGraphics(DiagramPrintingAnalyzer.java:220)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printLandscape_PrinterIsPortrait(DiagramPrintingOperation.java:690)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printPages(DiagramPrintingOperation.java:403)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.countPages(DiagramPrintingAnalyzer.java:170)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.setPageSize(DiagramPrintingAnalyzer.java:68)
> at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.<init>(DiagramPrintingAnalyzer.java:44)
> at com.metamatrix.modeler.diagram.ui.actions.PrintWrapper.doRun(PrintWrapper.java:100)
> at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
> at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
> at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:820)
> at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:806)
> at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:796)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> 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:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> 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:616)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407){noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-694) Property view's Restore Default Value never seems to be enabled
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-694?page=com.atlassian.jira.plug... ]
Barry LaFond resolved TEIIDDES-694.
-----------------------------------
Resolution: Won't Fix
Designer extends Eclipse's PropertySheetPage which controls the default value action/button.
> Property view's Restore Default Value never seems to be enabled
> ---------------------------------------------------------------
>
> Key: TEIIDDES-694
> URL: https://issues.jboss.org/browse/TEIIDDES-694
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.1.1
> Environment: Windows, JBDS 4.0 Beta 1
> Reporter: Paul Nittel
> Assignee: Dan Florian
> Priority: Minor
> Fix For: Future
>
>
> Using a relational source model, I found that I was not able to get the Restore Default Value action to enable, even after changing from a default value. I changed Supports JOIN from TRUE to FALSE for this experiment.
> Barry indicated he'd add more technical detail to this Jira.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 8 months