Does assignment “=” always update the timestamp of a property?
Article ID: KB0089442
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
When an assignment statement such as thisconcept.abc = "test" is not actually updating the property abc; TIBCO BusinessEvents (BE) always updates the timestamp.
Environment:
==========
All OS
All BE Version.
Symptoms:
=========
In BE you can use Instance.PropertyAtom.SetString to update the timestamp when desired or the timestamp will be updated automatically when you use assignment “=” to update the value of a property. When the new value is the same as the previous value, the Instance.PropertyAtom.SetString forces the update of the timestamp.
Resolution:
=========
Assignment “=” always updates the timestamp of the property even if the new value is the same as the previous value. There is not a different assignment “=” and Instance.PropertyAtom.SetString for this.
Description:
============
When an assignment statement such as thisconcept.abc = "test" is not actually updating the property abc; TIBCO BusinessEvents (BE) always updates the timestamp.
Environment:
==========
All OS
All BE Version.
Symptoms:
=========
In BE you can use Instance.PropertyAtom.SetString to update the timestamp when desired or the timestamp will be updated automatically when you use assignment “=” to update the value of a property. When the new value is the same as the previous value, the Instance.PropertyAtom.SetString forces the update of the timestamp.
Resolution:
=========
Assignment “=” always updates the timestamp of the property even if the new value is the same as the previous value. There is not a different assignment “=” and Instance.PropertyAtom.SetString for this.
Issue/Introduction
Does assignment “=” always update the timestamp of a property?
Feedback
Yes
No
Powered by
