January 2011 - teiid-designer-issues

[JBoss JIRA] Updated: (TEIIDDES-781) CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-781?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-781: ---------------------------------- Attachment: TEIIDDES_781_org.teiid.designer.relational.ui.patch Contains a patch to add a Web Service New Model contribution for generating procedures for Web Service translator. > CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-781 > URL: https://issues.jboss.org/browse/TEIIDDES-781 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1 > > Attachments: flat-file-procedures-option.png, flat_file_procedures.png, ForBarryTeiiddes-781.zip, generate-flat-file-procedures-page.png, invoke.jpg, invokeHttp.jpg, TEIIDDES_781_org.teiid.designer.relational.ui.patch > > > If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector. > If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user. > For the File Translator we should define getFiles, getTextFiles, and saveFile. > For the WS Translator we should define invoke and invokeHttp. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-781) CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-781?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-781: -------------------------------- Attachment: invoke.jpg invokeHttp.jpg Screen shots of manually created ws procedures. > CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-781 > URL: https://issues.jboss.org/browse/TEIIDDES-781 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1 > > Attachments: flat-file-procedures-option.png, flat_file_procedures.png, ForBarryTeiiddes-781.zip, generate-flat-file-procedures-page.png, invoke.jpg, invokeHttp.jpg > > > If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector. > If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user. > For the File Translator we should define getFiles, getTextFiles, and saveFile. > For the WS Translator we should define invoke and invokeHttp. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-781) CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-781?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-781: --------------------------------------- Added code for the fist half (File translator) in the new model wizard contribution. (See Screen Pics) > CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-781 > URL: https://issues.jboss.org/browse/TEIIDDES-781 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1 > > Attachments: flat-file-procedures-option.png, flat_file_procedures.png, ForBarryTeiiddes-781.zip, generate-flat-file-procedures-page.png > > > If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector. > If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user. > For the File Translator we should define getFiles, getTextFiles, and saveFile. > For the WS Translator we should define invoke and invokeHttp. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-779) CLONE - There's no way to create a Teiid File connection from JBDS/Teiid Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-779?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-779. ----------------------------------- Resolution: Done Added logic to extract/manage flat file connection profile info (Parent Folder) in a Model as a new connection profile and pass on to Teiid in Create Data Source. Now allows Preview data and Execute VDB. > CLONE - There's no way to create a Teiid File connection from JBDS/Teiid Designer > --------------------------------------------------------------------------------- > > Key: TEIIDDES-779 > URL: https://issues.jboss.org/browse/TEIIDDES-779 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.1.1 > > > There's no way to create a Teiid File connection from JBDS/Teiid Designer. There's also no way to do it from the console. A user has to create the ds.xml manually and deploy it. > One possible resolution for this issue is to use the DTP File connection profile (it it has the required information) and link it into the Teiid Designer's ability to create the datasource in Teiid. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-792) add support for in/out out return params

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-792?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDDES-792: ----------------------------------------- I also removed the restriction that a virtual procedure must return a result set. > add support for in/out out return params > ---------------------------------------- > > Key: TEIIDDES-792 > URL: https://issues.jboss.org/browse/TEIIDDES-792 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > In/out, out, return parameters are supported by Teiid virtual procedures - not just result sets - as of 7.4. Designer should remove validation restrictions preventing the usage of these parameters and update the external metadata logic to add out/return parameters as valid symbols. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-779) CLONE - There's no way to create a Teiid File connection from JBDS/Teiid Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-779?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-779: ---------------------------------- Fix Version/s: 7.1.1 (was: 7.3) Priority: Critical (was: Major) > CLONE - There's no way to create a Teiid File connection from JBDS/Teiid Designer > --------------------------------------------------------------------------------- > > Key: TEIIDDES-779 > URL: https://issues.jboss.org/browse/TEIIDDES-779 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 7.1.1 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 7.1.1 > > > There's no way to create a Teiid File connection from JBDS/Teiid Designer. There's also no way to do it from the console. A user has to create the ds.xml manually and deploy it. > One possible resolution for this issue is to use the DTP File connection profile (it it has the required information) and link it into the Teiid Designer's ability to create the datasource in Teiid. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-780) CLONE - There's no way to create a Teiid WS connection from JBDS/Teiid Designer without a WSDL.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-780?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-780: ---------------------------------- Fix Version/s: 7.1.1 Priority: Critical (was: Major) > CLONE - There's no way to create a Teiid WS connection from JBDS/Teiid Designer without a WSDL. > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-780 > URL: https://issues.jboss.org/browse/TEIIDDES-780 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1 > > > There's no way to create a Teiid WS connection from JBDS/Teiid Designer without a WSDL. This means that a user cannot develop and test a VDB that invokes a non-SOAP HTTP service from the tooling without creating the ds.xml manually and deploy it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-781) CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-781?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-781: ---------------------------------- Fix Version/s: 7.1.1 Priority: Critical (was: Major) > CLONE - Teiid Designer should create models for the WS translator invoke and invokeHttp procedures and the File translator getFiles procedure. > ----------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-781 > URL: https://issues.jboss.org/browse/TEIIDDES-781 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.1.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1 > > Attachments: flat-file-procedures-option.png, flat_file_procedures.png, ForBarryTeiiddes-781.zip, generate-flat-file-procedures-page.png > > > If a user models a SOAP service defined by a WSDL using the WSDL to Relational Model importer, the importer creates the invoke() physical procedure for the user. The execute procedure is required to execute the translator/connector. > If the service is not defined by a WSDL (ie. REST service, XML RPC service, ...), or is File based, then the user currently has to go through the error prone process of creating the physical models that define the procedures for the File and WS translators. Since the declaration of these procedures is static and known, JBDS/Teiid Designer should create the models for the user. > For the File Translator we should define getFiles, getTextFiles, and saveFile. > For the WS Translator we should define invoke and invokeHttp. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-792) add support for in/out out return params

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-792?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIIDDES-792: ------------------------------------ Affects Version/s: (was: 6.0.0) Description: In/out, out, return parameters are supported by Teiid virtual procedures - not just result sets - as of 7.4. Designer should remove validation restrictions preventing the usage of these parameters and update the external metadata logic to add out/return parameters as valid symbols. (was: In/out, out, return parameters should be supported in Teiid defined procedures - not just result sets. The logic for handling them would be similar to what exists for managing the update_count variable. The Designer would also need to remove validation restrictions preventing the usage of these parameters.) Complexity: Low (was: Medium) > add support for in/out out return params > ---------------------------------------- > > Key: TEIIDDES-792 > URL: https://issues.jboss.org/browse/TEIIDDES-792 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > In/out, out, return parameters are supported by Teiid virtual procedures - not just result sets - as of 7.4. Designer should remove validation restrictions preventing the usage of these parameters and update the external metadata logic to add out/return parameters as valid symbols. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-792) add support for in/out out return params

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-792?page=com.atlassian.jira.plug... ] Steven Hawkins moved TEIID-1449 to TEIIDDES-792: ------------------------------------------------ Project: Teiid Designer (was: Teiid) Key: TEIIDDES-792 (was: TEIID-1449) Affects Version/s: 6.0.0 (was: 6.0.0) Fix Version/s: (was: 7.4) Component/s: Modeling (was: Query Engine) > add support for in/out out return params > ---------------------------------------- > > Key: TEIIDDES-792 > URL: https://issues.jboss.org/browse/TEIIDDES-792 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > > In/out, out, return parameters should be supported in Teiid defined procedures - not just result sets. The logic for handling them would be similar to what exists for managing the update_count variable. The Designer would also need to remove validation restrictions preventing the usage of these parameters. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 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 January 2011