#5 User-provided log messages NOT recorded...

closed-fixed
None
7
2008-02-06
2007-02-19
Sam
No

...for object-level API-M Methods.

Discussion

  • Sam

    Sam - 2007-03-12

    Logged In: YES
    user_id=1709161
    Originator: YES

    Normally, API-M methods that do object modification will result in a new audit
    record in the object. This is true for all component (datastream and
    disseminator) methods, but in the case of the following methods, the logMessage
    is not recorded anywhere:

    - ingestObject
    - modifyObject
    - purgeObject

    Note that for purgeObject, it makes no sense to put the audit record in the
    object. Something else needs to be done, like writing it to the system log.

     
  • Chris Wilper

    Chris Wilper - 2007-10-16
    • priority: 5 --> 7
     
  • Bill Branan

    Bill Branan - 2008-01-25
    • assigned_to: nobody --> bbranan
     
  • Bill Branan

    Bill Branan - 2008-02-05

    Logged In: YES
    user_id=1987639
    Originator: NO

    Fixed bug in tasks 145707 (trunk) and 145936 (maintenance-2.2), ingestObject and modifyObject now create audit records which include the provided log message. The log message for purgeObject is written to the server log. In order to allow the choice to create an audit record on object ingest or not, an audit record will only be created if a log message is provided. If no log message is provided on the call, no audit record is created.

    Audit records are now created for all API-M methods which update the object with the exception of addRelationship and purgeRelationship. Some discussion will be necessary to determine if providing audit records on these methods is appropriate.

    All API-M methods in 3.0 now log a completion notice at the INFO level which includes any provided log message (this is only done for purgeObject in 2.2.)

     
  • Chris Wilper

    Chris Wilper - 2008-02-06
    • status: open --> closed-fixed
     
  • Chris Wilper

    Chris Wilper - 2008-02-06

    Logged In: YES
    user_id=189298
    Originator: NO

    committed fixes to trunk r6557 and maintenance-2.2 r6558

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks