|
If you were logged in you would be able to see more operations.
|
|
|
db4o Core
Created: 04/Dec/07 04:38 PM
Updated: 03/Jan/08 08:56 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
7.0.19
|
| Fix Version/s: |
7.0.24
|
|
|
Time Tracking:
|
|
Original Estimate:
|
Not Specified
|
|
|
Remaining Estimate:
|
0h
|
|
|
Time Spent:
|
5.77h
|
|
|
|
| Peers: |
Adriano Verona
|
| Order: |
3
|
| Original IDS Estimate: |
1 IDD
|
| Resolution Date: |
03/Jan/08 01:52 PM
|
| First Response Date: |
03/Jan/08 01:52 PM
|
| PSC Recommendation: |
A3
|
| Labels: |
|
| Participants: |
Andy 2003 and Rodrigo B. de Oliveira
|
| Number of Attachments: |
1
|
| Number of Comments: |
3
|
|
The TA-Instrumantation doesn't instrument setter methods which accessing fields. In following case this results in a bug:
1. Loading an Object fom DB
2. setting a field
3. reading the Object via getter
Currently objects get activated in Step 3. All settings b/4 Step 3 get overwritten.
Solution: objects need to get activated even b/4 write access.
A patch with testcase + fix is attached
|
|
Description
|
The TA-Instrumantation doesn't instrument setter methods which accessing fields. In following case this results in a bug:
1. Loading an Object fom DB
2. setting a field
3. reading the Object via getter
Currently objects get activated in Step 3. All settings b/4 Step 3 get overwritten.
Solution: objects need to get activated even b/4 write access.
A patch with testcase + fix is attached |
Show » |
|
Bug
Closed
Critical
[TA] Setter Methods doesn't get instrumented for transparent activation
