java.so

berkeley db 4.6.21的源码。berkeley db是一个简单的数据库管理系统

m4_comment([$Id: java.so,v 1.21 2006/08/24 16:32:33 bostic Exp $])

define(BDB_LOC, ..)

m4_ref_title(Upgrading m4_db Applications,
    Release 4.2: Java,,
    upgrade.4.2/intro, upgrade.4.2/queue)

m4_p([dnl
There are a number of major changes to the Java support in m4_db in this
release.  Despite that we have tried to make this a bridge release, a
release where we don't require you to change anything.  We've done this
using the standard approach to deprecation in Java.  If you do not
compile with deprecation warnings on, your existing sources should work
with this new release with only minor changes despite the large number
of changes.  Expect that in a future release we will remove all the
deprecated API and only support the new API names.])

m4_p([dnl
This is a list of areas where we have broken compatibility with the
4.1 release.  In most cases it is a name change in an interface class.
])
m4_bulletbegin

m4_bullet([dnl
m4_bold([DbAppDispatch.app_dispatch(DbEnv,Dbt,DbLsn,int)])m4_p([is now:
m4_bold([DbAppDispatch.appDispatch(DbEnv,Dbt,DbLsn,int)])])])

m4_bullet([dnl
m4_bold([DbAppendRecno.db_append_recno(Db,Dbt,int)])m4_p([is now:
m4_bold([DbAppendRecno.dbAppendRecno(Db,Dbt,int)])])])

m4_bullet([dnl
m4_bold([DbBtreeCompare.bt_compare(Db,Dbt,Dbt)])m4_p([is now:
m4_bold([DbBtreeCompare.compare(Db,Dbt,Dbt)])])])

m4_bullet([dnl
m4_bold([DbBtreeCompare.dup_compare(Db,Dbt,Dbt)])m4_p([is now:
m4_bold([DbBtreeCompare.compareDuplicates(Db,Dbt,Dbt)])])])

m4_bullet([dnl
m4_bold([DbBtreePrefix.bt_prefix(Db,Dbt,Dbt)])m4_p([is now:
m4_bold([DbBtreePrefix.prefix(Db,Dbt,Dbt)])])])

m4_bullet([dnl
m4_bold([DbSecondaryKeyCreate.secondary_key_create(Db,Dbt,Dbt,Dbt)])m4_p([is now:
m4_bold([DbSecondaryKeyCreate.secondaryKeyCreate(Db,Dbt,Dbt,Dbt)])])])

m4_bulletend

m4_p([dnl
The 4.2 release of m4_db requires at minimum a J2SE 1.3.1 certified Java
virtual machine and associated classes to properly build and execute.
To determine what version virtual machine you are running, enter:])

m4_indent([java -version])

m4_p([dnl
at a command line and look for the version number.  If you need to
deploy to a version 1.1 or 1.0 Java environment, it may be possible to
do so by not including the classes in the com.sleepycat.bdb package
in the Java build process (however, that workaround has not been tested
by us).])

m4_p([dnl
A few inconsistent methods have been cleaned up (for example, Db.close
now returns void; previously, it returned an int which was always zero).
The synchronized attributed has been toggled on some methods -- this is
an attempt to prevent multithreaded applications from calling close or
similar methods concurrently from multiple threads.])

m4_p([dnl
The m4_db API has up until now been consistent across all language APIs.
Although consistency has is benefits, it made our Java API look strange to
Java programmers.  Many methods have been renamed in this release of the
Java API to conform with Java naming conventions.  Sometimes this renaming
was simply "camel casing", sometimes it required rewording.  The mapping
file for these name changes is in m4_path(dist/camel.pm).  The Perl script
we use to convert code to the new names is called
m4_path(dist/camelize.pl), and may help with updating Java applications
written for earlier versions of m4_db.])

m4_p([dnl
m4_db has a number of places where as a C library it uses function pointers
to move into custom code for the purpose of notification of some event.  In
Java the best parallel is the registration of some class which implements
an interface.  In this version of m4_db we have made an effort to make those
interfaces more uniform and predictable.  Specifically, DbEnvFeedback is now
DbEnvFeedbackHandler, DbErrcall is DbErrorHandler and DbFeedback is
DbFeedbackHandler.  In every case we have kept the older interfaces and the
older registration methods so as to allow for backward compatibility in this
release.  Expect them to be removed in future releases.])

m4_p([dnl
As you upgrade to this release of m4_db you will notice that we have
added an entirely new layer inside the package com.sleepycat.bdb.  This
was formerly the Greybird project by Mark Hayes.  Sleepycat Software and
Mark worked together to incorporate his work.  We have done this in
hopes of reducing the learning curve when using m4_db in a Java project.
When you upgrade you should consider switching to this layer as over
time the historical classes and the new bdb package classes will be more
and more integrated providing a simple yet powerful interface from Java
into the m4_db library.])

m4_p([dnl
m4_db's Java API is now generated with m4_linkweb(http://www.swig.org, SWIG).
The new Java API is significantly faster for many operations.])

m4_p([dnl
Some internal methods and constructors that were previously public have
been hidden or removed.])

m4_p([Packages found under com.sleepycat are considered different APIs into
the m4_db system.  These include the core db api (com.sleepycat.db), the
collections style access layer (com.sleepycat.bdb) and the now relocated XA
system (com.sleepycat.xa).])

m4_page_footer