10 Replies Latest reply on May 11, 2006 12:19 PM by Clebert Suconic

    JBAS-1974: Remote Connection Factory Usage

    Weston M. Price Master

      TODO:

      Refactor org.jboss.resource.adapter.jdbc.remote to

      org.jboss.resource.adapter.remote (or something equivalent).

      Refector the WrapperDataSourceService into something more generic. First off, change the name, in many ways it doesn't make a lot of sense. Maybe something along the lines of RemoteConnectionFactoryService.

      Do we want to keep the relationship with the ConnectionFactoryBindingService, or do we want to break this out and create a RemoteConnectionFactoryBindingService, or even augment the existing ConnectionFactoryBindingService to allow for this capability?

      As mentioned on JIRA, proxy generation should be allowed for all non-serializable types on the CF/Connection interface. The existing service has an example of doing this, and it shouldn't be too difficult to make this generic for any CF.

      I think it is a good idea to tie client lease times to the client transaction timeout.

      This issue actually in some ways ties into the new deployment stuff being that I am assuming we are going to use the same 'useJavaContext' mechanism for this.

      If I missed anything, let me know.