More correctly handle the jms uri format of the binding. Still needs more work as there jms uri can be quite complicated and has a whole spec of its own that we should implement

git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@984756 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 1 insertions, 1 deletions

diff --git a/sca-java-2.x/trunk/modules/binding-jms/src/main/resources/binding-jms-validation-messages.properties b/sca-java-2.x/trunk/modules/binding-jms/src/main/resources/binding-jms-validation-messages.properties
index 33d6a9df5c..ca924c3c8f 100644
--- a/sca-java-2.x/trunk/modules/binding-jms/src/main/resources/binding-jms-validation-messages.properties
+++ b/sca-java-2.x/trunk/modules/binding-jms/src/main/resources/binding-jms-validation-messages.properties
@@ -33,7 +33,7 @@ InvalidDestinationType = Invalid destination type: {0}
 MissingActivationSpecName = Missing ActivationSpec Name
 MissingResponseActivationSpec = Missing response ActivationSpec name
 UnknownTokenInURI = Unknown token {0} in uri: {1}
-MustStartWithSchema = URI must start with the scheme 'jms:' for uri: {0}
+MustStartWithSchema = URI must start with the scheme 'jms:jndi:' or 'jms:queue:' or 'jms:topic:'  for uri: {0}
 InvalidCorrelationScheme = Invalid correlationScheme: {0}
 UnexpectedElement = Incomplete binding.jms definition found unexpected element: {0}
 UnexpectedResponseElement = Incomplete binding.jms/response definition found unexpected element: {0}