Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <30811631.1165517361779.JavaMail.jira@brutus>
Date: Thu, 7 Dec 2006 10:49:21 -0800 (PST)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (GERONIMO-434) Connection factories extracted from
 conceptually wrong gbean
In-Reply-To: <1607726730.1099588593392.JavaMail.apache@nagoya>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-434?page=all ]

David Jencks updated GERONIMO-434:
----------------------------------

    Fix Version/s: Wish List
                       (was: 1.x)

> Connection factories extracted from conceptually wrong gbean
> ------------------------------------------------------------
>
>                 Key: GERONIMO-434
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-434
>             Project: Geronimo
>          Issue Type: Improvement
>          Components: connector
>    Affects Versions: 1.0-M4
>            Reporter: David Jencks
>         Assigned To: David Jencks
>             Fix For: Wish List
>
>
> Currently connection factories/datasources (or their proxies) are obtained from the JCAManagedConnectionFactory gbean.  Since there is a ConnectionFactory/Datasource gbean for the jsr-77 requirements, it would make more sense to obtain the connection factory/datasource from there.  This would have the additional feature of allowing one to set up several connection factories under different names that all use the same ConnectionManager and ManagedConnectionFactory.  This would for instance let you set up separately named QueueConnectionFactory and TopicConnectionFactory that share the same connections: named appropriately, this can let you leave out resource-refs in plans for apps that call the factories different names.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira