TUSCANY-3641 - correct the comment as binding-ws models are added in that part of the code now rather than later in the higher processor.

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

1 files changed, 3 insertions, 3 deletions

diff --git a/sca-java-2.x/trunk/modules/implementation-java/src/main/java/org/apache/tuscany/sca/implementation/java/introspect/impl/JAXWSProcessor.java b/sca-java-2.x/trunk/modules/implementation-java/src/main/java/org/apache/tuscany/sca/implementation/java/introspect/impl/JAXWSProcessor.java
index ad6a9dee68..d97d375a0d 100644
--- a/sca-java-2.x/trunk/modules/implementation-java/src/main/java/org/apache/tuscany/sca/implementation/java/introspect/impl/JAXWSProcessor.java
+++ b/sca-java-2.x/trunk/modules/implementation-java/src/main/java/org/apache/tuscany/sca/implementation/java/introspect/impl/JAXWSProcessor.java
@@ -197,9 +197,9 @@ public class JAXWSProcessor extends BaseJavaClassVisitor {
         }               

         

         if (hasJaxwsAnnotation == true){

-            // Note that services are based on JAXWS annotations so 

-            // that during the build process a binding.ws can be added

-            // if required

+            // Note that services are based on JAXWS annotations in case 

+            // we need to know later. Add a ws binding and a JAXWS annotation

+            // implies a WS binding

             for ( Service service : type.getServices() ) {

                 service.setJAXWSService(true);

                 createWSBinding(type, service);