Persisting a domain model with JDO 2.0 - POJOs in Action: Developing Enterprise Applications with Lightweight Frameworks - page 167

makePersistent(po);
int poId = po.getId();
}
});
}
JDOPendingOrderPersistenceTests extends JDOPersistenceTests , which is
an ORMU nit class. The test instantiates a PendingOrder and saves it in the data-
base by calling makePersistent() , which is defined by JDOPersistenceTests
and calls JdoTemplate.makePersistent() .
A more thorough test would create a PendingOrder , update it, and delete it.
Listing 5.2 shows an example of such a test. This creates a PendingOrder , updates
it in different ways, and then deletes it. Each step of the test is a separate database
transaction that creates, deletes, and updates objects in the database.

Listing 5.2 JDOPendingOrderPersistenceTests

public class JDOPendingOrderPersistenceTests extends
JDOPersistenceTests {

private String poId;

private String restaurantId;

public void testPendingOrder() throws Exception {

createPendingOrder();

createRestaurant();

updateDeliveryInformation();

updateRestaurant();

updateQuantities();

changeQuantities();

deletePendingOrder();

}

B Creates and saves
PendingOrder

private void createPendingOrder() {
doWithTransaction(new TxnCallback() {
public void execute() throws Exception {
PendingOrder po = new PendingOrder();
makePersistent(po);
poId = po.getId();