axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "shijith lal (JIRA)" <>
Subject [jira] Commented: (AXISCPP-313) Axis Transport Project
Date Wed, 08 Dec 2004 12:24:09 GMT
     [ ]
shijith lal commented on AXISCPP-313:

 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.

> Axis Transport Project
> ----------------------
>          Key: AXISCPP-313
>          URL:
>      Project: Axis-C++
>         Type: Bug
>   Components: Transport (Client)
>     Versions: 1.3 Final
>  Environment: Windows XP with Apache Tomcat 3.3 and Apache SOAP at server side
>     Reporter: shijith lal
>     Priority: Blocker

>   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
>  2. In SecureChannel class SecureChannel::readNonBlocking function is not yet implemented.
This blocks the SSL usage.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message