JCA 1.0 does not provide any mechanisms for informing an adapter of a restart, an UNDEPLOY, or a REDEPLOY. Furthermore, JCA 1.0 does not specify whether ManagedConnectionFactory (MCF) objects are instantiated or released.
Since an adapter usually reserves external resources automatically (for example, inbound connection, threads, to process sender messages), it must also know when to release these resources and complete sender processing.
Using the finalize() method is not sufficient because it is not called until minutes or even hours later when the Java virtual machine garbage collector is running.
If the Adapter Framework is based on JCA 1.0, you must note the following implementation considerations if your adapter supports the sender direction:
The example adapter contains the implementation of start() and stop().
Open the example adapter and search for the character string SPIManagedConnectionFactory.java:CS_MCFASTART and SPIManagedConnectionFactory.java: CS_MCFASTOP.
This step is displayed in the example adapter.
Open SPIManagedConnectionFactory.java and search for the character string CS_MCFPROPS.