Hi
Fred, thanks for the reply. That would work, except the destructor for the
secure channel object (derived from Channel) is empty too. So when the channel
object is destroyed in the transport destructor, the secure channel destructor
gets called but doesn't do anything. So closeSSLChannel() doesn't get called
when the transport object disappears. Neither does destroySSLChannelObject(),
which is a shame because it would give my SSL library a chance to clean up
after itself. In fact I'm not sure the SSL library gets unloaded at all.
Or again, maybe I'm missing something.
Bruce.
PS: I'm looking at 1.5 now, but for this release I'm stuck with
1.4.
-----Original Message-----
From: Fred Preston [mailto:[EMAIL PROTECTED]
Sent: June 16, 2005 6:08 AM
To: Apache AXIS C User List
Subject: Re: Closing a secure channel
From: Fred Preston [mailto:[EMAIL PROTECTED]
Sent: June 16, 2005 6:08 AM
To: Apache AXIS C User List
Subject: Re: Closing a secure channel
Hi Bruce,
You should now be using AXIS3 transport. The reason why the method is empty is because the socket was not closed until you deleted the web service which in turn would call the destructor on the transport object, closing and then deleting the channel object.
Regards,
Fred Preston.
Bruce McHaffie <[EMAIL PROTECTED]> 06/15/2005 08:30 PM
Please respond to "Apache AXIS C User List"
To: "'Apache AXIS C User List'" <[email protected]>
cc:
Subject: Closing a secure channel
A 1.4 question for you: in axis2/SecureChannel.cpp the close() method doesn't do anything. Shouldn't it at least close the connection that is opened in the open() method? For instance:void SecureChannel::close()
{
m_pSSLChannel->closeSSLChannel()
}Or am I missing something here?
Thanks,
Bruce.
