axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-3675) AxisBindings are created for each and every transport on services deployed
Date Mon, 31 Mar 2008 15:18:24 GMT

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

Davanum Srinivas resolved AXIS2-3675.
-------------------------------------

    Resolution: Fixed

Fixed in svn revision 643008

> AxisBindings are created for each and every transport on services deployed
> --------------------------------------------------------------------------
>
>                 Key: AXIS2-3675
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3675
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Keith Godwin Chapman
>            Assignee: Sanka Samaranayake
>            Priority: Blocker
>             Fix For: 1.4
>
>         Attachments: axis2-3675.patch
>
>
> AxisBindings are created for each and every transport on services deployed. That is a
SOAP11, SOAP12 and HTTPBinding is created for each transport. Hence if both http and https
are enabled there will be 6 bindings.  This is not necessary we could have three bindings
and both the http and https transport can share the same binding.
> Note. At the moment the HTTPBinding is not shown on the https endpoint. This should be
fixed too.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message