Does this mean that there is not as yet a solution to my problem? Or does it mean I should
tackle my problem differently in the mean time? If so, would you be able to kindly provide
an example of how you would tackle based on the following scenario:
At the product layer we have say, a page that allows you to update a customers details.
The outcomes are "update", "delete" and "view history". A
particular client wants to redefine the process and page flow slightly: They want to; add
a new outcome to the page "add note", remove an outcome "view history"
and modify the process/page flow for the delete outcome to capture a deletion reason (so,
an interim page in the flow for that other process). Essentually:
Change:
/user_info.seam
| -> update
| -> delete
| -> confirm (/delete_user_confirm.seam)
| -> view history (/view_user_history.seam)
To:
/user_info.seam
| -> update
| -> delete
| -> delete reason (/site/delete_user_reason.seam)
| -> confirm (/delete_user_confirm.seam)
| -> add note (/site/add_user_note.seam)
It's a fairly stupid example, and would probably be tackled differently/better in a
real layout - But, the example demonstrates all layers that I need to be able to
override.
Cheers,
David
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059488#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...