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/02/02 04:28:18 UTC

[jira] Commented: (AXISCPP-351) Dynamic creation of Service Endpoints

     [ http://issues.apache.org/jira/browse/AXISCPP-351?page=comments#action_58476 ]
     
Samisa Abeysinghe commented on AXISCPP-351:
-------------------------------------------

This is another issue where we need transport visibility at Handler level. It seems related to what Fred wants in AXISCPP-397.

I think we got to discuss the Handler design in detail and come to a conclusion on this.

> Dynamic creation of Service Endpoints
> -------------------------------------
>
>          Key: AXISCPP-351
>          URL: http://issues.apache.org/jira/browse/AXISCPP-351
>      Project: Axis-C++
>         Type: New Feature
>     Reporter: rinsad ahmed

>
>  At the moment Axis C++ client engine supports, static Endpoints only,where the client already aware of its service endpoint. But with WS-Addressing, it is required to set the endpoint dynamically. 
>    But in this case, the endpoint is set by a Handler. But according to the current implementation of Axis C++, the handlers are invoked by the client engine after the connection is established between the client and the server.So there is no point of changing the endpoint. Is it possible to incorporate this requirement into the current implementation? 

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira