[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2101) Improve ConversationStack component by filtering based on view-ids
Pete Muir (JIRA)
jira-events at lists.jboss.org
Wed Jan 30 05:50:00 EST 2008
[ http://jira.jboss.com/jira/browse/JBSEAM-2101?page=all ]
Pete Muir updated JBSEAM-2101:
> Improve ConversationStack component by filtering based on view-ids
> Key: JBSEAM-2101
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2101
> Project: JBoss Seam
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 2.0.0.CR2
> Reporter: Jacob Orshalick
> Priority: Minor
> Fix For: 2.1.x
> The application I am currently developing follows the following Form scenario:
> 1. User selects a DataModel element for editing which takes them to view editDataModelSelection.xhtml .
> 2. User makes changes to the DataModelSelection.
> 3. User selects an associated Object for editing which takes the user to sub-view editAggregateObject.xhtml
> 4. User makes changes to associated object and submits those changes.
> 5. This takes the user back to editDataModelSelection.xhtml view where the changes to the associated object are shown updated to the DataModelSelection.
> 5. User submits the changes to the DataModelSelection which persists both DataModelSelection changes and associated object changes as well.
> A conversation is nested when the user accesses view editAggregateObject.xhtml . This allows a user to back-button to the editDataModelSelection.xhtml prior to editing the aggregate object without causing state inconsistencies between what the user sees and what actually persists on submit.
> The trouble is the display of breadcrumbs through the ConversationStack. When the user traverses the following path:
> view editDataModelSelection.xhtml -> action(editAssociatedObject) conversation nested here
> -> view editAggregateObject.xhtml -> action(submitChanges)
> -> view editDataModelSelection.xhtml
> In this scenario, the breadcrumbs by default are displayed as:
> Edit Data Model Selection | Edit Data Model Selection
> This makes sense due to the fact that the nested conversation has the same view-id as the outer conversation. This continues the more times the user edits an associated object. The implementation I am using filters ConversationEntries from the ConversationStack based on the view-id so that the breadcrumbs are simply displayed as:
> Edit Data Model Selection
> regardless of the nested ConversationEntries in this scenario. It is requested that the ConversationStack be filtered based on view-id to provide this as default behavior. Thanks.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues