You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2005/01/31 16:11:17 UTC
[jira] Created: (AXISCPP-397) Better support for client-side handlers
Better support for client-side handlers
---------------------------------------
Key: AXISCPP-397
URL: http://issues.apache.org/jira/browse/AXISCPP-397
Project: Axis-C++
Type: Bug
Environment: n/a
Reporter: Fred Preston
Need to have control over HTTP headers to control sessions.
* Set / reset the "Connection: keep-alive" header
* Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-397) Better support for client-side handlers
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=history ]
John Hawkins updated AXISCPP-397:
---------------------------------
type: Improvement (was: Bug)
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Type: Improvement
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-397) Better support for client-side handlers
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=comments#action_58468 ]
Samisa Abeysinghe commented on AXISCPP-397:
-------------------------------------------
Fred!
Could you please explain a bit more why we need to access trasport headers in a handler.
What advantages would we have over doing the same through Stub API?
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Type: Improvement
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-397) Better support for client-side handlers
Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=comments#action_58350 ]
Roshan Weerasuriya commented on AXISCPP-397:
--------------------------------------------
A handler can do this directly if it can get access to the Transport object, because the SoapTransport API has set/get methods to do this.
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Type: Bug
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-397) Better support for client-side handlers
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=history ]
Samisa Abeysinghe updated AXISCPP-397:
--------------------------------------
Component: Handlers
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Type: Improvement
> Components: Handlers
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-397) Better support for client-side
handlers
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=all ]
nadir amra closed AXISCPP-397.
------------------------------
Resolution: Won't Fix
Reopen only if getTransportProperty() and setTransportProperty() methods on a stub is for some reason not sufficient. If reopened, please explain.
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Issue Type: Improvement
> Components: Client - Handlers
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-397) Better support for client-side handlers
Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-397?page=comments#action_58351 ]
Roshan Weerasuriya commented on AXISCPP-397:
--------------------------------------------
A Handler can do this directly if it can get access to the Transport object, because the SoapTransport API has set/get methods to do this.
> Better support for client-side handlers
> ---------------------------------------
>
> Key: AXISCPP-397
> URL: http://issues.apache.org/jira/browse/AXISCPP-397
> Project: Axis-C++
> Type: Bug
> Environment: n/a
> Reporter: Fred Preston
>
> Need to have control over HTTP headers to control sessions.
> * Set / reset the "Connection: keep-alive" header
> * Write arbitrary HTTP headers in the HTTP message for SOAP requests and be able to read returned HTTP headers in the HTTP message for the SOAP response.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira