system/src/sc/layer/Layer.java
public void registerScopeProcessor(String scopeName, IScopeProcessor processor) {
      if (scopeProcessors == null)
         scopeProcessors = new HashMap<String,IScopeProcessor>();
      IScopeProcessor old = scopeProcessors.put(scopeName, processor);
      if (old != null && layeredSystem.options.verbose) {
         info("Scope processor for: " + scopeName + " replaced: " + old + " with: " + processor);
      }
      String scopeAlias = scopeAliases == null ? null : scopeAliases.remove(scopeName);
      if (scopeAlias != null) {
         verbose("Scope processor replaced scope alias: " + scopeName + ": " + scopeAlias);
      }
   }
/**
    * When encountering scope&lt;name&gt; in the code as an annotation for a type, the IScopeProcessor will allow
    * the framework developer the ability to customize how the getX, setX, methods of the object or property are
    * generated.  You can inject additional interfaces and fields into the type.  Additional parameters to the
    * constructor which are obtained in the current context in which this scope is valid.  Scopes let you flexibly
    * separate the names from how they are implemented in code - supporting iteration and other advanced constructs
    * at both the runtime and compile time contexts.
    */
When encountering scope<name> in the code as an annotation for a type, the IScopeProcessor will allow
the framework developer the ability to customize how the getX, setX, methods of the object or property are
generated.  You can inject additional interfaces and fields into the type.  Additional parameters to the
constructor which are obtained in the current context in which this scope is valid.  Scopes let you flexibly
separate the names from how they are implemented in code - supporting iteration and other advanced constructs
at both the runtime and compile time contexts.
When encountering scope<name > in the code as an annotation for a type the IScopeProcessor will allow the framework developer the ability to customize how the getX setX methods of the object or property are generated . You can inject additional interfaces and fields into the type . Additional parameters to the constructor which are obtained in the current context in which this scope is valid . Scopes let you flexibly separate the names from how they are implemented in code - supporting iteration and other advanced constructs at both the runtime and compile time contexts .
public void registerScopeProcessor(String scopeName, IScopeProcessor processor) {
      if (scopeProcessors == null)
         scopeProcessors = new HashMap<String,IScopeProcessor>();
      IScopeProcessor old = scopeProcessors.put(scopeName, processor);
      if (old != null && layeredSystem.options.verbose) {
         info("Scope processor for: " + scopeName + " replaced: " + old + " with: " + processor);
      }
      String scopeAlias = scopeAliases == null ? null : scopeAliases.remove(scopeName);
      if (scopeAlias != null) {
         verbose("Scope processor replaced scope alias: " + scopeName + ": " + scopeAlias);
      }
   }
public void registerScopeProcessor ( String scopeName , IScopeProcessor processor ) { if ( scopeProcessors == null ) scopeProcessors = new HashMap < String , IScopeProcessor > ( ) ; IScopeProcessor old = scopeProcessors . put ( scopeName , processor ) ; if ( old != null && layeredSystem . options . verbose ) { info ( "Scope processor for: " + scopeName + " replaced: " + old + " with: " + processor ) ; } String scopeAlias = scopeAliases == null ? null : scopeAliases . remove ( scopeName ) ; if ( scopeAlias != null ) { verbose ( "Scope processor replaced scope alias: " + scopeName + ": " + scopeAlias ) ; } }
When encountering scope&lt;name&gt; in the code as an annotation for a type, the IScopeProcessor will allow
 the framework developer the ability to customize how the getX, setX, methods of the object or property are
 generated.
When encountering scope&lt ; name&gt ; in the code as an annotation for a type the IScopeProcessor will allow the framework developer the ability to customize how the getX setX methods of the object or property are generated .