You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Craig Russell (JIRA)" <ji...@apache.org> on 2006/10/04 21:58:20 UTC
[jira] Updated: (JDO-432) Test for behaviour of null passed to
detachCopy(), makePersistent(), etc
[ http://issues.apache.org/jira/browse/JDO-432?page=all ]
Craig Russell updated JDO-432:
------------------------------
Fix Version/s: JDO 2 maintenance release 1
Assignee: Michelle Caisse
> Test for behaviour of null passed to detachCopy(), makePersistent(), etc
> ------------------------------------------------------------------------
>
> Key: JDO-432
> URL: http://issues.apache.org/jira/browse/JDO-432
> Project: JDO
> Issue Type: Task
> Components: tck20
> Affects Versions: JDO 2 final
> Reporter: Andy Jefferson
> Assigned To: Michelle Caisse
> Priority: Minor
> Fix For: JDO 2 maintenance release 1
>
>
> The JDO2 spec adequately defines (section 12.6.0 "Null Management") behaviour when null values are passed in to the PersistenceManager methods makePersistent, detachCopy, etc but there doesnt seem to be a test for these situations currently. JPOX 1.1.2 on calling detachCopy(null) actually throws an NPE, which is outside of spec ... now fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira