[JBoss JIRA] Resolved: (TEIIDDES-300) Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time
by John Doyle (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-300?page=com.atlassian.jira.plugin... ]
John Doyle resolved TEIIDDES-300.
---------------------------------
Resolution: Out of Date
Web Services are not modeled in this manner in Teiid 7.0.
> Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-300
> URL: https://jira.jboss.org/browse/TEIIDDES-300
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.1
> Environment: 5.5SP3 GA Designer on Linux
> Reporter: Greg Haber
> Assignee: John Doyle
> Attachments: FinancialsDemo_20081130_4.zip, no-parameter-stacktrace.txt, StockQuoteService-ghh.wsdl, StockQuoteService.aar, wsTest1.zip
>
>
> When the Web Service as Relational importer creates a source model, it creates a single request table and one or more response tables to model the web service operation. If there are any required parameters in the web service requests (those which do not contain the property "minOccurs=0") the right way to represent this in MetaMatrix would be via an access pattern.
> But the importer does not create such an access pattern on the request tables, which means that if the preview functionality is run against them, it tries to do a query against the table with no parameters specified, resulting in an error from the XML-Relational SOAP connector (stacktrace attached).
> The importer should create such an access pattern to more correctly reflect the actual behavior of the web service (and our connector framework).
> I'm attaching the model project set for my test, the WSDL for the service (as deployed on my machine), and the .aar file for the actual service (to use just deploy the Axis 2 war from http://www.gtlib.gatech.edu/pub/apache/ws/axis2/1_4_1/axis2-1.4.1-war.zip on a server, and then drop the .aar file in the axis2/WEB-INF/services directory that should exist on your server after deployment).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-506) Importing tables from a deployed VDB does not import columns
by Paul Nittel (JIRA)
Importing tables from a deployed VDB does not import columns
------------------------------------------------------------
Key: TEIIDDES-506
URL: https://jira.jboss.org/browse/TEIIDDES-506
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.0
Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final
Reporter: Paul Nittel
I created, and deployed, a VDB containing source and view models. I am able to query these tables.
I created a new project and into that project I attempted to import a view model's table from the previously-created VDB. What I found in the imported was the models and tables were shown, but no columns were available for import. Once imported, the tables did have no columns.
Screenshot and other stuff attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Moved: (TEIIDDES-504) Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL
by Steve Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIIDDES-504?page=com.atlassian.jira.plugin... ]
Steve Hawkins moved TEIID-983 to TEIIDDES-504:
----------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-504 (was: TEIID-983)
Affects Version/s: (was: 7.1)
Component/s: Documentation
(was: Documentation)
Fix Version/s: (was: 7.1)
> Getting Started With Designer kit needs updating to fix schema differences between SQL Server and MySQL
> -------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-504
> URL: https://jira.jboss.org/browse/TEIIDDES-504
> Project: Teiid Designer
> Issue Type: Task
> Components: Documentation
> Reporter: Larry O'Leary
> Assignee: Van Halbert
>
> The Intro to Designer training was originally written to use the MMFinancials schema for SQL Server. It appears that some data types are not imported the same way when the MySQL schema is used. This results in data type differences between the written instructions and the MySQL schema that is most commonly used in the Getting Started kit.
> For example, the ProductShares column in the AccountHoldings table is being imported as a biginteger when using SQL Server but as a bigdecimal when using MySQL. This difference then results in reconciler/transformation errors due to type incompatibility which require explicit conversions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months
[JBoss JIRA] Created: (TEIIDDES-495) Can't save a VDB after adding model.
by John Doyle (JIRA)
Can't save a VDB after adding model.
------------------------------------
Key: TEIIDDES-495
URL: https://jira.jboss.org/browse/TEIIDDES-495
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.0
Environment: RHEL 5
Sun java version "1.6.0_14"
Eclipse Version: 3.5.1 Build id: M20090917-0800
Reporter: John Doyle
I've created a single physical model via import and an empty VDB. I can add the model to the VDB with the editor, but cannot save the changes to the VDB.
java.lang.RuntimeException: Unable to rename /tmp/oracle/poof.vdb to /NotBackedUp/jdoyle/teiid_designer_7.0.M3/ws/oracle/poof.vdb
at org.teiid.designer.vdb.Vdb$2.tryToDo(Vdb.java:406)
at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:37)
at org.teiid.designer.vdb.Vdb.save(Vdb.java:365)
at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:556)
at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151)
at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:274)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2579)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:282)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:261)
at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156)
at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1357)
at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3328)
at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3341)
at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:76)
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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510)
at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1175)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1185)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1212)
at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:706)
at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2837)
at org.eclipse.swt.widgets.Button.gtk_key_press_event(Button.java:439)
at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1570)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4587)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4191)
at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:7588)
at org.eclipse.swt.widgets.Display.eventProc(Display.java:1185)
at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1860)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3110)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
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:368)
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:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 9 months