In current WebWork the main focus is on "actions". I miss the EXPLICIT implementation of the concept "dialog".
In my view a dialog is a finite state machine implementation (FSM), an action causes a state transition in the active state machine(s) (the (s) is because an application will usually contain layered state machines). I think this relates to my previous posting on "reusing actions" as current WebWork registers "actions" with their follow-up in "views.properties", in the FSM model views.properties would register "action bindings", which are unique (state machine plus action). I posted the above before, later I found an interesting link to a ready-to-run and free implementation of a FSM as dialog controller: http://www.jstatemachine.org/ In my view this approach is very clean and appropriate. ------------------------------------------------------- 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
