> > I am using the C++ version ... so i didn't have example3 :( > anyways, i had the cppservice sample and the calculatorclient sample so i > converted the calc client to a cppservice client and it worked !
I am confused. Are you using a java client to test the cppservice sample? > I have more questions now :) > > 1. Where and when is the WSDL file used? > currently axis c++ can generate serverside skeletons and client stubs from a WSDL. Axis c++ uses java classes from axis java to accomplish this. How this process works is well documented in the axis c++ web pages (go to http://ws.apache.org/axis/cpp/documentation.html to find the documentation) > 2. What if i want to plug in my own transport class having a custom > protocol? should i write my own AxisTransport and Call classes for the > client side? what about the server side - there is no transport class for > the server. > the "Ax_soapstream" structure of "Packet.h" contains place holders for function pointers for transport functions (i.e. get_request_bytes and send_response_bytes in apache's case) and other transport info such as the protocol, the uri path of the request etc.. So your custom transport class should fill in the "Ax_soapstream" structure with appropriate functions pointers and other info and call "process_request" of Axis.cpp which will invoke the Axis c++ engine. > This framework should have been extensible. there should have been transport > base classes for the server and the client that the user can extend to > support his/her own version. (or we can do it and i don't know how to) > > 3. i want to automate the process of exposing soap functions. i have a set > of functions that i want to expose using soap. how do i go about it so that > minimum coding is required? (cut and paste is not considered coding) > There is a wrapper class generator (wcg) that can generate serverside wrappers from ".h" files which does function but it is not completed. Please let us know how you are getting on. sanjaya. > > Regards > Jaspreet >
