August 2012 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-122) Add WSDL 2.0 Support to Designer for Data Services

by Ted Jones (JIRA)

Add WSDL 2.0 Support to Designer for Data Services -------------------------------------------------- Key: TEIIDDES-122 URL: https://jira.jboss.org/jira/browse/TEIIDDES-122 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Ted Jones Fix For: 6.0.0 In order to support REST (see TEIID-417), we need to allow for the generation of WSDL 2.0 specific WSDL. We still need to allow for the generation of WSDL 1.1 since WSDL 2.0 is not widely supported by many tools. There should be an option in the Designer to specify which version of the WSDL specification to use when generating the WSDL file. I suggest putting the option on the Web Services tab of the VDB, but I am open for other suggestions. Alternatively, we could add the WSDL using both specifications in separate WSDL files and then provide a different WSDL URL to get one or the other. This approach seems like overkill to me though and would have farther reaching ramifications. Ideally this would be completed for Westport. -- 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

13 years, 8 months

2
12
0 / 0

[JBoss JIRA] (TEIIDDES-1303) Create OData Importer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1303: ----------------------------------- Summary: Create OData Importer Key: TEIIDDES-1303 URL: https://issues.jboss.org/browse/TEIIDDES-1303 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.7 Reporter: Ted Jones Fix For: 7.7.1 To provide support for more complicated OData use cases, we should extend the XML Importer to create an OData importer. This importer will read the metadata of the service in the selected CP and determine what columns are allowable for input. We would then need to create an access pattern on the generated base table for these fields. These fields would be added to the URL of the service.. so the above Bank service URL would become: http://gw.esworkplace.sap.com/sap/opu/sdata/sap/DEMO_BANK/z_demo_bankColl... and the generated transformation should take the column values from the access pattern and build the URL accordingly in the invokeHttp() call. -- 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

13 years, 8 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1336) Consider removal of WS-Security option as unnecessary

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1336: ----------------------------------------- Summary: Consider removal of WS-Security option as unnecessary Key: TEIIDDES-1336 URL: https://issues.jboss.org/browse/TEIIDDES-1336 Project: Teiid Designer Issue Type: Sub-task Reporter: Paul Richardson Assignee: Paul Richardson Priority: Minor The security options for authenticated WSDLs are provided as BASIC and WS-Security. The latter is not considered necessary and should probably be removed from all situations, including the REST importer. -- 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

13 years, 8 months

2
7
0 / 0

[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1229: -------------------------------------- Assignee: Barry LaFond > CLONE - Add support for a comparable binary type > ------------------------------------------------ > > Key: TEIIDDES-1229 > URL: https://issues.jboss.org/browse/TEIIDDES-1229 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.0 > > > Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals. > See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-315) Designer properties tab jumps to a seemingly random location in the properties list when any object is selected

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-315?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-315: ---------------------------------- Fix Version/s: Future (was: 8.0) > Designer properties tab jumps to a seemingly random location in the properties list when any object is selected > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-315 > URL: https://issues.jboss.org/browse/TEIIDDES-315 > Project: Teiid Designer > Issue Type: Bug > Components: Editors > Affects Versions: 7.5 > Reporter: Michael Walker > Assignee: Dan Florian > Fix For: Future > > > Open a view model, click on a column of a view. The properties tab will skip down to the near-bottom of the list of properties. Perhaps it should display the top of the list, assuming you are clicking on a column for the first time. Scrolling to the near-bottom is a bug. > Now move the scroll bar for the properties window up to the top, and edit some property. Click on another column, as if you were going to edit the same property. > The properties tab will once again skip to the near-bottom of the list of properties. > Instead, it should remain wherever it previously was. This will facilitate quicker editing of the same property on multiple objects of the same type. -- 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

13 years, 8 months

1
0
0 / 0

[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 updated TEIIDDES-858: ---------------------------------- Issue Type: Bug (was: Feature Request) Fix Version/s: 8.1 (was: 8.0) > 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: 8.1 > > > 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 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-323) Option to copy from an XSD model of the same model class throws NPE

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-323?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-323. ----------------------------------- Resolution: Cannot Reproduce Bug Tested with JBDS 5.0.1 + SOA 5.3 Tooling Copied Employees.xsd and Books.xsd without error > Option to copy from an XSD model of the same model class throws NPE > ------------------------------------------------------------------- > > Key: TEIIDDES-323 > URL: https://issues.jboss.org/browse/TEIIDDES-323 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.4 > Environment: fedora 10 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.0 > > Attachments: JBEDSP-979_MPS.zip > > > Though there were other metamodels that had problems in 6.x release, the only one left is copying an XSD model > java.lang.NullPointerException > at com.metamatrix.core.util.PluginUtilImpl.log(PluginUtilImpl.java:238) > at com.metamatrix.modeler.internal.ui.wizards.StructuralCopyContributor.doFinish(StructuralCopyContributor.java:86) > at com.metamatrix.modeler.internal.ui.wizards.NewModelWizard$3.run(NewModelWizard.java:341) > Actual NPE is coming from: > org.eclipse.xsd.impl.XSDAttributeUseImpl.analyze() line: 790 > and the rest of the stack is basically EMF based on giving the EMF CopyCommand a model to copy. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-320) Input Sets on Staging tables for XML documents

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-320?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-320. ----------------------------------- Assignee: Barry LaFond (was: Mark Drilling) Resolution: Out of Date Designer docs do not include this incorrect statement. > Input Sets on Staging tables for XML documents > ---------------------------------------------- > > Key: TEIIDDES-320 > URL: https://issues.jboss.org/browse/TEIIDDES-320 > Project: Teiid Designer > Issue Type: Bug > Components: Documentation > Affects Versions: 7.1 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 8.0 > > > In the MetaMatrix Enterprise Designer Users Guide on page 219 it states: > Using Input Sets with Staging Tables > You can use Input Sets withing your staging table transformations as well. When you create a staging table beneath a mapping class, the transformation diagram has an Input Set. > This is not correct, please correct. -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1411) Using CASE statements within transformations cause an NPE

by Hisanobu Okuda (JIRA)

Hisanobu Okuda created TEIIDDES-1411: ---------------------------------------- Summary: Using CASE statements within transformations cause an NPE Key: TEIIDDES-1411 URL: https://issues.jboss.org/browse/TEIIDDES-1411 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 7.4.2 Environment: Teiid Designer Version: 7.4.2 bundled in JBoss Developer Studio 4.1.2.GA Reporter: Hisanobu Okuda CASE clause within transformations causes SQL validation failure and an NPE. -- 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

13 years, 9 months

4
14
0 / 0

[JBoss JIRA] (TEIIDDES-1466) url config property for Salesforce being dropped from -ds.xml creation during deployment from JBDS 5.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1466?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1466: ---------------------------------------- Try with "URL" instead of "url" to fix the issue. The properties are not case sensitive. {code} groovy:000> p = new Properties(); ===> {} groovy:000> p.setProperty("url", "https://login.salesforce.com/services/Soap/u/25.0"); ===> null groovy:000> p.setProperty("username", "mshirley.dev(a)redhat.com"); ===> null groovy:000> p.setProperty("password", "mypass"); ===> null groovy:000> createDataSource("test-salesforce", "connector-salesforce", p); <--- does not work ===> null groovy:000> p.setProperty("URL", "https://login.salesforce.com/services/Soap/u/25.0"); ===> null groovy:000> print(p) [URL:https://login.salesforce.com/services/Soap/u/25.0, password:mypass, url:https://login.salesforce.com/services/Soap/u/25.0, username:mshirley.dev@redhat.com]===> null groovy:000> groovy:000> groovy:000> createDataSource("test-salesforce", "connector-salesforce", p); <-- works {code} > url config property for Salesforce being dropped from -ds.xml creation during deployment from JBDS 5.0 > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1466 > URL: https://issues.jboss.org/browse/TEIIDDES-1466 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Affects Versions: 7.7 > Environment: JBDS 5.0.1 with SOA-Tooling/EDS 5.3 > Reporter: Johnathon Lee > Attachments: sfdcTest.zip > > > The URL specified in the Salesforce connection profile in JBDS is not being written to the datasource when it is created from a JBDS action (either through preview functionality or Model->Create Datasource). > Data sources created from Teiid Designer perspective do not include the SFDC URL input by the user. In some cases this results in the user being unable to authenticate and run queries against the datasource (preview or standard VDB queries) if their user id does not authenticate against the default login.salesforce.com site URLs. Need to correct the datasource creation behavior to push down the URL into the datasource as well. > When creating the datasource using the Modelling->Create Data Source with the "Use Model Connection Info", the end result is the sfdcTest-ds.xml below: > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <connection-factories> > <no-tx-connection-factory> > <jndi-name>sfdcTest</jndi-name> > <rar-name>teiid-connector-salesforce.rar</rar-name> > <use-java-context>true</use-java-context> > <connection-definition>javax.resource.cci.ConnectionFactory</connection-definition> > <jmx-invoker-name>jboss:service=invoker,type=jrmp</jmx-invoker-name> > <min-pool-size>0</min-pool-size> > <max-pool-size>10</max-pool-size> > <blocking-timeout-millis>3000</blocking-timeout-millis> > <idle-timeout-minutes>30</idle-timeout-minutes> > <prefill>false</prefill> > <background-validation>false</background-validation> > <background-validation-millis>0</background-validation-millis> > <validate-on-match>true</validate-on-match> > <use-fast-fail>false</use-fast-fail> > <statistics-formatter>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter</statistics-formatter> > <isSameRM-override-value>false</isSameRM-override-value> > <allocation-retry>0</allocation-retry> > <allocation-retry-wait-millis>5000</allocation-retry-wait-millis> > <config-property type="java.lang.String" name="password">blahblahblah</config-property> > <config-property type="java.lang.String" name="template-name">connector-salesforce</config-property> > <config-property type="java.lang.String" name="username">mshirley.dev(a)redhat.com</config-property> > </no-tx-connection-factory> > </connection-factories> > We should see an additional property of the URL (probably should look like the below example) stating the URL value from the model. > <config-property type="java.lang.String" name="url">https://login.salesforce.com/services/Soap/u/25.0</config-property> > Same behavior occurs when creating a data source using the connection profile option instead of the model connection info. -- 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

13 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2012