Use the Property Values page to set the attribute values of the tag. The oracle.xml.xsql.ViewObject action handler supports several optional features.
max-rows—(Optional, number value) If specified, limits the number of rows retrieved to the non-negative number N. If not specified, the default value if this optional attribute is "-1" which means "all rows" (in other words, no maximum).
skip-rows—(Optional, number value) If specified, skips the initial N rows retrieved from the view before beginning to generate XML for the remaining rows. Rows that are skipped do not count towards the max-rows limit, if specified. For example, specifying the combination of skip-rows="10" and max-rows="10" would retrieve the effective rows 11 through 20.
max-levels—(Optional, number value) If specified, limits the number of levels of depth that view link accessor attributes will be traversed. If not specified, the default is "-1" for no limit. For example, if you have DeptView linked to EmpView linked to DependentView and you use this action handler against the top DeptView, a value of max-levels="0" would retrieve only the DeptView information. max-levels="1" would retrieve DeptView and related EmpView information. max-levels="2" would retrieve both nested levels of EmpView and DependentView information.
In addition to these optional attributes, an optional <where> element can be nested inside the <xsql:action handler="oracle.xml.xsql.ViewObject"> tag to do query-by-example functionality. The <where> element can contain any number of nested <attribute> elements to provide query-by-example criteria against that attribute name.
<xsql:action handler="oracle.xml.xsql.ViewObject"
name="ViewUsageName"
appmodule="fully.qualified.AppModuleName"
configname="someconfigname">
<where>
<attribute name="attrname1" value="someval2"/>
<attribute name="attrname2" value="someval2"/>
</where>
</xsql:action>
As with any XSQL Action Handler, XSQL attributes can be used
anywhere attribute values are provided, so the entire use (or any part
of it) can be driven by attribute values like:
<xsql:action handler="oracle.xml.xsql.ViewObject"
name="ViewUsageName"
appmodule="fully.qualified.AppModuleName"
configname="someconfigname">
<where>
<attribute name="{@attr}" value="{@val}"/>
</where>
</xsql:action>
Related topics