Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Message-ID: <1086253253.1129648610019.JavaMail.jira@ajax.apache.org>
Date: Tue, 18 Oct 2005 17:16:50 +0200 (CEST)
From: "Michael Bouschen (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Subject: [jira] Commented: (JDO-154) Add tests for getUserObject,
 putUserObject, removeUserObject
In-Reply-To: <685102194.1128259073921.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/JDO-154?page=comments#action_12332371 ] 

Michael Bouschen commented on JDO-154:
--------------------------------------

I looked at the patch. I just have one question: would it make sense to call putUserObject a second time for the same key and verify that the second call overwrite the existing value for the key? 

> Add tests for getUserObject, putUserObject, removeUserObject
> ------------------------------------------------------------
>
>          Key: JDO-154
>          URL: http://issues.apache.org/jira/browse/JDO-154
>      Project: JDO
>         Type: Test
>   Components: tck20
>     Reporter: Craig Russell
>     Assignee: Craig Russell
>  Attachments: JDO-154.patch
>
> Assertion 12.11-1 PersistenceManager APIs
> Object putUserObject(Object key, Object value); This method models the put method of Map. The current value associated with the key is returned and replaced by the parameter value. If the parameter value is null, the implementation may remove the entry from the table of managed key/value pairs 
> Object removeUserObject(Object key); This method models the remove method of Map. The current value associated with the key is re turned and removed 
> Object getUserObject(Object key); This method models the get method of Map. The current value associated with the key is returned. If the key is not found in the table, null is returned.

-- 
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