June 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-201) Connector Binding Editor scroll bar does not allow you to scroll far enough if long properties are present.

by John Doyle (JIRA)

Connector Binding Editor scroll bar does not allow you to scroll far enough if long properties are present. ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-201 URL: https://jira.jboss.org/jira/browse/TEIIDDES-201 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 6.1.0 Environment: Designer 6.1 running in IDE on RHEL CSB. Reporter: John Doyle The Connector Binding editor does not allow enough scrolling to see very long fields. For example, the XML-Relational SOAP Connector has a very long classpath (you have to display advanced properties), and there is no way to scroll to the end of it. -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-194) jdbc Oracle import does not create connector

by Luca Gioppo (JIRA)

jdbc Oracle import does not create connector -------------------------------------------- Key: TEIIDDES-194 URL: https://jira.jboss.org/jira/browse/TEIIDDES-194 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0 Environment: eclipse.buildId=M20080911-1700 java.version=1.6.0_04 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86 Reporter: Luca Gioppo Importing model from jdbc Creating a new source for an Oracle 9 DB using jdbc14.jar and adding to udf (and a second time in the source definition) the jar from the oracle instant client the connection work, tables are imported but at hte end of the import the error is: Error post processing import (extension class=class com.metamatrix.modeler.internal.dqp.ui.jdbc.ConnectorBindingImportPostProcessor) -- 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

14 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-121) Simplify Adding Connector Jar as UDF jar in UDF view

by Barry LaFond (JIRA)

Simplify Adding Connector Jar as UDF jar in UDF view ---------------------------------------------------- Key: TEIIDDES-121 URL: https://jira.jboss.org/jira/browse/TEIIDDES-121 Project: Teiid Designer Issue Type: Feature Request Components: Views Affects Versions: 6.1.0 Reporter: Barry LaFond Priority: Minor Fix For: 6.1.0 Current UDF view provides two actions: Import UDF Extension Jars & Add Connector Jars to UDF The second action is somewhat redundant. Request moving the functionality of the second action into an "Advanced" section of the dialog from the first action. -- 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

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-174) Closing Project does not hide project-specific source bindings in Connectors View

by Barry LaFond (JIRA)

Closing Project does not hide project-specific source bindings in Connectors View --------------------------------------------------------------------------------- Key: TEIIDDES-174 URL: https://jira.jboss.org/jira/browse/TEIIDDES-174 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Reporter: Barry LaFond Priority: Minor Fix For: Future 1) Import Books or Parts and verify Connectors and Source Binding is created in Connectors View 2) Right-click Project and "Close Project" 3) Source bindings still visible (should be removed) 4) Select/deselect the "Hide Connectors Types" button on Connectors view toolbar 5) Sources bindings are now hidden. 6) Re-open project and Source bindings now visible Problem with refresh on Connectors View during Project Close action. -- 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

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-472) Support multi-source bindings

by John Verhaeg (JIRA)

Support multi-source bindings ----------------------------- Key: TEIIDDES-472 URL: https://jira.jboss.org/browse/TEIIDDES-472 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Probably need a framework somewhat similar to data roles, but at a model level, to manage these bindings such that they can be validated against or selected when editing a transformation. The VDB and its editor then need to be modified to support capturing this information and tying it to appropriate translators and JNDI names. -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-425) Add query capabilities to the Import from JDBC in the Designer

by Debbie Steigner (JIRA)

Add query capabilities to the Import from JDBC in the Designer -------------------------------------------------------------- Key: TEIIDDES-425 URL: https://jira.jboss.org/jira/browse/TEIIDDES-425 Project: Teiid Designer Issue Type: Feature Request Reporter: Debbie Steigner Fix For: 7.0 For dealing with databases with extrremely large numbers of tables 10,000 +, it would be very helpful to have these 2 features: 1. Search / Filter capabilities 2. Ability to turn off the tables details on the "right" side of the dialog as retrieving that data table by table is exceedingly slow especially when dealing with 1000's of tables. -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-469) Modify WSDL Management

by John Verhaeg (JIRA)

Modify WSDL Management ---------------------- Key: TEIIDDES-469 URL: https://jira.jboss.org/browse/TEIIDDES-469 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.1 Need to change web service metamodel and/or annotation handling to include generation of WSDL URL that used to be in VDB Also need to deal with generation of WSDL and WAR somewhere. -- 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

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-484) Error adding model to a vdb

by Steve Hawkins (JIRA)

Error adding model to a vdb --------------------------- Key: TEIIDDES-484 URL: https://jira.jboss.org/browse/TEIIDDES-484 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Reporter: Steve Hawkins Starting with a new project and an empty vdb, I created a new empty physical relational model and added it to the vdb. The resulting exception was: java.lang.RuntimeException: javax.xml.bind.MarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.] at com.metamatrix.core.modeler.CoreModelerPlugin.throwRuntimeException(CoreModelerPlugin.java:64) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:46) 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) Caused by: javax.xml.bind.MarshalException - with linked exception: [org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'.] at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:317) at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:243) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:75) at org.teiid.designer.vdb.Vdb$2.tryToDo(Vdb.java:390) at com.metamatrix.core.modeler.util.OperationUtil.perform(OperationUtil.java:37) ... 66 more Caused by: org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'translator-name' must appear on element 'source'. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:131) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:384) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:318) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:410) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(XMLSchemaValidator.java:3165) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.addDefaultAttributes(XMLSchemaValidator.java:2859) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(XMLSchemaValidator.java:2041) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(XMLSchemaValidator.java:685) at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorHandlerImpl.startElement(ValidatorHandlerImpl.java:549) at org.xml.sax.helpers.XMLFilterImpl.startElement(XMLFilterImpl.java:527) at com.sun.xml.internal.bind.v2.runtime.output.SAXOutput.endStartTag(SAXOutput.java:113) at com.sun.xml.internal.bind.v2.runtime.output.ForkXmlOutput.endStartTag(ForkXmlOutput.java:91) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.endAttributes(XMLSerializer.java:294) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:686) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157) at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:321) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsXsiType(XMLSerializer.java:687) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementNodeProperty.serializeItem(ArrayElementNodeProperty.java:54) at com.sun.xml.internal.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:157) at com.sun.xml.internal.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:141) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:321) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:581) at com.sun.xml.internal.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:309) at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:482) at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:314) ... 70 more -- 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-237) Create an Eclipse Data Tools integration to execute VDBs deployed in Teiid Server.

by John Doyle (JIRA)

Create an Eclipse Data Tools integration to execute VDBs deployed in Teiid Server. ---------------------------------------------------------------------------------- Key: TEIIDDES-237 URL: https://jira.jboss.org/jira/browse/TEIIDDES-237 Project: Teiid Designer Issue Type: Feature Request Components: Eclipse Integration, VDB & Execution Affects Versions: 6.3 Environment: Eclipse DTP environments. Reporter: John Doyle Assignee: John Doyle Fix For: 6.3 Teiid Designer currently executes VDBs with an embedded version of Teiid. Implementing the Eclipse DTP extension points will enable the designer to rely upon an external Teiid server to perform VDB execution, will provide Teiid connectivity for JBossTools, and enable the Teiid Designer to dump its fork of SQL Explorer. See this wiki doc for more detail. https://www.jboss.org/community/wiki/TeiidProjectsandtheEclipseDTP -- 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

14 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-190) There is no way to hand model a XML-Relational source.

by John Doyle (JIRA)

There is no way to hand model a XML-Relational source. ------------------------------------------------------ Key: TEIIDDES-190 URL: https://jira.jboss.org/jira/browse/TEIIDDES-190 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: John Doyle Fix For: 6.1.1 We used to ship the model extensions for XML-R modeling with the importer, and now we generate them on demand with the importer. However, if a user needs to hand model from scratch, perhaps because there is no XSD, there is no model extension to depend on. We need to provide a way to create just the extension. -- 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

14 years, 6 months

1
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2010