[
http://www.stripesframework.org/jira/browse/STS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter closed STS-36.
-------------------------
> Event Chaining
> --------------
>
> Key: STS-36
> URL: http://www.stripesframework.org/jira/browse/STS-36
> Project: Stripes
> Issue Type: New Feature
> Components: ActionBean Dispatching
> Reporter: Greg Hinkle
> Assignee: Tim Fennell
> Fix For: Release 1.0
>
> Attachments: UseActionBeanTag.java
>
>
> How do you feel about Event chaining? Here's my dilemma.
> List page - Project List
> Form is ProjectListForm and includes the typical list filter + pagination
> stuff (a few filter keys, start, size)
> Edit Page - Project Detail
> Form is ProjectForm and includes all project details for editing
> Normally, i'd have view helper for the list page and an action for the view +
> edit on the details page, but it'd be nice if I didn't have to do request
> parsing myself for the additional form elements of the ProjectListForm after
> submission of the ProjectForm's Save method (which fowards to the
> "ProjectList.jsp".
> Options:
> I could stick the list details in the session, but that's nasty and not
> multi-window safe.
> I could keep using a view helper, parsing numbers myself to get the start
> record and fill in the 3 different filter fields.
> Or, we could support event chaining. (I used to be against this, so tell me
> if you hate it.) If I could return new
> ChainEventResolution("project/ProjectListForm","List"); from my
> Project.save() event i'd be nice and happy. The dispatcher would rerun the
> binding for the second form and pass off to my new ProjectListActionBean
> that'd use all its preset ProjectFilter elements to create the proper list.
> Then I never have to parse the request again!
> I'm sure this has downsides, maybe the session is the right place for these,
> and maybe my list data is more sensibly loaded in a view helper
> (architecturally speaking), but its one of those situations where I will have
> both links and form buttons going to the same event (list projects). That is
> because to get to the list, you enter your filter criteria and press search.
> Then you might hit the link to resort by a different column or the paginate
> -> next button to see the next set of results. Thoughts?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
