September 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2329: ----------------------------------- Assignee: Ted Jones > WS translator Procedure definition defined in correctly > ------------------------------------------------------- > > Key: TEIIDDES-2329 > URL: https://issues.jboss.org/browse/TEIIDDES-2329 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Ted Jones > > TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation. > {code} > java.lang.NullPointerException > at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138) > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65] > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2323) Rest Importer should encode the both "default" and provided values before submitting query

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2323?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2323: -------------------------------- Fix Version/s: 8.6 > Rest Importer should encode the both "default" and provided values before submitting query > ------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2323 > URL: https://issues.jboss.org/browse/TEIIDDES-2323 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 8.6 > > Attachments: postoffice.png > > > For example take a web api examples here look at [https://www.usps.com/business/web-tools-apis/address-information.htm] > Here one is required to submit the XML as query parameter, XML needs to be encoded before the query is sent -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2323) Rest Importer should encode the both "default" and provided values before submitting query

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2323?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2323: -------------------------------- Affects Version/s: 8.6 > Rest Importer should encode the both "default" and provided values before submitting query > ------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2323 > URL: https://issues.jboss.org/browse/TEIIDDES-2323 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Attachments: postoffice.png > > > For example take a web api examples here look at [https://www.usps.com/business/web-tools-apis/address-information.htm] > Here one is required to submit the XML as query parameter, XML needs to be encoded before the query is sent -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2324: -------------------------------- Fix Version/s: 8.6 > Rest Importer: Use invokeHTTP procedure with Named Parameters > ------------------------------------------------------------- > > Key: TEIIDDES-2324 > URL: https://issues.jboss.org/browse/TEIIDDES-2324 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 8.6 > > > When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like > invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true') > this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2323) Rest Importer should encode the both "default" and provided values before submitting query

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2323?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2323: ----------------------------------- Assignee: Ted Jones > Rest Importer should encode the both "default" and provided values before submitting query > ------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2323 > URL: https://issues.jboss.org/browse/TEIIDDES-2323 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Attachments: postoffice.png > > > For example take a web api examples here look at [https://www.usps.com/business/web-tools-apis/address-information.htm] > Here one is required to submit the XML as query parameter, XML needs to be encoded before the query is sent -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2324: -------------------------------- Affects Version/s: 8.6 > Rest Importer: Use invokeHTTP procedure with Named Parameters > ------------------------------------------------------------- > > Key: TEIIDDES-2324 > URL: https://issues.jboss.org/browse/TEIIDDES-2324 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > > When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like > invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true') > this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2324) Rest Importer: Use invokeHTTP procedure with Named Parameters

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2324?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2324: ----------------------------------- Assignee: Ted Jones > Rest Importer: Use invokeHTTP procedure with Named Parameters > ------------------------------------------------------------- > > Key: TEIIDDES-2324 > URL: https://issues.jboss.org/browse/TEIIDDES-2324 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Fix For: 8.6 > > > When generating the transformation for rest procedure, in the invokeHTTP procedure, use named procedures. aka like > invokeHTTP (action=>'GET', endpoint=>qp, stream=>'true') > this way one can avoid putting the null parametes, as well as if there are additional parameters added to invokeHTTP as did in TEIID-3016 the generated procedure will be error free for next versions. I did see one error here with Teiid 8.9 Alpha, which is logged as TEIID-3107 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2325) REST Importer: Inline edit the parameters

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2325?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-2325: -------------------------------- Affects Version/s: 8.6 > REST Importer: Inline edit the parameters > ----------------------------------------- > > Key: TEIIDDES-2325 > URL: https://issues.jboss.org/browse/TEIIDDES-2325 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Attachments: popup.png > > > When using REST importer (actually goes for any dialog), when user is trying to add parameter it is done as POP-UP, that is 4th layer counting original layout. I believe this level can be removed by inline editing on the table in layer 3, see the attached picture. > I guess I draw line at 4th level :) hehe > Also, currently in layer 3 the user is given editing choices in the table but once the focus is gone the value is restored to previous value (this is a bug) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2325) REST Importer: Inline edit the parameters

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2325?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2325: ----------------------------------- Assignee: Ted Jones > REST Importer: Inline edit the parameters > ----------------------------------------- > > Key: TEIIDDES-2325 > URL: https://issues.jboss.org/browse/TEIIDDES-2325 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Ted Jones > Attachments: popup.png > > > When using REST importer (actually goes for any dialog), when user is trying to add parameter it is done as POP-UP, that is 4th layer counting original layout. I believe this level can be removed by inline editing on the table in layer 3, see the attached picture. > I guess I draw line at 4th level :) hehe > Also, currently in layer 3 the user is given editing choices in the table but once the focus is gone the value is restored to previous value (this is a bug) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ] Ted Jones reassigned TEIIDDES-2326: ----------------------------------- Assignee: Ted Jones > REST/SOAP importers - Re use of the connection profile after restart > -------------------------------------------------------------------- > > Key: TEIIDDES-2326 > URL: https://issues.jboss.org/browse/TEIIDDES-2326 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Ted Jones > Attachments: nomodel.png > > > Often times, as user I start the import of WSDL based or REST (with new one, or old with file and URL selection) service and go through the wizard, something does not work right. So, I typically remove the models generated, and then try the import process again. However, next time when I select the same connection profile I created before, I very seldom get same results. If I restarted the Designer for any reason, the previously created connection profile for sure does not work. > It seems to me that, designer stores a temp XML/JSON file from where it starts processing, during the restart that gets deleted and import process instead of sending another request for the results document it fails with arbitrary error. There is no way to recover form it. IMO, REST and SOAP needs to be treated differently from XML File type sources and issue the query to get response document, not store it anywhere. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 September 2014