July 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-509) Create Action to generate SalesForce function definitions

by John Doyle (JIRA)

Create Action to generate SalesForce function definitions --------------------------------------------------------- Key: TEIIDDES-509 URL: https://jira.jboss.org/browse/TEIIDDES-509 Project: Teiid Designer Issue Type: Task Components: Modeling Affects Versions: 7.1 Reporter: John Doyle Assignee: John Doyle Fix For: 7.1 The way UDFs are managed is changing in Teiid 7.1, and the way the SF functions are delivered has to change. An Eclipse Action needs to be created that puts the function definitions in a model project. The Action should be launchable directly by a user, an perhaps the importer could be smartened up to trigger the creation if the model contains multiselect column types. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-450) Implement the concept of a Translator into Teiid Designer

by Barry LaFond (JIRA)

Implement the concept of a Translator into Teiid Designer --------------------------------------------------------- Key: TEIIDDES-450 URL: https://jira.jboss.org/browse/TEIIDDES-450 Project: Teiid Designer Issue Type: Task Components: Editors, Teiid Integration, VDB & Execution, Views Affects Versions: 7.0 Reporter: Barry LaFond Fix For: 7.0 The Teiid Project has refactored their connection framework to better align their methodology with the AS container and the JON/JOPR community. As a result Designer will change it's connection framework from dealing with Connectors and Connector Types (ala MMX & Teiid Designer 6.0 thru 6.3). In it's place will be the concepts of Translators and Data Sources. The Translators hold the Teiid-specific properties and methods used at run-time to "translate" or transform/adjust any user query through the Teiid engine at run-time. This takes the place of actual Teiid-specific connector type properties. Data Sources are the portion of "Connecton Factories" that only deal with the actual data source connection properties (URL, Username, pwd, Driver class, etc.....) Designer needs to work on modifying the following: 1) Adjusting the "Teiid" View and underlying ExecutionAdmin (aka Connectors View) to display Translators and their instances instead of "Connector Types and their Connector instances". 2) Provide the hooks in the VDB Editor to manage both a "translator-name" and "connection-jndi-name" within each Relational Source Model's "source" element properties. 3) Provide the hooks for auto-binding models to Translators and JNDI Data Sources to simplify Preview Data functionality. 4) Provide the hooks for allowing users to "edit" or "override" any Translator property for each Relational Source model in a VDB. 5) Provide the hooks to search, select and re-use any set of Translator Properties that may exist in any VDB in the Designer workspace. -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-517) Unhandled Event Loop Exception when trying to edit a CHOICE node in an XML document model

by Paul Nittel (JIRA)

Unhandled Event Loop Exception when trying to edit a CHOICE node in an XML document model ----------------------------------------------------------------------------------------- Key: TEIIDDES-517 URL: https://jira.jboss.org/browse/TEIIDDES-517 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Reporter: Paul Nittel Attachments: AudioBooks_EventLooper.log, AudioBooks_MPS.zip I was testing the ability to create XML document models when I encountered this exception. I'll attach the exception (log file) and Model Project Set to assist in reproducing the issue. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-475) Ensure support for order by null ordering

by Steve Hawkins (JIRA)

Ensure support for order by null ordering ----------------------------------------- Key: TEIIDDES-475 URL: https://jira.jboss.org/browse/TEIIDDES-475 Project: Teiid Designer Issue Type: Quality Risk Affects Versions: 7.1 Reporter: Steve Hawkins See TEIID-715. support was added for order by nulls first/last. The display node logic needs to support this as well. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-460) Add HTTPBasic Support to Generated JBossWS-CXF War

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-460?page=com.atlassian.jira.plugin... ] Ted Jones commented on TEIIDDES-460: ------------------------------------ This should be done via the pass through authentication recently implemented in Teiid. > Add HTTPBasic Support to Generated JBossWS-CXF War > -------------------------------------------------- > > Key: TEIIDDES-460 > URL: https://jira.jboss.org/browse/TEIIDDES-460 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 6.2.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.1 > > > Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-460) Add HTTPBasic Support to Generated JBossWS-CXF War

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-460?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIIDDES-460: ------------------------------- Summary: Add HTTPBasic Support to Generated JBossWS-CXF War (was: Add HTTPBasic Suppor to Generated JBossWS-CXF War) > Add HTTPBasic Support to Generated JBossWS-CXF War > -------------------------------------------------- > > Key: TEIIDDES-460 > URL: https://jira.jboss.org/browse/TEIIDDES-460 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 6.2.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.1 > > > Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-460) Add HTTPBasic Suppor to Generated JBossWS-CXF War

by Ted Jones (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-460?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIIDDES-460: ------------------------------- Summary: Add HTTPBasic Suppor to Generated JBossWS-CXF War (was: Convert Legacy Web Services to CXF) > Add HTTPBasic Suppor to Generated JBossWS-CXF War > ------------------------------------------------- > > Key: TEIIDDES-460 > URL: https://jira.jboss.org/browse/TEIIDDES-460 > Project: Teiid Designer > Issue Type: Task > Affects Versions: 6.2.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 7.1 > > > Need to create a web services solution using CXF utilizing the web service models created in Designer. This is replacement functionality for the old MMSoap that used Axis2. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-298) ENHANCEMENT: soap requests should be modeled as procedures

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-298?page=com.atlassian.jira.plugin... ] Steve Hawkins resolved TEIIDDES-298. ------------------------------------ Resolution: Out of Date This change has already happened. There is a new xml integration issue to utilizing the new ws translator. > ENHANCEMENT: soap requests should be modeled as procedures > ---------------------------------------------------------- > > Key: TEIIDDES-298 > URL: https://jira.jboss.org/browse/TEIIDDES-298 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: Future > Reporter: Steven Hawkins > > Defect Tracker #23657: Currently SOAP request documents are imported as relational tables. This is not very clear from a user perspective. For simple requests, it would be better to import them as a procedure. This defect however cannot be worked until the ability to join on a procedure is implemented, which may happen in 5.0.3. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-301) Queries against web services that aren't running makes Designer inoperative (because of bug in Apache Axis)

by Steve Hawkins (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-301?page=com.atlassian.jira.plugin... ] Steve Hawkins resolved TEIIDDES-301. ------------------------------------ Resolution: Out of Date Execution in designer is no more, as is axis > Queries against web services that aren't running makes Designer inoperative (because of bug in Apache Axis) > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-301 > URL: https://jira.jboss.org/browse/TEIIDDES-301 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 7.1 > Environment: 5.5SP3 GA Designer on Linux > Reporter: Greg Haber > Attachments: axis-error.txt, wsTest1_20081211_1.zip > > > When putting together the new 5.5SP3 sales demo, I noticed that if I forgot to start the web service's container before I started Designer, and then tried to query against that web service, I would get an error message (as expected), but if I then started up the web service and retried my query in that same Designer instance, I would get a MetaMatrixException. I would need to shut down Designer and restart it to then be able to successfully query the web service. > I've attached the model project set for those who want to reproduce. The actual web service .aar file and instructions on using it are on JBEDSP-850. > For those trying to reproduce, note that I can only reproduce when the machine running the web service is up and reachable, but the container hosting the web service is not running (you need to get a java.net.ConnectException - if you get an UnknownHostException we do for some reason survive that). > I dug deeper into this and found that the initial exception I was seeing pop up in Designer was not in fact getting logged to the Designer message log. And on Designer's stdout, I saw the messages that I've attached as axis-error.txt. If you look at the exception you'll see that what is happening is that when we try to call printStackTrace on the exception, all sorts of Apache Axis stuff kicks in and the message logging fails. > I traced this issue back to com.metamatrix.connector.xml.soap.SOAPExecutor, where we have in the executeCall method the following: > } catch (AxisFault e) { > throw new ConnectorException(e); > I found that if I changed this to > } catch (AxisFault e) { > throw new ConnectorException(e.getMessage()); > to avoid passing back the AxisFault, then the error message about the java.net.ConnectException would be recorded in the Designer message log, and also that I could start up the web service and then retry my query in Designer successfully (without restarting Designer). > So it looks like we need to look at not only the XML-Relational Connector, but any other connectors that use Axis and throw AxisFault, to make sure we parse out the contents of the AxisFault and return those contents safely back when we throw ConnectorException. > I also thought about opening up a separate JIRA that the core MetaMatrix code should be able to handle when something went funny when we called printStackTrace on a ConnectorException. I ran this by one of the JBDS developers that sits near me, and he said that he thought that it was reasonable to assume that calling printStackTrace on any subclass of java.lang.Exception (such as AxisFault) should just work without having subclass-specific stuff available - so this isn't something we should need to protect against - that this is really poor design in Apache Axis, and since this is an exception to normal Exception behavior he recommended just protecting against this one subclass of Exception (AxisFault) like in my workaround above. -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-437) SalesForce provides two functions - Can we hide these, please?

by Barry LaFond (JIRA)

[ https://jira.jboss.org/browse/TEIIDDES-437?page=com.atlassian.jira.plugin... ] Barry LaFond resolved TEIIDDES-437. ----------------------------------- Resolution: Won't Fix TEIIDDES-509 will address this issue, along with the fact that UDF's are now first-class models and users will be able to inject the SF functions into ANY Function model. > SalesForce provides two functions - Can we hide these, please? > -------------------------------------------------------------- > > Key: TEIIDDES-437 > URL: https://jira.jboss.org/browse/TEIIDDES-437 > Project: Teiid Designer > Issue Type: Feature Request > Environment: All > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: Future > > > Upon opening the UDFs view two functions (includes and excludes) are visible. I'd like to propose these be, somehow, hidden from view. (The user can delete them, but I believe there is no simple means of getting them back.) > If nothing else, please use the Description to document what they are and warn to not delete them. -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2010