Difference between revisions of "DBOSelect"
(Created page with "==Description== thumb|DBOSelect with VulCon The DBOSelect element represents the DBO optimized for select operations. =={{GVESB}} configuration== DBOSele...") |
|||
| Line 4: | Line 4: | ||
=={{GVESB}} configuration== | =={{GVESB}} configuration== | ||
| − | + | [[File:DBOSelect.jpg|thumb|DBOSelect with VulCon]] | |
DBOSelect might contain the following sub-elements: | DBOSelect might contain the following sub-elements: | ||
* [[Description]] | * [[Description]] | ||
Revision as of 19:38, 28 March 2012
Description
The DBOSelect element represents the DBO optimized for select operations.
GreenVulcano® ESB configuration
DBOSelect might contain the following sub-elements:
Its attributes are:
- type: dbo
- class: it.greenvulcano.gvesb.datahandling.dbo.DBOSelect
- name
- transformation
- force-mode (caller|xml2db): Force mode of the DBO, can be used in DBOBuilder whit more heterogeneous DBO.
Mode:
caller - inherit the mode of the caller
db2xml - data extraction mode - jdbc-connection-name: DataSource JNDI name.
Override connection defined in DBOBuilder. - ignore-input (true|false): Tell the engine do not use the input data.
- output-data: The default is the value of @name-Output.
For example:
<?xml version="1.0" encoding="UTF-8"?>
<DBOSelect class="it.greenvulcano.gvesb.datahandling.dbo.DBOSelect"
name="SearchPerson" transformation="SearchPerson" type="dbo">
<statement id="1" keys="1,2,3" type="select">select p.NAME, p.BIRTHDATE, c.NAME, cc.CNUMBER, cc.CREDIT, cc.ENABLED
from PERSON p, CITY c, CREDIT_CARD cc
where p.ID_CITY = c.ID and p.ID = cc.ID_OWNER</statement>
</DBOSelect>
