A patch from Bruno Busco "Example application should use FindScreenDecorator" (https://issues.apache.org/jira/browse/OFBIZ-1846) - OFBIZ-1846

git-svn-id: https://svn.apache.org/repos/asf/ofbiz/trunk@671230 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jacques Le Roux
2008-06-24 16:06:17 +00:00
parent dbd34520d7
commit bfd0fdc03b
2 changed files with 7 additions and 1 deletions
@@ -26,6 +26,7 @@ under the License.
<actions>
<set field="headerItem" value="AjaxExample"/>
<set field="titleProperty" value="PageTitleFindExample"/>
<set field="exampleCtx" from-field="parameters"/>
</actions>
<widgets>
<decorator-screen name="main-decorator" location="${parameters.mainDecoratorLocation}">
@@ -60,9 +60,14 @@ under the License.
</form>
<!-- Typically, this extended form wouldn't be necessary. The parent form (ListExamples) would
have these attributes. -->
have these attributes.
For the Ajax example we want all example entities listed, so the we use the entity-condition
instead of the performFind service. -->
<form name="ListExamplesAjax" extends="ListExamples" type="list" paginate-target="authview/findExampleAjax">
<on-event-update-area event-type="paginate" area-id="ListExamplesAjax" area-target="ListExampleFormOnly"/>
<actions>
<entity-condition entity-name="Example"><order-by field-name="exampleName"/></entity-condition>
</actions>
</form>
<form name="EditExample" type="single" target="updateExample" title="" default-map-name="example">