[
https://issues.apache.org/jira/browse/TUSCANY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-3169:
--------------------------------
Fix Version/s: (was: Java-SCA-1.5.1)
Java-SCA-Next
> Illegal characters used for generated binding names
> ---------------------------------------------------
>
> Key: TUSCANY-3169
> URL: https://issues.apache.org/jira/browse/TUSCANY-3169
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.5.1
> Reporter: Simon Nash
> Assignee: Simon Nash
> Fix For: Java-SCA-Next
>
>
> The code in BindingConfigurationUtil to generate unique names for cloned
> bindings uses illegal characters "#" and "/" to separate the reference
> binding name, target component name, and service binding name. This causes
> validation errors when a node reads composite definitions that have been
> configured and written by the domain manager.
> To prevent validation errors, legal characters must be used. However, if
> legal characters are used, there can't be a 100% guarantee of name
> uniqueness, because of the possibility that there is a user-specified binding
> name using the same combination of legal characters. The chances of such a
> conflict can be greatly reduced by using unlikely combinations of legal
> characters.
> My proposed fix for these validation errors creates generated names using the
> legal characters "-" and "." instead of "#" and "/". To reduce the
> likelihood of conflicts, the current usage of "#" is replaced by a double
> dash ("--") and the current usage of "/" is replaced by a double period (
> ".."). It is extremely unlikely (though not impossible) that generated names
> containing these character combinations will conflict with user-specified
> names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
