Can't you just send in the cancel action as a parameter to the
confirmRemove.jsp?
So you would change:
<view name="verify-remove">confirmRemove.jsp</view>
to:
<view
name="verify-remove">confirmRemove.jsp?cancelAction=viewEntity.action</view>
and change the link in confirmRemove.jsp to:
<!-- Link to abort -->
<a href="<ww:property value="$cancelAction"/>">Abort</a>
That way the flow logic would stay in actions.xml.
Cheers,
Dick Zetterberg
[EMAIL PROTECTED]
----- Original Message -----
From: "Anders Engström" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 29, 2003 9:02 PM
Subject: [OS-webwork] Strategy for 'confirm-delete'
I'm looking for some suggestions/ideas on how to implement a
'confirm-delete' function in our application.
...
<action name="AddEditEntity" alias="viewEntity">
<view name="success">viewEntity.jsp</view>
<view name="error">redirect.action=listEntities.action</view>
<command name="remove" alias="removeEntity">
<view name="success">redirect.action=listEntities.action</view>
<view name="error">viewEntity.jsp</view>
<view name="verify-remove">confirmRemove.jsp</view>
</command>
</action>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
