[jira] Resolved: (SYNAPSE-320) AbstractTransport(Listener|Sender) should use the "name" property of Transport(In|Out)Description

["Andreas Veithen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNAPSE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen resolved SYNAPSE-320.
-------------------------------------

    Resolution: Fixed

> AbstractTransport(Listener|Sender) should use the "name" property of Transport(In|Out)Description
> -------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-320
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-320
>             Project: Synapse
>          Issue Type: Bug
>            Reporter: Andreas Veithen
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.3
>
>
> AbstractTransportListener (AbstractTransportSender) defines its own attribute "transportName" (initialized with a constant value by subclasses) instead of using the name provided by TransportInDescription (TransportOutDescription). This may lead to inconsistencies in AbstractTransportListener#disableTransportForService, because this method compares transportName to the result of TransportInDescription#getName(). This will only work correctly if the transport names specified in axis2.xml are the same as the ones hardcoded into the transports themselves.
> AbstractTransportListener (AbstractTransportSender) should always use the "name" property of TransportInDescription (TransportOutDescription).
> See also: http://www.nabble.com/transportName-attribute-in-AbstractTransport%28Listener%7CSender%29-to17291043.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org