Difference between revisions of "Data provider"

From GreenVulcano Wiki
Jump to: navigation, search
(→‎Definition)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
==Definition==
 
==Definition==
−
ODP 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 / or XPath.
+
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, this fileds are of three type:
+
 
−
*IN,
+
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:
−
*OUT,
+
*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-OUT
+
*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.
−
All data provider field contains the elements that define a field identified by a key, these fields can be of three types in, out, in-out. The fields of type IN operation is performed on the input object type getValue going to put in execution context with the key defined, then in subsequent expressions we use these values ​​by logging in with the syntax # key when OGNL expressions. The fields are defined type out only if you want to make the expression that modify object context.
+
*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 {{GVESB}} 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]]
  
 
{{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:

  1. Input: object set, usually the current GVBuffer, which will not be overwritten from attribute 'source-selector';
  2. 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:

{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>

Retrieved from "https://gvwiki.greenvulcano.com/gvwiki/index.php?title=Data_provider&oldid=3224"