Yeah, doesn't yet, but the plan is to add that in soon. Tonight I'll make the code quicker and then start incorporating Rickards ideas.
-Pat ----- Original Message ----- From: "Mike Cannon-Brookes" <[EMAIL PROTECTED]> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Sent: Monday, December 30, 2002 3:07 PM Subject: Re: [OS-webwork] Rethink > >>> My favourite usecase is the show-edit-update-show usecase. Which means > >>> having the need to pass the primary key of the object updated to the > >>> action show which is the view of the Update action. Views.proptiers > >>> whould look like that: > >>> > >>> Show.success=show.xslt > >>> Update.success=Show.action > >> > >> I would personally prefer that Update redirects to Show instead, because > >> otherwise a refresh will do the update again. The browser location > >> should never point to an action that "does things". > > > > Yes, you're right, but the point is that one need to pass some data (the > > key) to the redirect action. There two ways, doing it automatically or > > explicitely. > > Philipp, > > I'm fairlu sure Xwork does this already (and if not yet, it certainly will > do it). > > Update.success=Show.action?id=$id > > where $id is pulled from Update.getId() > > -mike > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
