This content has been marked as final.
Show 4 replies
-
1. Re: Problem with two different components having services with the same name
kcbabo Jan 9, 2014 9:29 AM (in response to tadayosi)At this point, we require component service names to be unique across the application. This can likely be relaxed in 2.0 if we qualify component service names internally with the component name (similar to what we do with references). SWITCHYARD-1525 would cover that.
-
2. Re: Problem with two different components having services with the same name
tadayosi Jan 9, 2014 8:01 PM (in response to kcbabo)Hi Keith,
Thank you for the prompt confirmation. So, once SWITCHYARD-1525 is implemented in the future, can we use the @ServiceOperation annotation something like the following?
@ServiceOperation("Bar/AwesomeService.greateMethod")
private Invoker greateMethod;
Best regards,
Tadayoshi
-
3. Re: Problem with two different components having services with the same name
kcbabo Jan 14, 2014 8:21 AM (in response to tadayosi)1 of 1 people found this helpfulYes, something like that would be required. Would you mind adding that as a comment in the JIRA?
thanks,
keith
-
4. Re: Problem with two different components having services with the same name
tadayosi Jan 14, 2014 9:25 PM (in response to kcbabo)Sure. Thanks, Keith!