axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Date Thu, 30 Jun 2005 08:49:57 GMT
    [ http://issues.apache.org/jira/browse/AXISCPP-664?page=comments#action_12314743 ] 

Samisa Abeysinghe commented on AXISCPP-664:
-------------------------------------------

The changes done in relation to this issue seems to be quite stable by now.

There were couple of problems reported which were related to changes here. Both of them are
solved now.

> Improve Call::initialize() method and make sure one off activities are not executed for
multiple invocations
> ------------------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-664
>          URL: http://issues.apache.org/jira/browse/AXISCPP-664
>      Project: Axis-C++
>         Type: Improvement
>   Components: Basic Architecture, Client - Engine
>     Versions: 1.5 Final
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.6 Alpha
>  Attachments: callSeq.JPG, callSeq_openDropped.JPG
>
> There are some complications in the Call::initialize() method. Some of the things that
we re doing here could be moved to the constructure.
> To start with, I am looking into the things htat we are doing in the Call::openConnection()
method. We are not opening the connection here at all, but rather do some initing of the transport
which could be done in the Call constructor.

-- 
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


Mime
View raw message