That's funny. I only got a message containing 'I'. Hm... :-S
Anyway, +1 for Thomas' answer.
Did it a bit different myself one time to prevent lots of
GetProcAddress blues: find out which calls/functionality you need,
write a 'wrapper' DLL offering just that functionality (using your own
interface)
Raymond Zhou wrote:
Hi there,
My goal is to modify axis2/c so that I can load the openSSL dlls at
runtime, this means that I will need the dlls to exist in the class
path only if my web service calls require SSL communication. The
AXIS2/c mainly calls the openSSL apis starting with SSL_, like
SS
Hi there,
I am using axis2/c to build a web service client, and axis2/c depends on
openSSL to support SSL. The way that axis2/c is currently built requires
resolving all the symbols at load time, which means that the openSSL dlls have
to present in the class path even if my web services does n
Hi there,
I