| Ilan Kirsh (JIRA) 2006-09-13, 1:11 am |
| [ http://issues.apache.org/jira/brows...action_12434343 ]
Ilan Kirsh commented on JDO-419:
--------------------------------
Hi Craig,
Your last comment is very interesting. I didn't know that this is the new policy. Actually ObjectDB 2.0 supports dual mode - enhancement when available (but with no binary compatibility) and reflection as a backup for persistence capable classes that are
not enhanced.
Currently, out of the 445 TCK tests that ObjectDB passes - 6 tests fail in reflection mode:
1. IsTransactionalFalse.testIsTransactionalFalse (access in line 86 is not detected)
2. MakeTransactionalPriorToTransactionRolle
dback.testTransactionalInst (modifications in lines 115, 117 are not detected)
3. InstanceLifecycleListenerLoad.testLoad (access in line 101 is not detected)
4. NoAccessToFieldsAfterPredelete.test (access in line 115, for instance, is not detected)
5. StateTransitions - as discussed in this issue.
6. WhenNontransactionalReadIsFalse.test (access in line 116, for instance, is not detected)
My plan was to offer the reflection mode as a non compatible extension, but if JDO can support reflection mode and these tests can be fixed it could be much better.
Regards, Ilan
> StateTransitions incorrectly asserts that field access in a deleted instance will throw an exception
> ----------------------------------------------------------------------------------------------------
>
> Key: JDO-419
> URL: http://issues.apache.org/jira/browse/JDO-419
> Project: JDO
> Issue Type: Bug
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Marc Prud'hommeaux
> Assigned To: Craig Russell
> Priority: Minor
> Attachments: JDO-419.patch
>
>
> The series of states marked with "read field with active datastore transaction" (element 14 of the "transitions" field of org.apache.jdo.tck.lifecycle.StateTransitions) asserts that accessing a field of a deleted instance will throw an exception. Howeve
r, this is not mandated by the spec, only suggested that it might happen. Section 5.5.6 reads: "Any other access to persistent fields is not supported and might throw a JDOUserException".
> The only easy fix is to just remove the "read field with active datastore transaction" test specifications.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|