axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nadir Amra <a...@us.ibm.com>
Subject Re: [Axis C++ 1.6b] Client and Server Engines - co-existing?
Date Mon, 20 Nov 2006 18:56:06 GMT
At this time you cannot run the client and server in same process - there 
is a jira issue (http://issues.apache.org/jira/browse/AXISCPP-771) to open 
this up.  Not sure when that will be done. 

As far as one way requests, not sure, but I do not think it is supported 
(http://issues.apache.org/jira/browse/AXISCPP-925), although there are 
plans to add support.

Nadir K. Amra


"Chinmoy Bhattacharjee" <chinmoy.bhattacharjee@gmail.com> wrote on 
11/20/2006 10:41:54 AM:

> Hi,
> We are using Axis C++ 1.6 b for our current project. We need to open
> up the server side implementation to receive and respond to web 
> services. The signalling is asynchronous - thus
> a) Client sends a Request
> b) We at the server side will send an acknowledgement 
> c) After some processing - the server side needs to push the 
> response of the pending operation as a HTTP post to an alternate URL.
> d) The client would send an acknowledgement of this response.
> Is it possible to have the client and server side implementation as 
> a single module ?
> Currently, we are trying to use the Call object to frame our 
> responses - but the initialization fails, since the initialization 
> has already been done as a server. Is it aboslutely mandatory that 
> the client side implementation must be a separate stand-alone 
> process that handles this scenario ? 
> Can the server modules not generate SOAP/HTTP requests to alternate 
> URLs and not merely respond to an ongoing session ?
> Thanks for any insight into this.
> Rgds.

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Mime
View raw message