Difference between revisions of "Data provider"
(→Definition) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==Definition== | ==Definition== | ||
| − | ODP (Object Data Provider) is a framework that lets you manage bidirectional conversion between instances of GVBuffer and generic objects, the access to the generic objects fields will be execute through OGNL and | + | ODP (Object Data Provider) is a framework that lets you manage bidirectional conversion between instances of GVBuffer and generic objects, the access to the generic objects fields will be execute through OGNL, XPath and Regex. |
| − | Each Data provider contains a field element identify by a key, | + | Each Data provider contains a field element identify by a key, these fields are of three types and indicate when an extension has to be applied: |
| − | *INOUT, The expression is evaluated on the object set (usually the current GVBuffer, unless otherwise specified by the attribute 'source-selector') the value returned by the expression, is added to the context with the prefix 'key_' + @ key, and set the data provider to be returned in the output. | + | *INOUT, The expression is evaluated on the object set (usually the current [[GVBuffer]], unless otherwise specified by the attribute 'source-selector') the value returned by the expression, is added to the context with the prefix 'key_' + @ key, and set the data provider to be returned in the output. |
| − | *IN, The expression is evaluated on the object set (usually the current GVBuffer, unless otherwise specified by the attribute 'source-selector') the value returned by the expression is added to the context with the prefix 'key_' + @ key. | + | *IN, The expression is evaluated on the object set (usually the current [[GVBuffer]], unless otherwise specified by the attribute 'source-selector') the value returned by the expression is added to the context with the prefix 'key_' + @ key. |
*OUT, The expression is evaluated directly on the object that is returned by the DataProvider. | *OUT, The expression is evaluated directly on the object that is returned by the DataProvider. | ||
In all cases, two variables are added to the context: | In all cases, two variables are added to the context: | ||
| Line 10: | Line 10: | ||
#Output: the object that is returned by the DataProvider. | #Output: the object that is returned by the DataProvider. | ||
| − | Expression are pre / post processing of data that can be made automatically from the connector before invoking | + | Expression are pre / post processing of data that can be made automatically from the connector before invoking {{GVESB}} and / or before returning the result to the caller. |
| − | |||
| − | |||
| − | |||
| − | Following a list of Data provider | + | Following a list of Data provider available: |
| − | *ObjectDataProvider | + | * [[ObjectDataProvider]] |
| − | *StringDataProvider | + | * [[StringDataProvider]] |
| − | *MapDataProvider | + | * [[MapDataProvider]] |
| − | *ArrayDataProvider | + | * [[ArrayDataProvider]] |
| − | *[[CollectionDataProvider]] | + | * [[CollectionDataProvider]] |
| − | *XMLEventCollectionDataProvider | + | * [[XMLEventCollectionDataProvider]] |
| − | *InputStreamDataProvider | + | * [[InputStreamDataProvider]] |
| − | *JMSBytesMessageDataProvider | + | * [[JMSBytesMessageDataProvider]] |
| − | *JMSMapMessageDataProvider | + | * [[JMSMapMessageDataProvider]] |
| − | *JMSObjectMessageDataProvider | + | * [[JMSObjectMessageDataProvider]] |
| − | *JMSStreamMessageDataProvider | + | * [[JMSStreamMessageDataProvider]] |
| − | *JMSTextMessageDataProvider | + | * [[JMSTextMessageDataProvider]] |
| − | *Axis2MessageContextDataProvider | + | * [[Axis2MessageContextDataProvider]] |
| − | *Axis2SAAJSOAPMessageDataProvider | + | * [[Axis2SAAJSOAPMessageDataProvider]] |
| − | *HttpMethodDataProvider | + | * [[HttpMethodDataProvider]] |
{{VOTE}} | {{VOTE}} | ||
Latest revision as of 17:14, 3 April 2012
Definition
ODP (Object Data Provider) is a framework that lets you manage bidirectional conversion between instances of GVBuffer and generic objects, the access to the generic objects fields will be execute through OGNL, XPath and Regex.
Each Data provider contains a field element identify by a key, these fields are of three types and indicate when an extension has to be applied:
- INOUT, The expression is evaluated on the object set (usually the current GVBuffer, unless otherwise specified by the attribute 'source-selector') the value returned by the expression, is added to the context with the prefix 'key_' + @ key, and set the data provider to be returned in the output.
- IN, The expression is evaluated on the object set (usually the current GVBuffer, unless otherwise specified by the attribute 'source-selector') the value returned by the expression is added to the context with the prefix 'key_' + @ key.
- OUT, The expression is evaluated directly on the object that is returned by the DataProvider.
In all cases, two variables are added to the context:
- Input: object set, usually the current GVBuffer, which will not be overwritten from attribute 'source-selector';
- Output: the object that is returned by the DataProvider.
Expression are pre / post processing of data that can be made automatically from the connector before invoking GreenVulcano® ESB and / or before returning the result to the caller.
Following a list of Data provider available:
- ObjectDataProvider
- StringDataProvider
- MapDataProvider
- ArrayDataProvider
- CollectionDataProvider
- XMLEventCollectionDataProvider
- InputStreamDataProvider
- JMSBytesMessageDataProvider
- JMSMapMessageDataProvider
- JMSObjectMessageDataProvider
- JMSStreamMessageDataProvider
- JMSTextMessageDataProvider
- Axis2MessageContextDataProvider
- Axis2SAAJSOAPMessageDataProvider
- HttpMethodDataProvider
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>
