[
https://issues.apache.org/jira/browse/TUSCANY-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-2626.
---------------------------------
Resolution: Fixed
To create any kind of sensible schema for this EndpointReference element we
need to put is in the target namespace. In that way we can create a schema that
can be used to validate the binding.ws element. So instead of this kind of thing
<service name="helloWorld" promote="HelloWorldService">
<interface.wsdl
interface="http://helloworld#wsdl.interface(HelloWorld)" />
<binding.ws>
<wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing";>
<wsa:Address>http://localhost:8085/myService</wsa:Address>
</EndpointReference>
</binding.ws>
</service>
You would use
<service name="helloWorld" promote="HelloWorldService">
<interface.wsdl
interface="http://helloworld#wsdl.interface(HelloWorld)" />
<binding.ws>
<EndpointReference>
<wsa:Address
xmlns:wsa="http://www.w3.org/2005/08/addressing";>http://localhost:8085/myService</wsa:Address>
</EndpointReference>
</binding.ws>
</service>
Now this new element doesn't conform to any specification schema and I've left
the wsa:EndpointReference approach active so we don't break anyone who is
already using it.
Looking at the OASIS spec they seem to be going this way but they have some
twists that don't look right to me (I'll take that up with them separately).
> Investigate why endpoint reference and wsdlLocation are not in the
> sca-binding-webservice.xsd schema file
> ---------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2626
> URL: https://issues.apache.org/jira/browse/TUSCANY-2626
> Project: Tuscany
> Issue Type: Task
> Components: Specification
> Reporter: Richard Mah
> Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
>
> Investigate why endpoint reference and wsdlLocation are not in the
> sca-binding-webservice.xsd schema file. If there is no good reason why they
> have been removed, insert it back into the sca-binding-webservice.xsd schema
> file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
