[
http://issues.apache.org/jira/browse/AXISCPP-497?page=comments#action_60118 ]
Samisa Abeysinghe commented on AXISCPP-497:
-------------------------------------------
Hi Mark,
Yes I agree - having two APIs here is a maintanance headache.
While I would love to have
setTransportProperty(AXIS_TRANSPORT_INFORMATION_TYPE, char*) removed there will
be other side effects as well.
As an example we set secure and non secure channels using
AXIS_TRANSPORT_INFORMATION_TYPE. Hence it is not only HTTP headers that we set
with AXIS_TRANSPORT_INFORMATION_TYPE version while setTransportProperty(char*,
char*) sets mostly HTTP header like settings.
Hence if we are to drop AXIS_TRANSPORT_INFORMATION_TYPE, we would have to
consult Fred on the possible implications on the channel setting.
On the inconsistancy factor, yes I do agree with you. The reason why
Call::setTransportProperty issues m_pTransport->getLastChannelError() is
because it is used for setting channel as I mentioned earlier. If we are
setting a HTTP header (using char*, char* method), there is no chance we would
get such an error, as we would not deal with the channel in that case. So
practically, looks to me as if these two methods are doing differernt things.
> 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
