Method Detail

• public java.util.Map<java.lang.String, java.lang.Object> call()

• public ServiceCallSync disableAuthz()

  Disable authorization for the current thread during this service call.

• public ServiceCallSync ignorePreviousError(boolean ipe)

  Normally service won't run if there was an error (ec.message.hasError()), set this to true to run anyway.

• public ServiceCallSync ignoreTransaction(boolean ignoreTransaction)

  By default a service uses the existing transaction or begins a new one if no tx is in place. Set this flag to ignore the transaction, not checking for one or starting one if no transaction is in place.

• public ServiceCallSync multi(boolean mlt)

  If true expect multiple sets of parameters passed in a single map, each set with a suffix of an underscore and the row of the number, ie something like "userId_8" for the userId parameter in the 8th row.

  Returns:

  Reference to this for convenience.

• public ServiceCallSync name(java.lang.String serviceName)

  Name of the service to run. The combined service name, like: "${path}.${verb}${noun}". To explicitly separate the verb and noun put a hash (#) between them, like: "${path}.${verb}#${noun}" (this is useful for calling the implicit entity CrUD services where verb is create, update, or delete and noun is the name of the entity).

• public ServiceCallSync name(java.lang.String verb, java.lang.String noun)

• public ServiceCallSync name(java.lang.String path, java.lang.String verb, java.lang.String noun)

• public ServiceCallSync noRememberParameters()

  Do not remember parameters in ArtifactExecutionFacade history and stack, important for service calls with large parameters that should be de-referenced for GC before ExecutionContext is destroyed.

• public ServiceCallSync parameter(java.lang.String name, java.lang.Object value)

  Single name, value pairs to put in the context (in parameters) passed to the service.

• public ServiceCallSync parameters(java.util.Map<java.lang.String, ?> context)

  Map of name, value pairs that make up the context (in parameters) passed to the service.

• public ServiceCallSync requireNewTransaction(boolean requireNewTransaction)

  If true suspend/resume the current transaction (if a transaction is active) and begin a new transaction for the scope of this service call.

  Returns:

  Reference to this for convenience.

• public ServiceCallSync softValidate(boolean sv)

  If true add danger messages instead of hard error messages for validation

• public ServiceCallSync transactionTimeout(int timeout)

  Override the transaction-timeout attribute in the service definition, only used if a transaction is begun in this service call.

• public ServiceCallSync useTransactionCache(boolean useTransactionCache)

  Use the write-through TransactionCache. WARNING: test thoroughly with this. While various services will run much faster there can be issues with no changes going to the database until commit (for view-entity queries depending on data, etc). Some known limitations: - find list and iterate don't cache results (but do filter and add to results aside from limitations below) - EntityListIterator.getPartialList(), .relative(), and .absolute() are not supported when tx cache is in place and values have been created; getCompleteList(), iteration using next() calls, etc are supported - find with DB limit will return wrong number of values if deleted values were in the results - find count doesn't add for created values, subtract for deleted values, and for updates if old matched and new doesn't subtract and vice-versa - view-entities won't work, they don't incorporate results from TX Cache - for-update queries are remembered but for best results do for-update queries before non for-update queries on the same record

  Returns:

  Reference to this for convenience.