Difference between revisions of "Data provider"
(→Definition) |
(→Definition) |
||
| Line 4: | Line 4: | ||
*IN, | *IN, | ||
*OUT, | *OUT, | ||
| − | IN-OUT | + | *IN-OUT, |
| − | + | ||
| + | Following a list of Data provider avaiable: | ||
| + | *ObjectDataProvider: | ||
| + | *StringDataProvider | ||
| + | *MapDataProvider | ||
| + | *ArrayDataProvider | ||
| + | *CollectionDataProvider | ||
| + | *XMLEventCollectionDataProvider | ||
| + | *InputStreamDataProvider | ||
| + | *JMSBytesMessageDataProvider | ||
| + | *JMSMapMessageDataProvider | ||
| + | *JMSObjectMessageDataProvider | ||
| + | *JMSStreamMessageDataProvider | ||
| + | *JMSTextMessageDataProvider | ||
| + | *Axis2MessageContextDataProvider | ||
| + | *Axis2SAAJSOAPMessageDataProvider | ||
| + | *HttpMethodDataProvider | ||
{{VOTE}} | {{VOTE}} | ||
Revision as of 16:35, 10 February 2012
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. Each Data provider contains a field element identify by a key, this fileds are of three type:
- IN,
- OUT,
- IN-OUT,
Following a list of Data provider avaiable:
- ObjectDataProvider:
- StringDataProvider
- MapDataProvider
- ArrayDataProvider
- CollectionDataProvider
- XMLEventCollectionDataProvider
- InputStreamDataProvider
- JMSBytesMessageDataProvider
- JMSMapMessageDataProvider
- JMSObjectMessageDataProvider
- JMSStreamMessageDataProvider
- JMSTextMessageDataProvider
- Axis2MessageContextDataProvider
- Axis2SAAJSOAPMessageDataProvider
- HttpMethodDataProvider
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>
