January 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-795) A Few Teiid Designer MANIFEST.MF Files Still Have Bundle Versions Associated With Their Dependencies

by Dan Florian (JIRA)

A Few Teiid Designer MANIFEST.MF Files Still Have Bundle Versions Associated With Their Dependencies ---------------------------------------------------------------------------------------------------- Key: TEIIDDES-795 URL: https://issues.jboss.org/browse/TEIIDDES-795 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.1 Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.2 The following plugins still have bundle versions associated with their dependencies: org.jdom, org.teiid.designer.ddl.importer, org.teiid.designer.ddl.importer.ui, org.teiid.designer.modelgenerator.salesforce.ui, and org.teiid.designer.transformation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-794) Build Warnings About JDK Version Should Be Suppressed

by Dan Florian (JIRA)

Build Warnings About JDK Version Should Be Suppressed ----------------------------------------------------- Key: TEIIDDES-794 URL: https://issues.jboss.org/browse/TEIIDDES-794 Project: Teiid Designer Issue Type: Task Reporter: Dan Florian Assignee: Dan Florian Fix For: 7.2 The build log contains warnings the the JDK version used by the pom is being overridden by the manifest. Adding code to the pom.xml files can suppress this warning. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-214) Validate that the jdbc4olap driver works as expected in Designer and Teiid.

by John Doyle (JIRA)

Validate that the jdbc4olap driver works as expected in Designer and Teiid. --------------------------------------------------------------------------- Key: TEIIDDES-214 URL: https://jira.jboss.org/jira/browse/TEIIDDES-214 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: John Doyle Assignee: John Doyle http://www.jdbc4olap.org/ provides a type 4 JDBC driver for OLAP sources that support XMLA. Supporting this driver will provide access to many OLAP sources (SAP, Microsoft, Mondrian) Currently the only OLAP source that we have tested with is SAP BW via the OLAP BAPI interface. Those BAPIs are procedural and require the model designer to create extensive procedural logic in their models. jdbc4olap should enable a user to access OLAP data via standard JDBC semantics. -- 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

14 years, 10 months

3
8
0 / 0

[JBoss JIRA] Resolved: (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 resolved TEIIDDES-781. --------------------------------- Resolution: Done New extensions have been added to the new model wizard to create these 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, 7.2 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1, 7.2 > > 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.patch, 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: -------------------------------- Fix Version/s: 7.2 Affects Version/s: 7.2 > 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, 7.2 > Reporter: John Doyle > Assignee: John Doyle > Priority: Critical > Fix For: 7.1.1, 7.2 > > 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.patch, 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: Teiiddes-781.patch Patch modified from Barry's original > 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.patch, 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] Resolved: (TEIIDDES-780) CLONE - There's no way to create a Teiid WS connection from JBDS/Teiid Designer without a WSDL.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-780?page=com.atlassian.jira.plug... ] John Doyle resolved TEIIDDES-780. --------------------------------- Resolution: Done implemented > 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, 7.2 > > Attachments: TEIIDDES-780.jd.patch > > > 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] Created: (TEIIDDES-793) Update LEGAL.txt and feature related files for 2011 copyright info

by Barry LaFond (JIRA)

Update LEGAL.txt and feature related files for 2011 copyright info ------------------------------------------------------------------ Key: TEIIDDES-793 URL: https://issues.jboss.org/browse/TEIIDDES-793 Project: Teiid Designer Issue Type: Bug Components: Build Affects Versions: 7.1.1 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 7.1.1 Various exposed copyrights in Teiid Designer need updating to 2011 This is related to JBIDE-8191 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
1
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 John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-780?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-780: -------------------------------- Attachment: TEIIDDES-780.jd.patch proposed patch > 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, 7.2 > > Attachments: TEIIDDES-780.jd.patch > > > 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-780) CLONE - There's no way to create a Teiid WS connection from JBDS/Teiid Designer without a WSDL.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-780?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-780: -------------------------------- Fix Version/s: 7.2 > 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, 7.2 > > Attachments: TEIIDDES-780.jd.patch > > > 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2011