Interface | Description |
---|---|
com.mchange.util.CommandLineParser |
Use com.mchange.v2.cmdline.CommandLineUtils instead
|
com.mchange.util.ObjectCache |
use com.mchange.v1.util.ObjectCache
|
com.mchange.v1.util.RunnableQueue |
use com.mchange.v2.async.RunnableQueue
|
com.mchange.v1.lang.holders.ThreadSafeBooleanHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeByteHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeCharHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeDoubleHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeFloatHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeIntHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeLongHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.ThreadSafeShortHolder |
use classes in com.mchange.v2.holders
|
Class | Description |
---|---|
com.mchange.v1.util.AbstractResourcePool |
use com.mchange.v1.resourcepool.AbstractResourcePool
|
com.mchange.lang.ArrayUtils |
use com.mchange.v1.util.ArrayUtils
|
com.mchange.v1.util.CleanupUtils |
use functions in per-closeable resouce utility classes
|
com.mchange.util.impl.CommandLineParserImpl |
Use com.mchange.v2.cmdline.CommandLineUtils instead
|
com.mchange.v1.db.sql.ConnectionEventSupport |
use com.mchange.v2.c3p0.util.ConectionEventSupport
|
com.mchange.io.impl.DirectoryDescendingFileFinderImpl |
use com.mchange.v2.io.DirectoryDescentUtils
|
com.mchange.v1.db.sql.DriverManagerDataSource |
use com.mchange.v2.c3p0.DriverManagerDataSource
|
com.mchange.v2.encounter.EqualityEncounterCounter |
-- Use of WeakHashMap can't properly guarantee counts with equality semantics,
as an Object can be encounted garbage collected, then re-encountered with
no apparent history. Clients should explicit choose the semantics they want
via WeakEqualityEncounterCounter or StrongEqualityEncounterCounter
|
com.mchange.v2.encounter.IdentityEncounterCounter |
use WeakIdentityEncounterCounter (name changed to emphasize for library users
that they need to understand whether implementations are weak or strong
to avoid accidental reference retention in strong counters)
|
com.mchange.v2.codegen.IndentedWriter |
-- please user com.mchange.v2.io.IndentedWriter
|
com.mchange.io.InputStreamUtils |
-- use com.mchange.v1.io.InputStreamUtils
|
com.mchange.v1.util.MapUtils |
Oops! Doesn't conform to Map equals() / hashCode() contract!
|
com.mchange.v1.lang.NullUtils |
use com.mchange.v2.ObjectUtils.eqOrBothNull()
|
com.mchange.lang.ObjectUtils |
use com.mchange.v2.ser.SerializableUtils;
|
com.mchange.io.OutputStreamUtils |
use com.mchange.v1.io.OutputStreamUtils
|
com.mchange.v2.naming.ReferenceableUtils.ExtractRec |
nesting references seemed useful until I realized that
references are Serializable and can be stored in a BinaryRefAddr.
Oops.
|
com.mchange.io.SerializableUtils |
use com.mchange.v2.ser.SerializableUtils
|
com.mchange.v1.util.SimpleRunnableQueue |
use com.mchange.v2.async.SimpleRunnableQueue
|
com.mchange.v2.async.SimpleRunnableQueue |
CarefulRunnableQueue is better.
|
com.mchange.net.SocketUtils |
use com.mchange.net.v1.net.SocketUtils
|
com.mchange.v1.db.sql.SqlUtils |
use com.mchange.v2.sql.SqlUtils
|
com.mchange.lang.StringUtils |
use com.mchange.v2.lang.StringUtils (JDK 1.4+)
|
com.mchange.v1.lang.holders.SynchronizedBooleanHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedByteHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedCharHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedDoubleHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedFloatHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedIntHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedLongHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.SynchronizedShortHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v2.lang.TypeResolutionUtils |
delete me
|
com.mchange.v1.lang.holders.VolatileBooleanHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.VolatileByteHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.VolatileCharHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.VolatileFloatHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.VolatileIntHolder |
use classes in com.mchange.v2.holders
|
com.mchange.v1.lang.holders.VolatileShortHolder |
use classes in com.mchange.v2.holders
|
com.mchange.io.WriterUtils |
use com.mchange.v1.io.WriterUtils
|
Exceptions | Description |
---|---|
com.mchange.lang.PotentiallySecondaryException |
jdk 1.4 mow includes this idea as part of the standard
Throwable/Exception classes.
|
com.mchange.io.UnsupportedVersionException |
use com.mchange.v2.ser.UnsupportedVersionException
|
Constructor | Description |
---|---|
com.mchange.v1.util.UnexpectedException(Throwable, String) |