In order to process the request using axis engine within the container, you need to look at the following aspects.
[1] You need to have an initialized axis2 environment ( which encapsulates logging, memory allocation ect. ) [2] An initialized configuration context which will contain the axis2 configurations which will be used when processing the request. [3] Input stream and output stream which will be used by axis2/c in reading the request and sending back the response. If you look the axis2 module, you will find that all these setting are handled. Another requirement is to extract some of the request specific information and pass them axis2. Have a look into the axis2_apache2_worker_process_request function to see how most of these thing are handled. axis2_build_conf_ctx method is used to initialize axis2 configurations. and http transport utils methods contain most of the http specific processing methods. Regards Nandika On Fri, Sep 3, 2010 at 9:02 PM, Richard Offer <[email protected]>wrote: > > Hi, > > I¹m trying to get started with embedding Axis2/C service inside a > standalone > C++ server (not Apache). > > I¹ve gone through the various ³documents² that describe this (WSO2¹s WSF > for > PHP, Lighttpd module), but its none explain the differences between what > Axis needs and what the container needs. > > I have a char* containing the request from a client, I need to (obviously) > process it, have Axis call my business logic and then get a char * response > back into my code (my code is handling all the networking) > > > In trying to sort the wheat from the chaff:- > > What Axis calls are required once to initialize ? > > What Axis calls are required to parse a request string and process a > single message ? > > > Thanks, > > Richard. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com
