[
https://issues.apache.org/jira/browse/TUSCANY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733421#action_12733421
]
Simon Nash commented on TUSCANY-3169:
-------------------------------------
The following output shows the errors produced when loading
payment-java-contribution from the travel sample:
[java] 21-Jul-2009 01:41:37
org.apache.tuscany.sca.node.launcher.NodeLauncher main
[java] INFO: Apache Tuscany SCA Node is starting...
[java] 21-Jul-2009 01:41:38
org.apache.tuscany.sca.node.launcher.NodeLauncher main
[java] INFO: SCA Node configuration:
http://localhost:9990/node-config/PaymentNode
[java] 21-Jul-2009 01:41:38 org.apache.tuscany.sca.node.impl.NodeImpl
<init>
[java] INFO: Creating node: http://localhost:9990/node-config/PaymentNode
[java] 21-Jul-2009 01:41:38 org.apache.tuscany.sca.node.impl.NodeImpl
configureNode
[java] INFO: Loading contribution:
file:/F:/book/samp11/travelsample/testdomain/../contributions/payment-java-contribution/target/scatours-payment-java-contribution.jar
[java] 21-Jul-2009 01:41:39 org.apache.tuscany.sca.node.impl.NodeImpl
configureNode
[java] INFO: Loading composite:
http://localhost:9990/composite-resolved/composite:scatours-payment;http://scatours;payment
[java] 21-Jul-2009 01:41:39
org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
[java] SEVERE: XMLSchema validation error occured in: null ,line = 1,
column = 733, Message = cvc-datatype-valid.1.2.1:
'customerRegistry#CustomerRegistryComponent/CustomerRegistry' is not a valid
value for 'QName'.
[java] 21-Jul-2009 01:41:39
org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
[java] SEVERE: XMLSchema validation error occured in: null ,line = 1,
column = 733, Message = cvc-attribute.3: The value
'customerRegistry#CustomerRegistryComponent/CustomerRegistry' of attribute
'name' on element 'binding.sca' is not valid with respect to its type, 'QName'.
[java] 21-Jul-2009 01:41:39
org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
[java] SEVERE: XMLSchema validation error occured in: null ,line = 1,
column = 1,174, Message = cvc-datatype-valid.1.2.1:
'emailGateway#EmailGatewayComponent/EmailGateway' is not a valid value for
'QName'.
[java] 21-Jul-2009 01:41:39
org.apache.tuscany.sca.contribution.processor.ValidatingXMLStreamReader
[java] SEVERE: XMLSchema validation error occured in: null ,line = 1,
column = 1,174, Message = cvc-attribute.3: The value
'emailGateway#EmailGatewayComponent/EmailGateway' of attribute 'name' on
element 'binding.sca' is not valid with respect to its type, 'QName'.
[java] 21-Jul-2009 01:41:40 org.apache.tuscany.sca.node.impl.NodeImpl start
[java] INFO: Starting node: http://localhost:9990/node-config/PaymentNode
[java] 21-Jul-2009 01:41:40 org.apache.tuscany.sca.http.jetty.JettyServer
addServletMapping
[java] INFO: Added Servlet mapping: http://Angels:8081/Payment
[java] 21-Jul-2009 01:41:40
org.apache.tuscany.sca.node.launcher.NodeLauncher main
[java] INFO: SCA Node is now started.
[java] 21-Jul-2009 01:41:40
org.apache.tuscany.sca.node.launcher.NodeLauncher main
[java] INFO: Press 'q' to quit, 'r' to restart.
> 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-1.5.1
>
>
> 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.
