Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.6-RC1, 5.6
    • Component/s: Seam / JSF UI

      Description

      When an Exception is thrown by a Listener marking the TX as Rollback only we end up with a DocumentModel in a Dirty state : it contains un commited changes.

      This is good as long as we stay on the initial screen that generated the save tentative. But if we navigate to a new screen (i.e. new tab) we should automatically refetch the DocumentModel from the repository to avoid displaying un commited data in the UI.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.