[
https://issues.apache.org/jira/browse/GERONIMO-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dain Sundstrom closed GERONIMO-2715.
------------------------------------
Resolution: Fixed
Committed to trunk (2.0-M2) in revision 494503.
Committed to branches/1.2 in revision 494504.
> Connector Lazy Activation
> -------------------------
>
> Key: GERONIMO-2715
> URL: https://issues.apache.org/jira/browse/GERONIMO-2715
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: connector
> Reporter: Dain Sundstrom
> Assigned To: Dain Sundstrom
> Fix For: 1.2, 2.0-M2
>
>
> The ConnectionTrackingCoordinator now supports lazy connector activation via
> the optional 'lazyActivation' GBean attribute. Currently, the CTC tracks all
> connections opened in a component instance and when the component is
> reentered, all previously open connections are reconnected. The new optional
> mode waits to reconnect connection until they are actually used. If the
> connection is not used, then it is not connected. This is accomplished by
> proxying the Connection instance. The proxy implements all interfaces that
> the Connection implemented, so the proxy can still be cast to a vendor
> specific connection interface (think Oracle JDBC Connection sub-interface).
> One very nice side effect of this feature is that is reduces the burden to
> track open connections on a per component basis. Without lazy activation,
> each component instance must track previously open connections, so that they
> can be reconnected. With lazy activation, the proxy is performing this
> tracking, so the component is free to not track that information. Of course,
> components will still want to demarc component entrance and exit so the
> Connector system can return handles to the connection pool (for connectors
> that support disassociation), but that is a much simpler task. This
> relaxation of the requirements for a component integrator is very important
> to OpenEJB3 as we now use JPA for CMP and will not be able to implement all
> of the connector tracking rules that we were when we had complete control
> over the CMP implementation. This will also make integration with component
> frameworks Spring much easier since connection tracking can be optional.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
