Uploaded image for project: 'Causeway'
  1. Causeway
  2. CAUSEWAY-1709

[INVALID] Inconsistent handling of commands vs auditing for objects implementing HasTransactionId

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Invalid
    • 1.15.0
    • 2.0.0-M5
    • Core
    • None

    Description

      Noticed that if

      ApplicationUser#updateEmailAddress(...)

      with

      isis.services.audit.objects=none
      isis.services.command.actions=none

      then do get a Command persisted, but don't get any audit records persisted.

      The auditing behaviour is correct, but the command behaviour is wrong.

      What seems to happen is that no CommandFacet is installed (ActionAnnotationFacetFactory#processCommand), and then in the ObjectMemberAbstract because there is no command facet it defaults to

      "// if no facet, assume do want to execute right now, but only persist (eventually) if hinted."

      My guess is that the hinting does occur (PersistenceSession#completeCommandFromInteractionAndClearDomainEvents as objects are dirtied.

      Attachments

        Activity

          People

            danhaywood Daniel Keir Haywood
            danhaywood Daniel Keir Haywood
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: