Issue Details (XML | Word | Printable)

Key: AXISCPP-313
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: shijith lal
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Axis-C++

Axis Transport Project

Created: 08/Dec/04 05:59 AM   Updated: 01/Feb/05 10:51 PM
Return to search
Component/s: Transport (Client)
Affects Version/s: 1.3 Final
Fix Version/s: None

Time Tracking:
Not Specified

Environment: Windows XP with Apache Tomcat 3.3 and Apache SOAP at server side

Resolution Date: 11/Jan/05 10:42 PM


 Description  « Hide
 
  I am working with Axis Client 1.3 (C++ ) version. I am using the secure socket layer support. For this, in AxisTransport project i found two errors.
 
 1. This project consist of two classes one is SecureChannel nad other is Channel. Channel is the base class. Both consist of a function (operator overloaded) <<. But the signoture of both functions are different. This make ivalid call to base class function while using SSL.

 2. In SecureChannel class SecureChannel::readNonBlocking function is not yet implemented. This blocks the SSL usage.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Samisa Abeysinghe added a comment - 08/Dec/04 08:45 AM
There was no secure channel in 1.3.

This came with 1.4.

Please try with 1.4

shijith lal added a comment - 08/Dec/04 12:22 PM
 download the 1.4 alpha vesion source. But it does not consist of
AxisTransport project files. I think it is same as the 1.3 final
release. I got the AxisTransport project from 1.3 final. It consist of
secure channel functionality ( See SecureChannel class in 1.3 final
path src/transport/axis/SecureChannel.cpp)

I make some changes in 1.3 version. Please see the code difference i made

1. In channelclass change the functio signature
old signiture was
"const Channel & Channel::operator << (cont char *msg) ". I change this to
"const Channel & Channel::operator << (const std::string &msg) " .
Because in SecureChannel class the signature is same as the second
one. For proper working of virtual functio both signiture must be same

2. I add "const Channel &
SecureChannel::readNonBlocking( std::string & msg, bool
bBlockingRequired)" function in SecureChannel class. Because if there
is no function and one use the securechannel class instead of channel
class, it will call the base class function (channel class). It try to
read from normal channel and got only encrypted data.

Please look at these.

Fred Preston added a comment - 11/Jan/05 10:42 PM
There was no SSL implementation in 1.3
The comments suggest ways of changing the code to enable SSL, but if you want SSL you will need to move to v1.4.

John Hawkins added a comment - 01/Feb/05 10:51 PM
SSL is only supported in 1.4