[
https://issues.apache.org/jira/browse/TUSCANY-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583029#action_12583029
]
Simon Nash commented on TUSCANY-2164:
-------------------------------------
This behaviour is required by the OSOA SCA 1.0 specifications. However, it
causes problems, as you have pointed out, so I opened issue ASSEMBLY-27 in the
OASIS sca-assembly TC (see http://www.osoa.org/jira/browse/ASSEMBLY-27) with a
proposal to make the change that you have suggested. This proposal was
accepted and the issue is now resolved in OASIS with this change to the URI
construction rules.
We need to decide how the Tuscany implementation should handle differences like
this between the OSOA and OASIS specs. I'm starting a thread on the
tuscany-dev list to discuss this.
> binding.ws generate different endpoint URI according to the count services of
> implementation
> ---------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2164
> URL: https://issues.apache.org/jira/browse/TUSCANY-2164
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-1.2
> Reporter: wangfeng
> Priority: Minor
> Fix For: Java-SCA-Next
>
>
> A component service bound by web service,the generated webservice endpoint
> URI has the rule like invoking service.
> If the implementation only supply one service,the webservice endpoint URI is
> '/componentname'.
> If the implementation supply multiple services,the endpoint URI is
> '/componentname/servicename'.
> But I have a scenario like this:I have a implementation only included one
> service and put it to web service and the web service endpoint URL has been
> used by customer.If I add another service on this implementation,I must
> notify my customer the endpoint URL has been changed,but this is not needed.
> Thus I think if the implementaion has only one service,the endpoint URI
> should be '/componentname/servicename' too.
> If do this,only need to modify the class CompositeConfigurationBuilderImpl
> and set the flag 'includeBindingName' always true.If do so,some samples will
> be modified 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
