You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Keith Godwin Chapman (JIRA)" <ji...@apache.org> on 2008/03/28 10:08:25 UTC
[jira] Created: (AXIS2-3675) AxisBindings are created for each and
every transport on services deployed
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: Critical
Fix For: 1.4
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
[jira] Resolved: (AXIS2-3675) AxisBindings are created for each and
every transport on services deployed
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (AXIS2-3675) AxisBindings are created for each
and every transport on services deployed
Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583324#action_12583324 ]
Sanka Samaranayake commented on AXIS2-3675:
-------------------------------------------
I suggest the about fix for this issue.
Thanks,
Sanka
> 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
[jira] Commented: (AXIS2-3675) AxisBindings are created for each
and every transport on services deployed
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583265#action_12583265 ]
Davanum Srinivas commented on AXIS2-3675:
-----------------------------------------
Sanka,
Please submit a patch ASAP!
thanks,
dims
> 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
>
>
> 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
[jira] Updated: (AXIS2-3675) AxisBindings are created for each and
every transport on services deployed
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Godwin Chapman updated AXIS2-3675:
----------------------------------------
Priority: Blocker (was: Critical)
As a result of this generated WSDLs are not valid. Hence increasing priority
> 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
>
>
> 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
[jira] Updated: (AXIS2-3675) AxisBindings are created for each and
every transport on services deployed
Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanka Samaranayake updated AXIS2-3675:
--------------------------------------
Attachment: axis2-3675.patch
> 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