Are you saying you develop an agent which acts as a web service at one time but acts as web service client toward a next web service at another time?
Being new to Axis2 Java and C, I would start and work through some simple tutorials first. There are in my mind more tutorials available for Axis2/Java then for Axis2/C. Up to you, but start simple without Rampart first. framing the payload: Axis2/C has axutil and axiom too, an OM model can be serialized easy using either the Java or the C implementations of axiom. De-serializing an SOAP/XML Payload is more of a challenge. Again - Start simple, understand what you do and don't hope that tools will answer what you don't master yourself. My mind: Build Axis2/C using a good IDE like Visual Studio 2008 and greater, then watch, running / debugging the Axiom Tests and learn how to do it, how to work with Axiom in C/C++. It helps tremendously! BTW: --- what are your platforms --- is the client i.e. running on Windows using WCF 4.0 and servers agents run on ???? Or is it the opposite around? What is it, what will it be? Do you control al or only apart of the overall system? Two different platforms may make you have INTEROP ISSUES (quite a bunch of it) Best to be mastered (my own mind) using Java JAXWS/JAXB on the server side, and VS 2010 or greater on the Client Side. This results sooner in service providing objects AND using i.e. Visual Studio helps to generate the client side stubs, ready to use. TCP/IP Connections is OK, TCP/IP being the Truck! Because it carries HTTP and HTTP has XML which carries after all SOAP/XML and this TRAFFIC is best watched with the TCP Monitor. Or the SOAP UI or WireShark. Avoid doing the agent upfront; master your simple CL/SV situation first in any aspect, then add complexity by making your SV a Agent calling other services. It might well happen that you need to implement some a synchronicity, this is a challenge by itself i.e. call-backs é all. i.e. Addressing issues, Listeners and Transports. During the development keep any time an eye on securing issues using Rampart é all. STS i.e. Define early what needs to be encrypted, encrypting all using SSL / HTTPS might perhaps not be what you want. Maybe you need to encrypt only a few things, a few fields of your XML Payload, yes I know it's not standard; But it has the advantage that you don't need the burden of Rampart; JCE is start. Particular in mixed environments; i.e. Windows WCF Client and a secured Apache Axis2 Service Environment. AND be warned, when it comes to encryption, no protocol analyzer can be sniffed in-between, can help you. (at least not the ones I know) As you can see, there is many thing to master, so do not forget over all to have a good architecture for your overall system. When you design your physical system you need to have it as it brings in constraints, many constraints. Josef Von: Venkataragavan Vijayakumar [mailto:venkataragava...@gmail.com] Gesendet: Mittwoch, 13. Februar 2013 13:10 An: c-user@axis.apache.org Betreff: Need to Know how web services client /server will get the info to develop the payload to send to the opposite side. Hi All, I am very much new to Web services. I am working on the Feature where it should run a Webservices to contact the other services. So it should act either client or server on a particular time. So we planned to use axis2C for exchanging the payload and Rampant C to use for security. our setup is a single C server running and giving inputs to the AXIS2C engine for framing the payloads to send to the opposite side. So i want know, what kind of connection the we can made between C server and AXIS2C engine. We planned to make a TCP connection between them. Is it right way or any other way is there? Please do the needful. Thanks, Venkat
