[jira] Updated: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations

["Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]

Samisa Abeysinghe updated AXISCPP-664:
--------------------------------------

    Attachment: callSeq_openDropped.JPG

I removed the openConnection method from Call class and moved the login that was inside this method to Call class constructor. This was reasonable as the logic inside this method was basically initializing the transport.
callSeq_openDropped.JPG figure shows the new sequence after this change.

The next step is to look into elemenating the deletion of current client engine on every method invocation.

> 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