It's interesting that we need this. It is probably common enough that
maybe we should change the groovy event handler to automatically put
it in the context.
Also, does anyone know what the "ExampleFeatureOptions" screen in the
ExampleFeatureScreens.xml file is meant to be used for? It doesn't
seem to be referred to anywhere, and it points to a script that
doesn't seem to exist, and an ftl file that doesn't seem to exist...
-David
On Jun 21, 2008, at 8:10 PM, [EMAIL PROTECTED] wrote:
Author: lektran
Date: Sat Jun 21 19:10:26 2008
New Revision: 670298
URL: http://svn.apache.org/viewvc?rev=670298&view=rev
Log:
Fix after groovy migration
Modified:
ofbiz/trunk/framework/example/webapp/example/WEB-INF/actions/
includes/FindExampleFeatures.groovy
Modified: ofbiz/trunk/framework/example/webapp/example/WEB-INF/
actions/includes/FindExampleFeatures.groovy
URL:
http://svn.apache.org/viewvc/ofbiz/trunk/framework/example/webapp/example/WEB-INF/actions/includes/FindExampleFeatures.groovy?rev=670298&r1=670297&r2=670298&view=diff
=
=
=
=
=
=
=
=
======================================================================
--- ofbiz/trunk/framework/example/webapp/example/WEB-INF/actions/
includes/FindExampleFeatures.groovy (original)
+++ ofbiz/trunk/framework/example/webapp/example/WEB-INF/actions/
includes/FindExampleFeatures.groovy Sat Jun 21 19:10:26 2008
@@ -25,6 +25,7 @@
import org.ofbiz.entity.condition.EntityFunction;
import org.ofbiz.entity.condition.EntityOperator;
+delegator = request.getAttribute("delegator");
andExprs = [];
fieldValue = request.getParameter("exampleFeatureId");
