[jira] [Updated] (TUSCANY-4007) Mutliple delegations for binding.sca
[ https://issues.apache.org/jira/browse/TUSCANY-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-4007: Attachment: delegation-v2.patch Updates to the original patch. Putting here for backup. Am going off this approach a little as it's got a bit more complicated. Mutliple delegations for binding.sca Key: TUSCANY-4007 URL: https://issues.apache.org/jira/browse/TUSCANY-4007 Project: Tuscany Issue Type: Improvement Components: SCA Java Runtime Affects Versions: Java-SCA-2.x Environment: All Reporter: Simon Laws Fix For: Java-SCA-2.0 Attachments: delegation-v2.patch, delegation.patch I've come across a situation where I'd like to support multiple remote delegations for a single binding.sca instance. This came up because I was looking at a situation where I wanted to support reliable and non-reliable comms at the same time so thought I would experiment with delegating to different underlying binding implementations. Currently the code doesn't allow you to do that as it assumes a local delegation and a single remote delegation are represented by the single binding.sca instance take from the component model. I've attached a patch with a fix to make this work. It creates a new endpoint for each required delegation. Am going to raise on the dev list before committing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-4005) Ambiguous wire target is not reported as an error
[ https://issues.apache.org/jira/browse/TUSCANY-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4005: --- Assignee: Simon Laws Ambiguous wire target is not reported as an error - Key: TUSCANY-4005 URL: https://issues.apache.org/jira/browse/TUSCANY-4005 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Assignee: Simon Laws Priority: Minor I have a component reference with a target that includes only a component name. reference name=xyz target=MultipleServiceComponent/ The target component has multiple services. According to the following text in the assembly specification, the target component must have one and only one service with a compatible interface. 1844 If service-name is not present, the target component MUST have one and only 1845 one service with an interface that is a compatible superset of the wire source's 1845 interface and satisifies the policy requirements of the wire source, and the SCA 1846 runtime MUST use this service for the wire. [ASM60048] This implies to me that if there are multiple services with compatible interfaces, I should get an error. This does not happen. Instead the first match is taken. It's unclear to me why there needs to be only one match. If there are multiple matches that satisfy the interface and the policy requirements, it seems like using any of the matches is just as good. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
