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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5 Final
• Fix Version/s: 1.6 Alpha
• Component/s: Basic Architecture, Client - Engine
• Assignee: Don Samisa Abeysinghe
• Reporter: Don Samisa Abeysinghe
• Created: 31/May/05 13:42
• Updated: 05/Apr/06 21:06
• Resolved: 25/Jul/05 13:25

Description

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.