Difference between revisions of "GVCoreCallNode"

From GreenVulcano Wiki
Jump to: navigation, search
Line 1: Line 1:
=={{GVESB}} Configuration==
+
=={{VULCON}} / {{GVCONSOLE}} Configuration==
  
 
GVCoreCallNode element allows direct invocation of a {{GVESB}} core workflow, is a [[Flow]] element that extends [[FlowNode]].
 
GVCoreCallNode element allows direct invocation of a {{GVESB}} core workflow, is a [[Flow]] element that extends [[FlowNode]].

Revision as of 14:49, 4 March 2013

VulCon / GV Console Configuration

GVCoreCallNode element allows direct invocation of a GreenVulcano® ESB core workflow, is a Flow element that extends FlowNode.

Dynamic fields can contains placeholders.

The following table shows the GVCoreCallNode element's attributes:

Attribute Tyte Description
class fixed This attribute must assume the value it.greenvulcano.gvesb.core.flow.GVCoreCallNode.
op-type fixed This attribute must assume the value corecall.
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 optional 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 'true'.

input-ref-dp optional Name of Data Provider to use for input manipulation.

This Data Provider will receive in input a GVBuffer and must return the object to be inserted in GVBuffer.object.

output-ref-dp optional Name of Data Provider to use for output manipulation.

This Data Provider will receive in input a GVBuffer and must return the object to be inserted in GVBuffer.object.