[jbossts-issues] [JBoss JIRA] (JBTM-465) Consider allowing JDBCImple to manage connection lifecycles

[Mauro Molinari (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739832#comment-12739832 ] 

Mauro Molinari commented on JBTM-465:
-------------------------------------

Hi Tom,
please let me understand something. From JBTM-1230 I understand that JDBC connections for the Object Store are now retrieved using JNDI, is this correct?

If so, as I already stated already in other circumstances, this is a problem for us, since we're using JBoss TS embedded in an application which is meant to work outside a JEE environment. We would need to setup a fake JNDI repository with Spring to let the object store find JDBC connections.
Do you confirm this? Or is there an alternative way to still provide connections without JNDI?

If not, I personally consider this, together with the push towards the mandatory use of a JCA connector (in place of the plain JDBC implementation) in JBoss TS 5.x, a step backward. Please note that I've not followed this evolution so tightly, but this is what I understood based on the feedback I received on the bugs I opened myself (and for some of which I also contributed with patches that were never integrated).

Thanks in advance.
                
> Consider allowing JDBCImple to manage connection lifecycles
> -----------------------------------------------------------
>
>                 Key: JBTM-465
>                 URL: https://issues.jboss.org/browse/JBTM-465
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Resource Manager
>    Affects Versions: 4.5.0
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>             Fix For: 4.17.3, 5.0.0.M2
>
>
> JDBCImple assumes that the JDBCAccess class manages the lifecycle of connections it returns.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira