July 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2447: ----------------------------------- Fix Version/s: 9.0.3 > Failed to import SalesForce Metadata > ------------------------------------ > > Key: TEIIDDES-2447 > URL: https://issues.jboss.org/browse/TEIIDDES-2447 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.2, 9.0.3 > > Attachments: sfddl (1).ddl > > > Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong. > 1) The DDL should be successfully imported > 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-987) Add ability to edit/generate Create Virtual Procedure SQL statements for RestEasy XML, File and Web Service Translator procedures

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-987?page=com.atlassian.jira.plug... ] Ted Jones resolved TEIIDDES-987. -------------------------------- Resolution: Out of Date This functionality has been implemented. > Add ability to edit/generate Create Virtual Procedure SQL statements for RestEasy XML, File and Web Service Translator procedures > --------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-987 > URL: https://issues.jboss.org/browse/TEIIDDES-987 > Project: Teiid Designer > Issue Type: Enhancement > Components: Editors, Transformations > Affects Versions: 7.4 > Reporter: Barry LaFond > Fix For: Future > > > Designer includes "Generate xxxx procedures" options in the New Model Wizard. > Also have a RestEasy use-case that requires getXXXX virtual procedures that contain SQL like: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT XMLELEMENT(NAME parts, XMLAGG(XMLELEMENT(NAME part, XMLFOREST(VirtualParts_Supplier.PARTS.PART_ID, VirtualParts_Supplier.PARTS.PART_NAME, VirtualParts_Supplier.PARTS.PART_COLOR, VirtualParts_Supplier.PARTS.PART_WEIGHT)))) AS result FROM VirtualParts_Supplier.PARTS WHERE VirtualParts_Supplier.getParts.partId_in = VirtualParts_Supplier.PARTS.PART_ID; > END > Would be nice to have a framework where "wizards" can be accessed to create/edit the content of this SQL if the basic structure is a Set Query (SELECT * FROM XXX)for these specific use-cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1809: -------------------------------- Fix Version/s: 9.0.3 > WAR File (REST, SOAP) Creation usability enhancements > ------------------------------------------------------ > > Key: TEIIDDES-1809 > URL: https://issues.jboss.org/browse/TEIIDDES-1809 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 9.0.3 > > > I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation > 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create. > 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide. > 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-1809: ----------------------------------- Assignee: Ted Jones > WAR File (REST, SOAP) Creation usability enhancements > ------------------------------------------------------ > > Key: TEIIDDES-1809 > URL: https://issues.jboss.org/browse/TEIIDDES-1809 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Ramesh Reddy > Assignee: Ted Jones > > I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation > 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create. > 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide. > 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2469) [Usability] Problem importing SOAP web service via URL

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2469?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2469: -------------------------------- Issue Type: Quality Risk (was: Bug) > [Usability] Problem importing SOAP web service via URL > ------------------------------------------------------ > > Key: TEIIDDES-2469 > URL: https://issues.jboss.org/browse/TEIIDDES-2469 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 9.0 > Reporter: Van Halbert > > Conversation: > [09:44] <jmarley> vhalbert: do you have a document for import soap web service via url > [09:45] <jmarley> we are getting hung up on creating relational model > [09:45] <jmarley> vhalbert: nevermind, > [09:46] <jmarley> vhalbert: there was an error saying we didn't have a column defined, but it was for a different procedure than the one that was selected, which and we didn't know we needed to select the other procedure and assumed it was issue with current procedure we were working with > [09:47] <vhalbert> jmarley, hm > [09:47] <vhalbert> jmarley, so designer was processing something that wasn't selected > [09:48] <jmarley> vhalbert: yes, and didn't give an indication as to which procedure it was referring to -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2567) REST war returns source column names instead of the virtual table column names

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2567?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2567: ----------------------------------- Assignee: Ted Jones > REST war returns source column names instead of the virtual table column names > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2567 > URL: https://issues.jboss.org/browse/TEIIDDES-2567 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.1 > Reporter: Marc Shirley > Assignee: Ted Jones > Fix For: 9.2, 9.0.3 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2567) REST war returns source column names instead of the virtual table column names

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2567?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2567: -------------------------------- Fix Version/s: 9.2 9.0.3 > REST war returns source column names instead of the virtual table column names > ------------------------------------------------------------------------------ > > Key: TEIIDDES-2567 > URL: https://issues.jboss.org/browse/TEIIDDES-2567 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 9.0.1 > Reporter: Marc Shirley > Assignee: Ted Jones > Fix For: 9.2, 9.0.3 > > > When querying a REST procedure built off of a virtual table, it returns the physical source column name instead of the virtual table column name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-603) Change Generated CXF WAR and REST WAR to create Dynamic Web Projects

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-603?page=com.atlassian.jira.plug... ] Ted Jones resolved TEIIDDES-603. -------------------------------- Resolution: Won't Fix > Change Generated CXF WAR and REST WAR to create Dynamic Web Projects > --------------------------------------------------------------------- > > Key: TEIIDDES-603 > URL: https://issues.jboss.org/browse/TEIIDDES-603 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: Komodo > > > When creating a CXF or REST 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 was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2394) Add UI support for TEXTTABLE Custom Line Separator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2394?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2394: ------------------------------------------ If neither is specified the default of new line would be assumed for the row delimiter. > Add UI support for TEXTTABLE Custom Line Separator > --------------------------------------------------- > > Key: TEIIDDES-2394 > URL: https://issues.jboss.org/browse/TEIIDDES-2394 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Teiid Integration > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: FileConnector, TEXTTABLE > Fix For: 9.2 > > > Add UI support for TEXTTABLE capability to support a Custom Line Separator . See https://docs.jboss.org/author/display/TEIID/FROM+Clause with the ROW DELIMITER char option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2394) Add UI support for TEXTTABLE Custom Line Separator

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2394?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2394: ---------------------------------------- So the File importer's *Edit Delimiter Character" button will need to change to "Configure Delimiters" and include the original Edit Delimiter Character radio buttons and add the NO ROW DELIMITER/ROW DELIMITER char options [~shawkins] Can you clarify that since *NO ROW DELIMITER* flag is optional it also means something different if neither *NO ROW DELIMITER/ROW DELIMITER* is present? > Add UI support for TEXTTABLE Custom Line Separator > --------------------------------------------------- > > Key: TEIIDDES-2394 > URL: https://issues.jboss.org/browse/TEIIDDES-2394 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export, Teiid Integration > Reporter: Shiveeta Mattoo > Assignee: Barry LaFond > Labels: FileConnector, TEXTTABLE > Fix For: 9.2 > > > Add UI support for TEXTTABLE capability to support a Custom Line Separator . See https://docs.jboss.org/author/display/TEIID/FROM+Clause with the ROW DELIMITER char option. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015