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 "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2005/05/31 06:43:51 UTC
[jira] Created: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
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
Reporter: Samisa Abeysinghe
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
[jira] Commented: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Resolved: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]
Samisa Abeysinghe resolved AXISCPP-664:
---------------------------------------
Resolution: Fixed
I did many changes in liene with this issue. All these changes seem to be stabilized over the pasr month or so. The problems revealed through testing and reported by other users has been fixed. Hence we can call this issue to be resolved.
> 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
[jira] Closed: (AXISCPP-664) Improve Call::initialize() method and
make sure one off activities are not executed for multiple invocations
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]
Fred Preston closed AXISCPP-664:
--------------------------------
> 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
[jira] Updated: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]
Samisa Abeysinghe updated AXISCPP-664:
--------------------------------------
Assign To: Samisa Abeysinghe
Version: 1.5 Final
Component: Basic Architecture
Client - Engine
Fix Version: 1.6 Alpha
> 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
>
> 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
[jira] Updated: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "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
[jira] Updated: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=all ]
Samisa Abeysinghe updated AXISCPP-664:
--------------------------------------
Attachment: callSeq.JPG
callSeq.jpg shows the current sequence of method calls triggered by Call::initialize()
> 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
>
> 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
[jira] Commented: (AXISCPP-664) Improve Call::initialize() method and make sure one off activities are not executed for multiple invocations
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-664?page=comments#action_12313558 ]
Samisa Abeysinghe commented on AXISCPP-664:
-------------------------------------------
I successfully moved AxisEngine::initilize() from Call::initialize() to Call constructor.
The tests are successful.
> 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