[
https://issues.apache.org/jira/browse/GERONIMO-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904257#action_12904257
]
David Jencks commented on GERONIMO-434:
---------------------------------------
rev 990869 trunk.
ee jndi requires a new instance be created on each lookup. This doesn't fit
with osgi jndi which aggressively caches services from service factories. So
the osgi jndi is getting a single cached connection factory from the
JCAConnectionFactory whereas ee jndi is getting a new one each lookup from
ConnectionManager gbean.
> 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-M1
>
>
> 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.
