Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.4.2-RC2, 5.4.2
    • Component/s: Audit
    • Tags:
    • Upgrade notes:
      Hide

      The Seam bean has not been changed so you can continue using the same method, although you are advised to switch to PageProvider and ContentViews since the Seam Bean APi will be deprecated in next release.

      The only impacting change is that the LinkedDocument pojo has been migrated from audit-client to audit-api so that the Provider can computed the linked document from the comment.
      This means you can now use the PageProvider to get the LogEntry and also have the pre-processed comments.

      This should not impact the existing code since this change is completly transparent from the xhtml point of view and LinkedDocument was mainly a helper class used to expose the content to the xhtml views ...

      Show
      The Seam bean has not been changed so you can continue using the same method, although you are advised to switch to PageProvider and ContentViews since the Seam Bean APi will be deprecated in next release. The only impacting change is that the LinkedDocument pojo has been migrated from audit-client to audit-api so that the Provider can computed the linked document from the comment. This means you can now use the PageProvider to get the LogEntry and also have the pre-processed comments. This should not impact the existing code since this change is completly transparent from the xhtml point of view and LinkedDocument was mainly a helper class used to expose the content to the xhtml views ...

      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.