October 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-603) Change Generated CXF WAR to create Dynamic Web Project

by Ted Jones (JIRA)

Change Generated CXF WAR to create Dynamic Web Project ------------------------------------------------------- Key: TEIIDDES-603 URL: https://jira.jboss.org/browse/TEIIDDES-603 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.2 When creating a CXF war from web service models, the war artifacts should be saved as a dynamic web projects in JBoss Tools. This will allow the user to view and manipulate the generated files and deploy to an AS server view -- 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

12 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-983) Add Export Option for Generated SOAP and REST Wars

by Ted Jones (JIRA)

Add Export Option for Generated SOAP and REST Wars -------------------------------------------------- Key: TEIIDDES-983 URL: https://issues.jboss.org/browse/TEIIDDES-983 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.5 Currently (in 7.4), the JBossWS-CXF and RESTEasy wars are generated via the VDB context menu option Modeling->Generate JBossWS-CXF WAR or Generate RESTEasy WAR. It would be nice to make this an Export option to flow more logically with the rest of Designer processing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-119) XML-Relaional modeling needs to be easier for sources that do not provide an XSD.

by John Doyle (JIRA)

XML-Relaional modeling needs to be easier for sources that do not provide an XSD. --------------------------------------------------------------------------------- Key: TEIIDDES-119 URL: https://jira.jboss.org/jira/browse/TEIIDDES-119 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Reporter: John Doyle Assignee: John Doyle The main case for this is REST services. REST services do not have a standard description mechanism like WSDL for SOAP services. The inputs and outputs of the service might be documented in a HTML help page, with sample XML documents, with WADL, etc. Hand modeling is too difficult, so we need to come up with other assists. The solution is probably a mix of new features and documented best practices. For example: Add WADL support to the importer. Document use of a schema from XML tool (like inst2XSD) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
11
0 / 0

[JBoss JIRA] (TEIIDDES-1111) Create a model(s) (view/source) based on the schema and type of data source provided

by Ramesh Reddy (Created) (JIRA)

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: Feature Request Components: Import/Export Reporter: Ramesh Reddy 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-465) Trying to import wsdl as at Relation Model but unable to select a method

by Van Halbert (JIRA)

Trying to import wsdl as at Relation Model but unable to select a method ------------------------------------------------------------------------ Key: TEIIDDES-465 URL: https://jira.jboss.org/browse/TEIIDDES-465 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.3 Reporter: Van Halbert Trying to import the wsdl jrl_inquirywsdl.wsdl (in attached zip) using the import --> WSDL to Relational Model option. After selecting the wsdl from the file system, then validating, the next panel presented the methods to select (none-preselected). When you highlight a method, in the Select Details section it says: "The style for the service cannot be determined. " The next or finished button was never enabled. -- 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

12 years, 2 months

4
11
0 / 0

[JBoss JIRA] Created: (TEIIDDES-633) Pasting a vlue into a model editor's table view (for example, column) gets NPE

by Paul Nittel (JIRA)

Pasting a vlue into a model editor's table view (for example, column) gets NPE ------------------------------------------------------------------------------ Key: TEIIDDES-633 URL: https://jira.jboss.org/browse/TEIIDDES-633 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.1 Environment: All Reporter: Paul Nittel Fix For: 7.1.1 Pasting the value 666 into the length of a column got this error: Cannot set value "666" for the length property of this Column And this NPE: Error 2010-09-24 10:55:36.516 Cannot set value "666" for the length property of this Column java.lang.NullPointerException at org.eclipse.emf.edit.provider.ItemProviderAdapter.getPropertyDescriptor(ItemProviderAdapter.java:258) at com.metamatrix.modeler.internal.ui.properties.ModelObjectPropertySource.getPropertyValue(ModelObjectPropertySource.java:332) at com.metamatrix.modeler.internal.ui.table.ModelRowElement.setValue(ModelRowElement.java:244) at com.metamatrix.modeler.internal.ui.table.ModelTableEditor.pasteClipboardContents(ModelTableEditor.java:1400) at com.metamatrix.modeler.internal.ui.actions.TableClipboardPasteAction.doRun(TableClipboardPasteAction.java:41) 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.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.Text.gtk_key_press_event(Text.java:1412) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1570) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4594) 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:7603) 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

12 years, 2 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1090) Usability:Confusion in the View model, create a base table or a view table

by Van Halbert (Created) (JIRA)

Usability:Confusion in the View model, create a base table or a view table -------------------------------------------------------------------------- Key: TEIIDDES-1090 URL: https://issues.jboss.org/browse/TEIIDDES-1090 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.4.2 Reporter: Van Halbert In the view model, there really isn't any feature/functional difference for which one should be recommended over the other. The only difference I see is that the view table doesn't have the ability to create indexes/keys as the base table. Which brings in the question, do we really need two way's to create a view table, regardless what we call it? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-837) NPEs found in Designer log after testing SalesForce

by Paul Nittel (JIRA)

NPEs found in Designer log after testing SalesForce --------------------------------------------------- Key: TEIIDDES-837 URL: https://issues.jboss.org/browse/TEIIDDES-837 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1.1 Reporter: Paul Nittel Attachments: NpeUhOh.log, NpeUhOh_MPS.zip While testing the SalesForce importer, I noticed I was getting a new NPE each time I clicked in the Model explorer tree. I don't know when it started, so I can't say what may have triggered it. But in the hope that you may find something, I've attached the exported log. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-949) Usability: Use FK/PK relationships to prebuild JOIN when building view

by Van Halbert (JIRA)

Usability: Use FK/PK relationships to prebuild JOIN when building view ----------------------------------------------------------------------- Key: TEIIDDES-949 URL: https://issues.jboss.org/browse/TEIIDDES-949 Project: Teiid Designer Issue Type: Enhancement Components: Modeling, Views Affects Versions: 7.1.1 Reporter: Van Halbert When creating a new view which includes two tables which do have FK/PK relationship defined (as links), the view should automatically add the JOIN clause. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-175) Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid.

by John Doyle (JIRA)

Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid. ----------------------------------------------------------------------------------------------------- Key: TEIIDDES-175 URL: https://jira.jboss.org/jira/browse/TEIIDDES-175 Project: Teiid Designer Issue Type: Feature Request Components: Teiid Integration Reporter: John Doyle Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different versions of Teiid in order to test models/VDBs across different versions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues October 2011