Hi Jaspreet,

First I thank you for your feedback on Axis C++.


> -----Original Message-----
> From: Jaspreet Singh [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 26, 2003 3:09 PM
> To: [EMAIL PROTECTED]
> Subject: RE: newbie query
>
>
> Hi
>
>
> > -----Original Message-----
> > From: Chandrasegaram Jeyakumaran [mailto:[EMAIL PROTECTED]
> > Sent: Friday, November 21, 2003 9:22 AM
>
> > Hi,
> > welcome to axis:)
> > You are using simpleaxisserver.
> > The easy way to start is try out the example3 of userguide.
> > You better follow userguide procedures to get it done.
> > Then you will find the way. Then you can write your own client.
>
> 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 have more questions now :)
>
> 1. Where and when is the WSDL file used?
        - To generate server side wrappers/skeletons in C/C++ using WSDL2Ws tool.
        - To generate client side stubs in C/C++ using WSDL2Ws tool.
        - To keep statically on the Axis C++ server to be sent to client on
request.
>
> 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.

At the moment Apache web server / IIS is intended to be the server side
transport
listener for Axis C++. But your own transport layer is possible (see simple
axis server coding).
But the API provided is yet intended for C transport layers. Not for C++
transport layers.
We are in the process of providing set of base classes for C++ transport
layers. So your
requirements/feedback in this area is very much appreciated.

So please let us know what kind of API or base classes you prefer.

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

One possibility is you start with a wsdl and generate the server side
wrappers and skeletons.
Then from within the skeleton's methods you can call corresponding methods
in your library.

Thanks,

Susantha.

>
>
> Regards
> Jaspreet
>

Reply via email to