July 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1427) For Teiid Server Connection Info, jdbc connection password will not save when save button is selected

by Van Halbert (JIRA)

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1425) Refactor > Rename of abstraction layer model was partially reflected in transformation

by Paul Nittel (JIRA)

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-1397) Latest Designer Help is pointing to 7.6 community docs

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1397: ------------------------------------- Summary: Latest Designer Help is pointing to 7.6 community docs Key: TEIIDDES-1397 URL: https://issues.jboss.org/browse/TEIIDDES-1397 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.7.1 Environment: JBDS 5.0 Beta 3 with SOA-tooling Beta 2 Reporter: Paul Nittel Assignee: Van Halbert The link for the Help docs points to 1) community docs, and 2) they docs are version 7.6. For SOA-tooling, we need "Product" docs that reflect the 7.7 version of the Designer. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1388) Improve Flat File importer

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1388: -------------------------------------- Summary: Improve Flat File importer Key: TEIIDDES-1388 URL: https://issues.jboss.org/browse/TEIIDDES-1388 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.7, 7.7.1 Reporter: Barry LaFond The Flat File importer still lacks simplicity. Need to spend another cycle improving usability PAUL NITTEL wrote: I'm tinkering with this thing and have a few suggestions. (The problem with coming up with cool wizardly things is they spark other synapses thereby creating an endless flow of work.) The Create Teiid Flat File Connection action seems to be a mixture of building the data source connection and laying the groundwork for the transformation (like where are the column name and types). Moving this to the Create Source Model wizard might make it easier and flow better for the user. Rather than checkboxes that presume much about how flat file data may be constructed, how about allowing the user to tell you which lines are contain heading and type info (if any, of course)? In the case of my weird data file, there a comment in line 1, line 2 is blank, line 3 have column names and line 4 has types. Data starts in line 5. I realize my case is atypical, but might be worth consideration. ;-) -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1386) Cannot multi-select schema contents when building response procedure result set (Web Service as input)

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1386: ------------------------------------- Summary: Cannot multi-select schema contents when building response procedure result set (Web Service as input) Key: TEIIDDES-1386 URL: https://issues.jboss.org/browse/TEIIDDES-1386 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7.1 Reporter: Paul Nittel When modeling the response result set for an incoming Web Service, the user must select each attribute individually and click the Add button. Intuitively, I tried to multi-select the attributes, but that is not permitted. It should be. :-) Screenshot is attached. I used the Oorsprong FullCountryInfo operation which has several output attributes from which to choose. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1380) Create Editor wizard for existing SOAP Web Service view

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1380: -------------------------------------- Summary: Create Editor wizard for existing SOAP Web Service view Key: TEIIDDES-1380 URL: https://issues.jboss.org/browse/TEIIDDES-1380 Project: Teiid Designer Issue Type: Feature Request Components: Editors, Import/Export Reporter: Barry LaFond After Importing WSDL (http://www.oorsprong.org/websamples.countryinfo/CountryInfoService.wso?WSDL) I wanted to open these 3 procedures in an editor or wizard so I could tweak the content of the procedures I had already generated. Seems like it wouldn't be too bad to parse request, response and wrapper procedures and re-populate the ProcedureGenerator with RequestInfo, ResponseInfo and underlying column/attribute info based whether or not the WSDL source is still accessable via the Source file's connection profile -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)

by Paul Nittel (JIRA)

Refactored file is not reflected in VDB (no corresponding file in workspace) ---------------------------------------------------------------------------- Key: TEIIDDES-505 URL: https://jira.jboss.org/browse/TEIIDDES-505 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.0 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final Reporter: Paul Nittel I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace". I believe the VDB's contents should have been involved in the refactoring, just like other files. -- 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

13 years, 3 months

4
8
0 / 0

[JBoss JIRA] (TEIIDDES-1285) Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1285: ------------------------------------- Summary: Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys Key: TEIIDDES-1285 URL: https://issues.jboss.org/browse/TEIIDDES-1285 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Affects Versions: 7.7.1 Reporter: Van Halbert The creation of a "View" table is not really useful. This is because the "Base Table" represents the same thing and it also supports foreign keys. Something the "View" table doesn't support. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (TEIIDDES-1449) Getting Processing Exception - Could not parse query transformation when making a procedure execution

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1449?page=com.atlassian.jira.plu... ] Van Halbert closed TEIIDDES-1449. --------------------------------- Resolution: Rejected The problem was that when I updated JBDS and Designer to the latest (JBDS early access and latest Designer) there was no issue. Was able to perform this scenario with no issue. So rejecting this issue for the Designer folks. > Getting Processing Exception - Could not parse query transformation when making a procedure execution > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1449 > URL: https://issues.jboss.org/browse/TEIIDDES-1449 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Attachments: 0009_ReationalWSModeling.pdf, Financials_Linux.vdb, Financial_VDB.vdb, Lab-008.zip, Lab-008_w_error.zip > > > Trying to issue the command: > EXEC AllCustomerAccounts_WS.AllCustomerAccounts_customer.getcustomer('<?xml version="1.0" encoding="UTF-8"?><customer_Input xmlns="http://www.metamatrix.com/account_Input"><customerid>CST01010</customerid></customer_Input>') > and getting: > 14:01:29,316 WARN [PROCESSOR] Processing exception 'Could not parse query transformation for ALLCUSTOMERACCOUNTS_OUTPUT_VIEW.CUSTOMER_OUTPUTVIEW.MAPPINGCLASSES.CUSTOMER_OUTPUT_INSTANCE_1: null' for request SrNmZbySl22E.5. Exception type org.teiid.api.exception.query.QueryPlannerException thrown from org.teiid.query.parser.QueryParser.parseCommand(QueryParser.java:133). Enable more detailed logging to see the entire stacktrace. > It says its a warning, but no results are returned. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1449) Getting Processing Exception - Could not parse query transformation when making a procedure execution

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1449?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1449: ----------------------------------- Attachment: Financials_Linux.vdb > Getting Processing Exception - Could not parse query transformation when making a procedure execution > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1449 > URL: https://issues.jboss.org/browse/TEIIDDES-1449 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Barry LaFond > Priority: Critical > Attachments: 0009_ReationalWSModeling.pdf, Financials_Linux.vdb, Financial_VDB.vdb, Lab-008.zip, Lab-008_w_error.zip > > > Trying to issue the command: > EXEC AllCustomerAccounts_WS.AllCustomerAccounts_customer.getcustomer('<?xml version="1.0" encoding="UTF-8"?><customer_Input xmlns="http://www.metamatrix.com/account_Input"><customerid>CST01010</customerid></customer_Input>') > and getting: > 14:01:29,316 WARN [PROCESSOR] Processing exception 'Could not parse query transformation for ALLCUSTOMERACCOUNTS_OUTPUT_VIEW.CUSTOMER_OUTPUTVIEW.MAPPINGCLASSES.CUSTOMER_OUTPUT_INSTANCE_1: null' for request SrNmZbySl22E.5. Exception type org.teiid.api.exception.query.QueryPlannerException thrown from org.teiid.query.parser.QueryParser.parseCommand(QueryParser.java:133). Enable more detailed logging to see the entire stacktrace. > It says its a warning, but no results are returned. -- 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, 3 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 2012