[teiid-issues] [JBoss JIRA] (TEIID-1714) Allow WS calls to set a timeout value

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708767#comment-12708767 ] 

Steven Hawkins commented on TEIID-1714:
---------------------------------------

We should not break backwards compatibility.  A resolving change would be needed if another parameter is to be added.  Adding another procedure also seems undesirable.  At the very least the timeout should be a configuration property though, as you cannot expect users to know/embed their timeouts in SQL.  Also note that having the WSDL based ws translator allows for CXF timeouts to be specified at a port level rather than at a service level - which minimizes the need to have an explicit timeout parameter.

invokeHTTP does not use any timeout now.  We'd have to add handling to enforce a timeout.
                
> Allow WS calls to set a timeout value
> -------------------------------------
>
>                 Key: TEIID-1714
>                 URL: https://issues.jboss.org/browse/TEIID-1714
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: XML Connector
>    Affects Versions: 8.0
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>             Fix For: 8.1
>
>
> With the upgrade beyond CXF 2.3, there is a straightforward way to set timeouts: https://issues.apache.org/jira/browse/CXF-2991
> The translator (via a new invoke method) and/or the connection factory should have the ability to specify a request timeout.  It is quite cumbersome to use CXF configuration for this and is a common need.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira