[
https://issues.apache.org/jira/browse/TUSCANY-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated TUSCANY-2248:
-----------------------------------------
Attachment: TUSCANY-2248-2.patch
TUSCANY-2248-2.patch:
Since "soap.1_1 and soap.1_2" are now qualified intents of "soap", even though
it seems logical that
<sca:bindingType type="sca:binding.ws" mayProvide="soap soap11 soap12"
alwaysProvides=""/>
can be replaced with
<sca:bindingType type="sca:binding.ws" mayProvide="soap" alwaysProvides=""/>
I am hitting some warning messages like the following:
May 13, 2008 3:13:06 PM
org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem
WARNING: Policy related exception:
org.apache.tuscany.sca.assembly.builder.impl.PolicyConfigurationException: The
following are unfulfilled intents for binding in service - ep2
Unfulfilled Intents = [{http://www.osoa.org/xmlns/sca/1.0}soap.1_1]
> SOAP intents not being honored
> --------------------------------
>
> Key: TUSCANY-2248
> URL: https://issues.apache.org/jira/browse/TUSCANY-2248
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-1.0
> Reporter: Lou Amodeo
> Fix For: Java-SCA-Next
>
> Attachments: TUSCANY-2248-2.patch, TUSCANY-2248.patch
>
>
> Hi, It looks like there are a couple issues with the handling of the SOAP
> version intents with the Web Services binding. The first one is the literal
> used to identify the SOAP version and the second is the alrogitym used to
> apply the SOAP intent.
> 1) Tuscany is currently using soap. soap11 and soap12 for the literals to
> identify the soap version. I believe these should be soap, soap.1_1,
> soap.1_2 according to section 2.3.1 of WS Binding specification.
> 2) During WSDL generation the soap.1_1 intent is not being honored. It
> appears that the algorithm to determine which soap version to use is
> incorrect. I believe it should be as follows:
> I think this is the algorithym:
> no requires= specifying a soap version or requires="soap"
> - generate soap.1_1 and soap.1_2 port and binding
>
> requires = "soap.1_1"
>
> - generate soap.1_1 port and binding only
> requires = "soap.1_.2"
> - generate soap.1_2. port and binding only
> I also see that an http port/binding is generated by Axis2 by default.
> Since he intetns are based on soap version I would
> think the http:address should not be generated.
> <wsdl:port name="HelloWorldServiceHttpEndpoint"
> binding="ns:HelloWorldServiceHttpBinding">
> <http:address
> location="http://localhost:8080/axis2/services/HelloWorldService"/>
> </wsdl:port
>
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
