# Deprecated API

## Contents

- Deprecated Methods
- Deprecated Constructors

- Deprecated Methods
  Method and Description
  org.jboss.jca.adapters.jdbc.WrappedResultSet.getBigDecimal(int, int)
  org.jboss.jca.adapters.jdbc.WrappedCallableStatement.getBigDecimal(int, int)
  org.jboss.jca.adapters.jdbc.WrappedResultSet.getBigDecimal(String, int)
  org.jboss.jca.adapters.jdbc.WrappedResultSet.getUnicodeStream(int)
  org.jboss.jca.adapters.jdbc.WrappedResultSet.getUnicodeStream(String)
  org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setAsciiStream(int, InputStream, int)
  org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.setUnicodeStream(int, InputStream, int)
  org.jboss.jca.adapters.jdbc.CachedPreparedStatement.setUnicodeStream(int, InputStream, int)
  org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.setXADataSourceProperties(String) this method requires the internal usage of a synchronized map, and will only work with objects created using the deprecated `XAManagedConnectionFactory.XAManagedConnectionFactory()` constructor. Because this can lead to a deadlock when comparing two instances of this class, prefer to define the data source properties at the `XAManagedConnectionFactory.XAManagedConnectionFactory(Map)` constructor instead.

- Deprecated Constructors
  Constructor and Description
  org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory() this constructor internally requires the use of synchronized map instance. This type of map can cause deadlocks when comparing two connection factories. For that reason, prefer to use `XAManagedConnectionFactory.XAManagedConnectionFactory(Map)` instead.

Copyright © 2014 IronJacamar (http://www.ironjacamar.org)