On Wed, Jan 6, 2010 at 12:55 PM, Thomas Baier 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.
Samisa...
Best,
Thomas
Samisa Abeysinghe schrieb:
I think this
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.
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
I think this is possible. This is what happens with samples in binary
distribution I guess.
Samisa...
On Tue, Dec 29, 2009 at 3:03 AM, Thomas Baier thomas.ba...@gmx.net wrote:
Hi,
is there a (simple and easy) way to create a single self-contained
executable including both the web server and
Samisa,
any ideas or hints on how to do this?
Best,
Thomas
Samisa Abeysinghe schrieb:
I think this is possible. This is what happens with samples in binary
distribution I guess.
Samisa...
Hi,
is there a (simple and easy) way to create a single self-contained
executable including both the web server and the web service (and all
necessary configuration)?
The idea is not to use axis2_http_server and a shared library for the
web service and a few configuration files, but to have
