Axis2/C acts not just as a soap library but a service container. The term repository mean the directory where axis2/c is. Under this repository directory, you will have the following folders, modules, services, lib , bin and doc. The modules directory contains axis2 modules which can be used to add QOS functionality to your soap processing. WS Security , WS RM etc are implemented as modules. Services are dlls which implement the business logic. They are placed in the services directory inside a folder named after the service name. An xml file named axis2.xml is located in the repository directory defining the configuration of axis2. Each service and module have a configuration file named module.xml and service.xml.
As for your requirement of using axis2 to handle the soap request and make your applicaton the service can be done. However you will need to understand how axis2c works inorder to do that since you will have to write a message receiver which will connect your application and axis2 and pickup the http request the set it to axis2/c engine. You can remove services directory and axis2 will still function properly. You can have a look at how we did it to implement WSF/PHP extension here. https://wso2.org/repos/wso2/trunk/wsf/php Regards Nandika On Tue, Nov 11, 2008 at 1:03 AM, Yanroy <[EMAIL PROTECTED]> wrote: > > Thank you very much for your swift reply. I had already seen the > documentation listed at that first link you provided. It doesn't seem to > have much in the way of API docs. The only such docs I can find are the > doxygen-generated ones, which don't have a high-level overview. Also, as I > mentioned, I think my use case is a bit strange since it's never even > mentioned anywhere. > > That distribution that you linked to is what I'm trying to build. I > followed all the build instructions that came with it and it fails due to > dependency problems, as I mentioned in my previous email. In my attempt to > get rid of the Apache httpd dependency (I don't want to build anything > httpd > related), I edited the build scripts to not build any of modules like > rampart, sandesha, neethi, etc. I also had to change the build target from > dist to dist_as_lib to get rid of it trying to build the httpd module > itself. I know that won't produce any of the samples, but I was hoping to > get some DLLs that I could use in my own test application (because the > binary distribution ones give me memory corruption errors). I may have > been > confusing -- there are several different problems I'm having. I keep > switching my way of attacking Axis because I keep hitting dead ends. A > short list of my problems: > > 1) can I even use Axis2/C the way I intend? See my last email for a > detailed description, but the short version is "can I integrate it directly > into my application without having any server modules, service DLLs or any > other external communcations or interfaces?" > > 2) I can't run the example standalone server from the binary distribution > because of the error in my previous email. > > 3) I can't run a small test application (based on the echo sample client) > that I built against the binary distribution libraries because it gives me > memory corruption errors (it free()'s some pointer twice, I think). > > 4) I can't build from source because of dependency problems. I was trying > to build from source because I thought having my own bins might fix > problems > 2 and 3. If I can get the binary distribution working, then I will not > need > to build from source. > > I've been posting on this ML because AFAICT, all my problems are in the > Axis2/C part of the build script. I think it's failing before it even gets > to the C++ specific parts that WSO2 added. I looking into posting on their > ML, but they've had 2 posts in the past year according to the archive I > looked at, so I didn't think I'd find much help there. > > Thank you very much for your help so far, > > Ryan > > > nandika jayawardana-2 wrote: > > > > You can find documentation on Axis2/C here. > > *http://ws.apache.org/axis2/c/docs/index.html* > > > > In addition to that there are number of articles published here as well. > > http://wso2.org/taxonomy/term/254 > > > > Ok back to your problem. > > > > I assume your problem comes with building this distribution > > http://wso2.org/downloads/wsf/cpp > > > > We usually used vc2005. However, you can actually build the code with vc6 > > as > > well. You might want to make a minor modifications to the makefiles for > > that.You do not need to specify a build target to the build.bat if you > > have > > downloaded WSF/CPP distribution.Edit the configure.in file located in > the > > outermost directory and just run the build.bat. dist_as_lib is used only > > for > > building library dlls. It will not build the services or clients and will > > not be of use to you. If you are directly using the makefile located in > > build\win32 directory , Always use dist target as it builds the usable > > binary distribution with all headers copied to proper locations. > > > > Hope this helps. Since you are interested in cpp, you can get more help > > by > > posting to [EMAIL PROTECTED] > > > > Regards > > Nandika > > > > > > -- > View this message in context: > http://www.nabble.com/building-Axis2-C-on-windows-tp20387114p20426494.html > Sent from the Axis - C++ - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com
