Christopher,
In this case the "entity-condition" op gets the list-name from the "form"
element and puts the list if gets there. And since that is the variable that
the form expects to find the list info in, it works out.
-Al
On 2/19/07, Christopher Snow <[EMAIL PROTECTED]> wrote:
I'm struggling with form-widgets:
<xs:attribute type="xs:string" name="list-name">
<xs:annotation><xs:documentation>for list type and other multiple
data/form types this is the name of the list in the context to iterate
over</xs:documentation></xs:annotation>
</xs:attribute>
How does the list get put in the context? Is it put into the context by
<actions> (see below for the example app)?
Is it redundant in ListExamples as it is not being referred to anywhere?
Many thanks,
Chris
<form name="ListExamples" type="list" list-name="examples"
paginate-target="FindExample"
default-title-style="tableheadtext"
default-widget-style="tabletext" default-tooltip-style="tabletext">
<actions>
<entity-condition entity-name="Example">
<order-by field-name="description"/>
</entity-condition>
</actions>
<field name="exampleId" title="${uiLabelMap.ExampleExampleId}"
widget-style="buttontext">
<hyperlink also-hidden="false" description="${exampleId}"
target="EditExample?exampleId=${exampleId}"/>
</field>
<field name="exampleName" title="${uiLabelMap.CommonName
}"><display/></field>
<field name="exampleTypeId"
title="${uiLabelMap.CommonType}"><display-entity
entity-name="ExampleType"/></field>
<field name="statusId"
title="${uiLabelMap.CommonStatus}"><display-entity
entity-name="StatusItem"/></field>
<field name="description" title="${uiLabelMap.CommonDescription
}"><display/></field>
</form>
