axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Whitlock (JIRA)" <axis-c-...@ws.apache.org>
Subject [jira] Commented: (AXISCPP-497) Problems with Stub::setTransportProperty
Date Thu, 03 Mar 2005 13:26:48 GMT
     [ http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60114 ]
     
Mark Whitlock commented on AXISCPP-497:
---------------------------------------

Hi Samisa,
Thank you for comments. I understand the need to have a setTransportProperty(char*, char*)
now. 

On Call there is only a setTransportProperty(AXIS_TRANSPORT_INFORMATION_TYPE, char*) and not
a setTransportProperty(char*, char*). This means that applications that use the Call interface
and not generated stubs will not be able to set arbitrary transport properties. Do we need
AXIS_TRANSPORT_INFORMATION_TYPE?

I propose removing AXIS_TRANSPORT_INFORMATION_TYPE from the external API and having Call::setTransportProperty(char*,
char*).

Also Call::setTransportProperty checks that the soapaction is enclosed in double quotes, whereas
Stub::setTransportProperty does not. Call::setTransportProperty issues m_pTransport->getLastChannelError()
whereas Stub::setTransportProperty does not. This is inconsistent. Surely the two methods
should behave the same. So either I copy the Call code into Stub or I call Call:setTransportProperty
from Stub::setTransportProperty. What do you think?

You may be interested in AXISCPP-499 which discusses a related issue.

> Problems with Stub::setTransportProperty
> ----------------------------------------
>
>          Key: AXISCPP-497
>          URL: http://issues.apache.org/jira/browse/AXISCPP-497
>      Project: Axis-C++
>         Type: Bug
>     Reporter: Mark Whitlock
>     Assignee: Mark Whitlock

>
> The exception processing in Call::setTransportProperty is not in Stub::setTransportProperty.
Stub::setTransportProperty should just call Call::setTransportProperty instead of SOAPTransport::setTransportProperty.
Also the message is new[]'ed in Call but delete'd in AxisGenException. This will fail on Linux,
where it should be delete[]'ed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message