bruno 2003/10/31 04:24:24
Modified: src/blocks/woody/java/org/apache/cocoon/woody/formmodel
Action.java
Log:
Removed formContext.setActionEvent call, not needed anymore.
Revision Changes Path
1.5 +3 -5
cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/formmodel/Action.java
Index: Action.java
===================================================================
RCS file:
/home/cvs/cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/formmodel/Action.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Action.java 24 Oct 2003 22:49:08 -0000 1.4
+++ Action.java 31 Oct 2003 12:24:24 -0000 1.5
@@ -62,8 +62,9 @@
/**
* An Action widget. An Action widget can cause an [EMAIL PROTECTED]
ActionEvent} to be triggered
- * on the server side, which will be handled by the [EMAIL PROTECTED]
org.apache.cocoon.woody.FormHandler FormHandler}
- * (in case of flowscript this is a javascript function). An Action widget
can e.g. be rendered as a button,
+ * on the server side, which will be handled by either the event handlers
defined in the
+ * form definition, and/or by the [EMAIL PROTECTED]
org.apache.cocoon.woody.event.FormHandler FormHandler}
+ * registered with the form, if any. An Action widget can e.g. be rendered
as a button,
* or as a hidden field which gets its value set by javascript. The Action
widget will generate its associated
* ActionEvent when a requestparameter is present with as name the id of
this Action widget, and as
* value a non-empty value.
@@ -92,9 +93,6 @@
form.addWidgetEvent(new ActionEvent(this,
definition.getActionCommand()));
handleActivate();
-
- // TODO : to be removed
- formContext.setActionEvent(new ActionEvent(this,
definition.getActionCommand()));
}
}
