axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Perera (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-96) Call.isModuleEngaged(QName) will be useful
Date Wed, 27 Jul 2005 05:35:19 GMT
     [ 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


Mime
View raw message