[
https://issues.apache.org/jira/browse/AXIS2C-1393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754016#action_12754016
]
Sebastien Bigot commented on AXIS2C-1393:
-----------------------------------------
The fact is that not everybody is using HTTP at transport layer, but, for
example, a legacy transport protocol which is not soap/web services aware.
In this case, if an endpoint accept both soap 1.1 and soap 1.2, the only way to
know is to check for the soap namespace declaration in the soap env.
Regards,
Sebastien
> axiom_soap_builder_identify_soap_version should accept parameter
> soap_version_uri_from_transport to be NULL
> -----------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1393
> URL: https://issues.apache.org/jira/browse/AXIS2C-1393
> Project: Axis2-C
> Issue Type: Bug
> Components: xml/soap
> Affects Versions: 1.6.0
> Reporter: Sebastien Bigot
>
> Looking at axiom_soap_builder_identify_soap_version in soap_builder.c,
> NULL soap_version_uri_from_transport means that we don't know the version of
> the soap message to be decoded prior the call to
> axiom_soap_builder_identify_soap_version.
> You should remove this
> AXIS2_PARAM_CHECK(env->error, soap_version_uri_from_transport,
> AXIS2_FAILURE); at line 873
> since later we check that the soap message should match the specified soap
> version ( line 914),
> and if it was not specified just set the soap version to the one decoded in
> the message (line 925, 940).
> Regards,
> Sebastien
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
