Difference between revisions of "GVNodeCheck"
(→{{GVESB}} Configuration) |
|||
| Line 15: | Line 15: | ||
The conditions can be redefined in several places, in case of ambiguity will be considered according to priority. | The conditions can be redefined in several places, in case of ambiguity will be considered according to priority. | ||
| − | The GVNodeCheck | + | The GVNodeCheck is a [[Flow]] element that extends [[FlowNode]]. It has the following attributes: |
| − | |||
| − | |||
{|class="gvtable" | {|class="gvtable" | ||
! Attribute !! Type !! Description | ! Attribute !! Type !! Description | ||
| − | |||
| − | |||
|- | |- | ||
| op-type || fixed || This attribute must assume the value '''check'''. | | op-type || fixed || This attribute must assume the value '''check'''. | ||
|- | |- | ||
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVNodeCheck'''. | | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVNodeCheck'''. | ||
| − | |||
| − | |||
|} | |} | ||
Might contain the following sub-elements: | Might contain the following sub-elements: | ||
| − | |||
* [[#GVRouting|GVRouting]] | * [[#GVRouting|GVRouting]] | ||
Revision as of 15:03, 4 March 2013
Description
This element defines the nodes where GreenVulcano® ESB makes decisions and determines which is the next node to execute.
GreenVulcano® ESB Configuration
Each 'GVNodeCheck' has a basic routing mechanism that chooses the next node only by the presence or absence of errors reported by exceptions. In any case, you can define more sophisticated routing mechanisms defining the sub-elements GVRouting, allowing many opportunities for branching flows:
- BASE (without GVRouting): Depending on the type of input (GVBuffer or exception) will be designated as the next node, the one expressed by the attributes 'default-id' or 'on-exception-id'.
- ADVANCED (with GVRouting): Regardless of the type of input (GVBuffer or exception) will assess the conditions for routing the order they are defined.
The first condition is verified the evaluation ends and the corresponding node is designated as the next node of the workflow.
If neither GVRouting condition is met and is considering an exception continues from
the node specified by 'on-exception-id' otherwise continues from the node specified by 'default-id'.
If 'default-id' is not configured will create an exception type it.greenvulcano.gvesb.core.GVCoreException and the node specified by 'on-exception-
id' is the next node to execute.
Routing conditions refer to conditions specified by the items 'Conditions' present on the nodes Flow, Service and Client (from high to low priority).
The conditions can be redefined in several places, in case of ambiguity will be considered according to priority.
The GVNodeCheck is a Flow element that extends FlowNode. It has the following attributes:
| Attribute | Type | Description |
|---|---|---|
| op-type | fixed | This attribute must assume the value check. |
| class | fixed | This attribute must assume the value it.greenvulcano.gvesb.core.flow.GVNodeCheck. |
Might contain the following sub-elements:
GVRouting
Associates a condition to a node of the workflow.
If the condition is satisfied, the workflow transfers control to the associated node.
The following table shows the GVRouting element's attributes:
| Attribute | Type | Description |
|---|---|---|
| condition | required | Name of the condition to be verified.
The actual meaning of the condition is specified by the elements 'Conditions' present on the nodes Flow, Service and Client. |
| next-node-id | required | Node to execute if the condition is verified. |
| 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®. |
Might contain the sub-element Description.
