geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-434) Connection factories extracted from conceptually wrong gbean
Date Tue, 23 Mar 2010 19:30:27 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-434.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Wish List)
                   3.0

finally implemented as part of runtime TransacitonSupport.  rev 926678.

> Connection factories extracted from conceptually wrong gbean
> ------------------------------------------------------------
>
>                 Key: GERONIMO-434
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-434
>             Project: Geronimo
>          Issue Type: Improvement
>          Components: connector
>    Affects Versions: 1.0-M4
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message