THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Okay, enough of the general stuff, here is a catalog and description of the available operations.
Call Operations
call-map-processor
The call-map-processor tag invokes a simple map processor from an existing map, creating a new map or adding to an existing one if the named out-map already exists. Resulting messages are added to the named list, and a new list is created if a list with the given name does not yet exist. Note that all lists and maps exist in the same context and must have unique names.
An inline simple-map-processor can be used by putting a simple-map-processor tag under the call-map-processor tag. If both an external and an inline map-processor are specified, the external one will be called first, allowing the inline one to override its behavior.
| Attribute Name | Required? | Description |
|---|---|---|
| xml-resource | N | The full path and filename on the classpath of the XML file which contains an external map processor to execute. This is only required if an external map processor is desired. |
| processor-name | N | The name of the external map processor to execute in the specified xml-resource. This is only required if an external map processor is desired. |
| in-map-name | Y | The name of a map in the method environment to use as the input map. |
| out-map-name | Y | The name of a map in the method environment to use as the output map. Will be created if it does not exist already. If already exists will be added to in place. |
| error-list-name | N | The name of a list in the method environment that the error messages will be added to. Will be created if it does not exist. Defaults to "error_list". |
| Sub-Element Name | How Many | Description |
|---|---|---|
| simple-map-processor | 0 or 1 | Uses the same definition as the simple-map-processor in the context of a simple-map-processors XML file. Allows for an inlined simple-map-processor. |
call-service
The call-service tag invokes a service through the Service Engine. If the specified error code is returned from the service, the event is aborted and the transaction in the current thread is rolled back. Otherwise, the remaining operations are invoked.
The result-to-request and result-to-session elements will be IGNORED when called in a service context. So, they are ONLY used when called in an event context.
| Attribute Name | Required? | Description |
|---|---|---|
| service-name | Y | |
| in-map-name | Y | |
| include-user-login | N | Defaults to "true". |
| error-code | N | Defaults to "error". |
| success-code | N | Defaults to "success". |
| Sub-Element Name | How Many | Description |
|---|---|---|
| error-prefix | 0 or 1 | |
| error-suffix | 0 or 1 | |
| success-prefix | 0 or 1 | |
| success-suffix | 0 or 1 | |
| message-prefix | 0 or 1 | |
| message-suffix | 0 or 1 | |
| default-message | 0 or 1 | |
| results-to-map | 0 to many | |
| result-to-field | 0 to many | |
| result-to-request | 0 to many | |
| result-to-session | 0 to many | |
| result-to-result | 0 to many |
call-service-asynch
Calls a service asynchronously and ignores the result, so no return messages are used; that doesn't mean no errors will result, but they would just be system errors like database failures, etc which all have system error messages.