You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gopalakrishnan (JIRA)" <ji...@apache.org> on 2005/07/26 09:03:17 UTC
[jira] Created: (AXIS2-96) Call.isModuleEngaged(QName) will be useful
Call.isModuleEngaged(QName) will be useful
------------------------------------------
Key: AXIS2-96
URL: http://issues.apache.org/jira/browse/AXIS2-96
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: client-api
Versions: 0.9
Reporter: Gopalakrishnan
Currently Call has only a method to enagage a module (Call.engageModule(QName moduleName)), but no method to check if a module is already engaged. It will be useful to have a method Call.isEngaged(QName moduleName) as in AxisConfiguration.
Or call.engageModule() should not try to enagage the module if the module is already engaged.
--
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] Assigned: (AXIS2-96) Call.isModuleEngaged(QName) will be useful
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-96?page=all ]
Srinath Perera reassigned AXIS2-96:
-----------------------------------
Assign To: Srianth Perera
> Call.isModuleEngaged(QName) will be useful
> ------------------------------------------
>
> Key: AXIS2-96
> URL: http://issues.apache.org/jira/browse/AXIS2-96
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: client-api
> Versions: 0.9
> Reporter: Gopalakrishnan
> Assignee: Srianth Perera
>
> Currently Call has only a method to enagage a module (Call.engageModule(QName moduleName)), but no method to check if a module is already engaged. It will be useful to have a method Call.isEngaged(QName moduleName) as in AxisConfiguration.
> Or call.engageModule() should not try to enagage the module if the module is already engaged.
--
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: (AXIS2-96) Call.isModuleEngaged(QName) will be useful
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-96?page=all ]
Srinath Perera resolved AXIS2-96:
---------------------------------
Resolution: Fixed
I choose #2, engageing twice will not throw a exception
> Call.isModuleEngaged(QName) will be useful
> ------------------------------------------
>
> Key: AXIS2-96
> URL: http://issues.apache.org/jira/browse/AXIS2-96
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: client-api
> Versions: 0.9
> Reporter: Gopalakrishnan
> Assignee: Srianth Perera
>
> Currently Call has only a method to enagage a module (Call.engageModule(QName moduleName)), but no method to check if a module is already engaged. It will be useful to have a method Call.isEngaged(QName moduleName) as in AxisConfiguration.
> Or call.engageModule() should not try to enagage the module if the module is already engaged.
--
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