1<!--$Id: handle.so,v 1.6 2004/08/15 03:22:57 bostic Exp $--> 2<!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> 3<!--See the file LICENSE for redistribution information.--> 4<html> 5<head> 6<title>Berkeley DB Reference Guide: Release 3.2: Java and C++ object reuse</title> 7<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> 8<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> 9</head> 10<body bgcolor=white> 11<table width="100%"><tr valign=top> 12<td><b><dl><dt>Berkeley DB Reference Guide:<dd>Upgrading Berkeley DB Applications</dl></b></td> 13<td align=right><a href="/upgrade.3.2/mutexlock.html"><img src="/images/prev.gif" alt="Prev"></a><a href="/toc.html"><img src="/images/ref.gif" alt="Ref"></a><a href="/upgrade.3.2/notfound.html"><img src="/images/next.gif" alt="Next"></a> 14</td></tr></table> 15<p align=center><b>Release 3.2: Java and C++ object reuse</b></p> 16<p>In previous releases of Berkeley DB, Java DbEnv and Db objects, and C++ 17<a href="/api_cxx/env_class.html">DbEnv</a> and <a href="/api_cxx/db_class.html">Db</a> objects could be reused after they 18were closed, by calling open on them again. This is no longer 19permitted, and these objects no longer allow any operations after a 20close. Applications reusing these objects should be modified to create 21new objects instead.</p> 22<table width="100%"><tr><td><br></td><td align=right><a href="/upgrade.3.2/mutexlock.html"><img src="/images/prev.gif" alt="Prev"></a><a href="/toc.html"><img src="/images/ref.gif" alt="Ref"></a><a href="/upgrade.3.2/notfound.html"><img src="/images/next.gif" alt="Next"></a> 23</td></tr></table> 24<p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> 25</body> 26</html> 27