
| Key: |
JDO-425
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Ilan Kirsh
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
In order to support non binary compatibility JDO implementations that do not have control on each field access (reflective implementations) the following tests that are based on immediate field access tracking have to be modified:
1. IsTransactionalFalse.testIsTransactionalFalse (field access in line 86 is not detected immediately)
2. MakeTransactionalPriorToTransactionRolledback.testTransactionalInst (field modifications in lines 115, 117 are not detected immediately)
3. InstanceLifecycleListenerLoad.testLoad (field access in line 101 is not detected immediately)
4. NoAccessToFieldsAfterPredelete.test (field access in line 115, for instance, is not detected immediately)
5. StateTransitions.test (operations in lines 472-496 are not detected immediately)
6. WhenNontransactionalReadIsFalse.test (field access in line 116, for instance, is not detected immediately)
Accordingly the specification should be updated in a way that state transitions, exceptions and events that are based on immediate field access tracking should be optional or more flexible in timing, at least for non binary compatibility implementations. For instance, the events firePreDirty and firePostDirty may be fired only when it is detected the an object became dirty in the following call to isDirty, commit or flush (this for example does not require changing the TCK).
|
|
Description
|
In order to support non binary compatibility JDO implementations that do not have control on each field access (reflective implementations) the following tests that are based on immediate field access tracking have to be modified:
1. IsTransactionalFalse.testIsTransactionalFalse (field access in line 86 is not detected immediately)
2. MakeTransactionalPriorToTransactionRolledback.testTransactionalInst (field modifications in lines 115, 117 are not detected immediately)
3. InstanceLifecycleListenerLoad.testLoad (field access in line 101 is not detected immediately)
4. NoAccessToFieldsAfterPredelete.test (field access in line 115, for instance, is not detected immediately)
5. StateTransitions.test (operations in lines 472-496 are not detected immediately)
6. WhenNontransactionalReadIsFalse.test (field access in line 116, for instance, is not detected immediately)
Accordingly the specification should be updated in a way that state transitions, exceptions and events that are based on immediate field access tracking should be optional or more flexible in timing, at least for non binary compatibility implementations. For instance, the events firePreDirty and firePostDirty may be fired only when it is detected the an object became dirty in the following call to isDirty, commit or flush (this for example does not require changing the TCK). |
Show » |
| There are no subversion log entries for this issue yet.
|
|