[
https://issues.apache.org/jira/browse/QPID-7203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299490#comment-15299490
]
Keith Wall commented on QPID-7203:
----------------------------------
I made a simple change to resolve the problem, special casing
createdBy/createdDate/lastUpdateBy/lastUpdateDate in the same way as
AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore already do for their
storable derived attributes. I think in the long term we should look again at
how these attributes types are represented in the model. I think the code would
be cleaner if ManagedAttribute had a flag userMaintainable. If this flag were
set false, ACO would know to reject values from the outside but would still
persist/resolve the attribute in the normal way.
> Model loses audit information
> ------------------------------
>
> Key: QPID-7203
> URL: https://issues.apache.org/jira/browse/QPID-7203
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.0.1
> Reporter: Keith Wall
>
> The Broker is supposed to save audit information on each object:
> {{createdBy}}, {{createdDate}}, {{lastUpdatedBy}}, {{lastUpdatedDate}}. This
> feature is broken and has been so since at least 0.30.
> The values are persisted properly to the message store, but on recovery, they
> only make it as far as the attribute map backing the configured object. The
> mechanics of ACO fails to reunite the attribute value with the field
> underlying each attribute. As a result the audit trail is unreliable.
> The problem would affect any storable derived attribute. Other storable
> derived attributes AutoGeneratedSelfSignedKeyStore and SiteSpecificTrustStore
> use {{postResolve}} to reunite the attribute with the field.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
