[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2329:
----------------------------------------
See the comment by SteveH in TEIID-3107 about the return type of the "invokeHTTP" method, the same seems to be true for "invoke" procedure call too. The documentation on these methods can be found at https://docs.jboss.org/author/display/TEIID/Web+Services+Translator
One thing we would like to know is, in which version "contentType" attribute added? Is that a released version? Based on the answer, Teiid can provide a compensated code in 8.9 version, but in Teiid 8.8 it would fail.
> 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
>
> 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)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2329:
-----------------------------------
Assignee: (was: Steven Hawkins)
> 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
>
> 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)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Ramesh Reddy moved TEIID-3108 to TEIIDDES-2329:
-----------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-2329 (was: TEIID-3108)
Affects Version/s: (was: 8.8)
Component/s: Import/Export
(was: Misc. Connectors)
Fix Version/s: (was: 8.9)
> 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: Steven Hawkins
>
> 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)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2328) Rest Importer: Show the response document
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2328?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2328:
-----------------------------------
Attachment: showdocument.png
> Rest Importer: Show the response document
> -----------------------------------------
>
> Key: TEIIDDES-2328
> URL: https://issues.jboss.org/browse/TEIIDDES-2328
> Project: Teiid Designer
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Reporter: Ramesh Reddy
> Attachments: showdocument.png
>
>
> I used the one of the REST APIs from [http://nycpulse.herokuapp.com/api]
> For this JIRA, I was using [http://mtaapi.herokuapp.com/times?hour=10&minute=25]
> The importer says the response document is bad, see the attached screen shot. The repose is like
> {code}
> {
> "result": [
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:00",
> "id": "242N",
> "lat": "40.662742",
> "lon": "-73.95085",
> "name": "Sterling St"
> },
> {
> "arrival": "10:25:30",
> "id": "A09S",
> "lat": "40.840719",
> "lon": "-73.939561",
> "name": "168 St"
> }
> }
> {code}
> So, that looks like valid JSON to me. So, two part question
> 1) Why importer complaining? fix any errors as such
> 2) The gist of this JIRA, instead of showing link to some response file, that I have no way to check the contents if wanted, show the response document itself. This pattern is not new, CSV importer and XML importer do show the document to user, which IMO is much more valuable and gives visual indication right away what they are working with.
> I even say this needs to be done File based importer too (create JIRA if you decide to work on this separately)
>
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2328) Rest Importer: Show the response document
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2328:
--------------------------------------
Summary: Rest Importer: Show the response document
Key: TEIIDDES-2328
URL: https://issues.jboss.org/browse/TEIIDDES-2328
Project: Teiid Designer
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Import/Export
Reporter: Ramesh Reddy
I used the one of the REST APIs from [http://nycpulse.herokuapp.com/api]
For this JIRA, I was using [http://mtaapi.herokuapp.com/times?hour=10&minute=25]
The importer says the response document is bad, see the attached screen shot. The repose is like
{code}
{
"result": [
{
"arrival": "10:25:00",
"id": "242N",
"lat": "40.662742",
"lon": "-73.95085",
"name": "Sterling St"
},
{
"arrival": "10:25:00",
"id": "242N",
"lat": "40.662742",
"lon": "-73.95085",
"name": "Sterling St"
},
{
"arrival": "10:25:30",
"id": "A09S",
"lat": "40.840719",
"lon": "-73.939561",
"name": "168 St"
}
}
{code}
So, that looks like valid JSON to me. So, two part question
1) Why importer complaining? fix any errors as such
2) The gist of this JIRA, instead of showing link to some response file, that I have no way to check the contents if wanted, show the response document itself. This pattern is not new, CSV importer and XML importer do show the document to user, which IMO is much more valuable and gives visual indication right away what they are working with.
I even say this needs to be done File based importer too (create JIRA if you decide to work on this separately)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2326:
-----------------------------------
Description:
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.
was:
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.
For ex: I tried with [http://dev.kwayisi.org/apis/gse/equities] REST with JSON
and after restart I attached
> 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
> 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)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2326?page=com.atlassian.jira.plu... ]
Ramesh Reddy updated TEIIDDES-2326:
-----------------------------------
Attachment: nomodel.png
> 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
> 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.
> For ex: I tried with [http://dev.kwayisi.org/apis/gse/equities] REST with JSON
> and after restart I attached
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2326) REST/SOAP importers - Re use of the connection profile after restart
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2326:
--------------------------------------
Summary: 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
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.
For ex: I tried with [http://dev.kwayisi.org/apis/gse/equities] REST with JSON
and after restart I attached
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2325) REST Importer: Inline edit the parameters
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2325:
--------------------------------------
Summary: 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
Reporter: Ramesh Reddy
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)
10 years, 4 months