Name

adams.flow.standalone.WeakExternalStandalone

Synopsis

Standalone that executes an external standalone actor stored on disk.
For executing whole flows, use the adams.flow.standalone.ExternalFlow standalone actor instead.
Only used at design time, gets deactivated at runtime.

Additional information

Flow input/output:
-standalone-

See also

• adams.flow.standalone.ExternalFlow

Options

• loggingLevel
  

  The logging level for outputting errors and debugging output.

  command-line	-logging-level <OFF|SEVERE|WARNING|INFO|CONFIG|FINE|FINER|FINEST>
  default	WARNING
  min-user-mode	Expert

  
  
• name
  

  The name of the actor.

  command-line	-name <java.lang.String>
  default	WeakExternalStandalone

  
  
• annotations
  

  The annotations to attach to this actor.

  command-line	-annotation <adams.core.base.BaseAnnotation>
  default

  
  
• skip
  

  If set to true, transformation is skipped and the input token is just forwarded as it is.

  command-line	-skip <boolean>
  default	false

  
  
• stopFlowOnError
  

  If set to true, the flow execution at this level gets stopped in case this actor encounters an error; the error gets propagated; useful for critical actors.

  command-line	-stop-flow-on-error <boolean>
  default	false
  min-user-mode	Expert

  
  
• silent
  

  If enabled, then no errors are output in the console; Note: the enclosing actor handler must have this enabled as well.

  command-line	-silent <boolean>
  default	false
  min-user-mode	Expert

  
  
• actorFile
  

  The file containing the external actor; programmatic variables like 'flow_dir' can be used as part of the file name as they get expanded before attempting to load the file.

  command-line	-file <adams.core.io.FlowFile>
  default	${CWD}

  
  
• monitor
  

  The scheme to use for monitoring the actor file for changes.

  command-line	-monitor <adams.core.io.filechanged.FileChangeMonitor>
  default	adams.core.io.filechanged.NoChange
  min-user-mode	Expert

  
  
• onTheFly
  

  If enabled, the external flow is not required to be present at set up time (eg if built on the fly), only at execution time.

  command-line	-on-the-fly <boolean>
  default	false