Currently, this is not supported. When loading modules and services, axis2 uses the same function axis2_get_instance which is implemented by all modules and services. Therefore an static linking will fail for the moment. However, we have it on the project road map to implement static linking support.
Regards Nandika On Wed, Jan 6, 2010 at 1:47 PM, Thomas Baier <thomas.ba...@gmx.net> wrote: > Samisa Abeysinghe schrieb: > > > > > > On Wed, Jan 6, 2010 at 12:55 PM, Thomas Baier <thomas.ba...@gmx.net > > <mailto:thomas.ba...@gmx.net>> wrote: > > > > Samisa, > > > > any ideas or hints on how to do this? > > > > > > If the default binary pack like solution is acceptable, then the build > > scripts does that for you. > > Maybe I don't understand correctly. The default build scripts build a > shared library (or DLL on Windows) and this shared library is then > loaded by axis2_http_server. I would like to have a solution _without_ > axis2_http_server and a DLL, or more exactly with a single executable > containing both axis2_http_server _and_ the service DLL. As far as I > have seen, this is not what the build scripts do, or is there an option > I should use? > > Best, > Thomas > -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com