diff options
author | rfeng <rfeng@13f79535-47bb-0310-9956-ffa450edef68> | 2011-09-02 23:32:33 +0000 |
---|---|---|
committer | rfeng <rfeng@13f79535-47bb-0310-9956-ffa450edef68> | 2011-09-02 23:32:33 +0000 |
commit | e7cc5737c05ea9e1e88025ac8e75055f6e9fd9bd (patch) | |
tree | 81cb106a72cf9669e4c3469cac4d55c1595d469e /sca-java-2.x/trunk/modules/core | |
parent | 8dddab593539a95331a32f4c43c103d5614fca67 (diff) |
Fix the single quote issues in all message bundles
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1164763 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'sca-java-2.x/trunk/modules/core')
-rw-r--r-- | sca-java-2.x/trunk/modules/core/src/main/resources/endpoint-validation-messages.properties | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/sca-java-2.x/trunk/modules/core/src/main/resources/endpoint-validation-messages.properties b/sca-java-2.x/trunk/modules/core/src/main/resources/endpoint-validation-messages.properties index a52c124780..5c9e01ffdc 100644 --- a/sca-java-2.x/trunk/modules/core/src/main/resources/endpoint-validation-messages.properties +++ b/sca-java-2.x/trunk/modules/core/src/main/resources/endpoint-validation-messages.properties @@ -18,6 +18,7 @@ # under the License. # # -NoEndpointsFound = No endpoints found in the domain that match the reference {0} -EndpointReferenceCantBeMatched = = Unable to match the endpoint reference {0} with the policy of the service to which it refers, matching process was {1} -ComponentReferenceTargetNotFound = Component reference target not found at deployment time, it might be a remote service elsewhere in the SCA Domain so we'll try and resolve it again at runtime: {0} +NoEndpointsFound = No endpoints found in the domain that match the reference {0} +EndpointReferenceCantBeMatched = Unable to match the endpoint reference {0} with the policy of the service to which it refers, matching process was {1} +# Single quote (we'll) needs to be escaped as we''ll +ComponentReferenceTargetNotFound = Component reference target not found at deployment time, it might be a remote service elsewhere in the SCA Domain so we''ll try and resolve it again at runtime: {0} |