Hi Sam, As I added before to this discussion, I believe that you could use either of the two options,
1. Adding mod_axis2 2. Adding mod_existing (+ mod_axis2 features) The manual caters for 1, which actually targets users, developers like you seeking for option 2, will rather have to browse through the header files, to understand the inner workings of Axis2/C. However, as I said before, I believe that if you could add the functionality in mod_axis2.c (just this single file), into your module, and add to it the other files in src/core/transport/http/server/apache2, which are support methods and API extensions, you can improve your module to include Axis2/C support. Thus, you will require just only your module being deployed in your apache server instance, instead of having two. Regards, Senaka > > On Sun, 2008-02-24 at 23:48 -0500, Sam Carleton wrote: >> On Sun, Feb 24, 2008 at 11:32 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> >> wrote: >> > >> > Ok, let me present my perspective. You can use Axis2/C's httpd module >> > and implement a service, that will wrap your current C/C++ business >> > logic and the .NET application can communicate with the service >> hosted >> > with Axis2/C's httpd module. >> >> So do you have any tips on exactly how I might go about doing this? > Please follow [1]. > >> First off, it is the nature of Axis2/C such that the service is linked >> into the same module as Axis2/C or is the service normally a library >> that Axis2/C loads up via configuration? > Yes service is a library Axis2/C loads up through the configuration. > Follow [2] on how to deploy a service in Axis2/C. > > > [1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#mod_axis2 > > [2] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#quick_start > > >> I get the impression it is >> the former, if that is the case, how might I go about blending the >> Axis2/C module with my existing module? >> >> Sam >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
