GVCoreCallNode

From GreenVulcano Wiki
Revision as of 10:06, 23 February 2012 by Anonymous (talk) ({{GVESB}} Configuration)
Jump to: navigation, search

GreenVulcano® ESB Configuration

GVCoreCallNode element allows direct invocation of a GreenVulcano® ESB core workflow.

Dynamic fields can contains placeholders.

The following table shows the GVCoreCallNode element's attributes:

Attribute Tyte Description
type fixed This attribute must assume the value flow-node.
class fixed This attribute must assume the value it.greenvulcano.gvesb.core.flow.GVCoreCallNode.
op-type fixed This attribute must assume the value corecall.
id required ID of the node. Unique within the Flow.
dynamic optional If 'true' id-system, id-service and operation attributes can contains metadata to be resolved at runtime.
id-service required Name of service to invoke.
id-system required Name of service's client.
operation required Name of service's operation to invoke
overwrite-sys-svc optional If 'true' SYSTEM and SERVICE fields of GVBuffer will be overwritten.

The default is 'false'.

change-log-context optional If 'true' log context is updated.

The default is 'false'.

input required Specifies the input (from the execution environment) for the operation.

If the input is an exception, the operation is not performed, and the output is set equal input exception.

output optional The operation's output (GVBuffer or Exception) is inserted into the execution environment with this exact name.

Default to "input" value.

next-node-id required Indicates the next node in the workflow to execute when the operation ends.
point-x optional X position of the node in the VulCon workflows editor.

Immutable, used by VulCon®.

point-y optional Y position of the node in the VulCon workflows editor.

Immutable, used by VulCon®.

dump-in-out optional If true enable the dump of the input/output GVBuffer.

Default false.

dump-env-in-out optional If true enable the dump of the input/output Execution Environment.

Default false.