axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AXIS2C-136) Keeping listener_manager inside conf_ctx
Date Mon, 08 May 2006 02:18:21 GMT
     [ http://issues.apache.org/jira/browse/AXIS2C-136?page=all ]
     
Samisa Abeysinghe closed AXIS2C-136:
------------------------------------

    Resolution: Won't Fix

I did away with this in implemeting service client. If it happens that we need this in the
future, then we can do this; else no need to bother

> Keeping listener_manager inside conf_ctx
> ----------------------------------------
>
>          Key: AXIS2C-136
>          URL: http://issues.apache.org/jira/browse/AXIS2C-136
>      Project: Axis2-C
>         Type: New Feature

>   Components: core/context
>     Versions: 0.91
>  Environment: All
>     Reporter: Nabeel Yoosuf
>     Assignee: Samisa Abeysinghe
>      Fix For: 0.91

>
> With the service client API, user has the ability to creating a service_client passing
the conf_ctx. In this senario, when the service_client initializes the transport, it first
checks wether listener_manager is already created through conf_ctx (AXIS2_CONF_CTX_GET_LISTENER_MANAGER).
At present, conf_ctx does not create/keep track of listener_manager.

-- 
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