Difference between revisions of "Op-type"
(Created page with "==Description== This attribute indicates the type of operation that must execute. =={{VULCON}} / {{GVCONSOLE}} Configuration== The available operations are: * ''call'': if yo...") |
(→{{VULCON}} / {{GVCONSOLE}} Configuration) |
||
| Line 2: | Line 2: | ||
This attribute indicates the type of operation that must execute. | This attribute indicates the type of operation that must execute. | ||
| − | |||
| − | |||
The available operations are: | The available operations are: | ||
| Line 9: | Line 7: | ||
* ''call'': if you want {{GVESB}} to perform an invocation. | * ''call'': if you want {{GVESB}} to perform an invocation. | ||
* ''enqueue'': if you want {{GVESB}} to perform a send a message. | * ''enqueue'': if you want {{GVESB}} to perform a send a message. | ||
| − | * ''dequeue'': if you want {{GVESB}} to execute a receipt of a message. <br/> In this case you can also enter a sub-element | + | * ''dequeue'': if you want {{GVESB}} to execute a receipt of a message. <br/> In this case you can also enter a sub-element ''DequeueFilter'' (See bellow). |
* ''corecall'': if you want {{GVESB}} to execute an internal service call. | * ''corecall'': if you want {{GVESB}} to execute an internal service call. | ||
* ''check'' | * ''check'' | ||
| Line 17: | Line 15: | ||
* ''change [[GVBuffer]]'', | * ''change [[GVBuffer]]'', | ||
* ''end''. | * ''end''. | ||
| + | |||
| + | |||
| + | '''DequeueFilter''' | ||
| + | |||
| + | Used in [[GVOperationNode]] with ''op-type'' set to ''dequeue'', allows you to define the criteria for receiving messages. <br/> Will be received only messages that meet the criteria. <br/> May have one or more subelements of the following types: | ||
| + | |||
| + | * ''IDFilter'': would set the criteria of the received message ID. | ||
| + | * ''RetCodeFilter'': would set the criteria on the return code of the received message. | ||
| + | * ''SystemFilter'': would set the criteria field system of the received message. | ||
| + | * ''ServiceFilter'': would set the criteria in the field service of the received message. | ||
| + | * ''PropertyFilter'': would set the criteria on the properties of the received message | ||
| + | |||
| + | |||
| + | If multiple policies are specified, then the message to receive must meet them all. | ||
Revision as of 11:29, 26 January 2012
Description
This attribute indicates the type of operation that must execute.
The available operations are:
- call: if you want GreenVulcano® ESB to perform an invocation.
- enqueue: if you want GreenVulcano® ESB to perform a send a message.
- dequeue: if you want GreenVulcano® ESB to execute a receipt of a message.
In this case you can also enter a sub-element DequeueFilter (See bellow). - corecall: if you want GreenVulcano® ESB to execute an internal service call.
- check
- notification
- save
- wait
- change GVBuffer,
- end.
DequeueFilter
Used in GVOperationNode with op-type set to dequeue, allows you to define the criteria for receiving messages.
Will be received only messages that meet the criteria.
May have one or more subelements of the following types:
- IDFilter: would set the criteria of the received message ID.
- RetCodeFilter: would set the criteria on the return code of the received message.
- SystemFilter: would set the criteria field system of the received message.
- ServiceFilter: would set the criteria in the field service of the received message.
- PropertyFilter: would set the criteria on the properties of the received message
If multiple policies are specified, then the message to receive must meet them all.
