Correct comment

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

1 files changed, 3 insertions, 4 deletions

diff --git a/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java b/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
index 89fdc09ae1..cf1c9cb05f 100644
--- a/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
+++ b/sca-java-2.x/trunk/modules/builder/src/main/java/org/apache/tuscany/sca/builder/impl/ModelBuilderImpl.java
@@ -97,15 +97,14 @@ public class ModelBuilderImpl implements CompositeBuilder {
             composite = compositeIncludeBuilder.build(composite, context);
 
             // Set up the structural URIs for components (services/references/bindings)
-            // TODO does this need to happen before policy attachment
             composite = structuralURIBuilder.build(composite, context);
             
             // Apply policy external attachment. Happens before the composite type
             // is created so that suitable promotion and structural processing is
             // applied to the attached policies
-            // TODO - I don't think this is correct. The policy spec (4.12.1)implies that
-            //        policy attachment happens independently of implementation or 
-            //        structural inheritance
+            // TODO - Can you attach a policy to a component and have it promoted to the 
+            //        components services and references. If yes this call is in the 
+            //        right place
             composite = policyAttachmentBuilder.build(composite, context);
 
             // Process the implementation hierarchy by calculating the component type