[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-3358) Enable JTATransactionFactory and JTATransaction factory to work without JNDI

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole updated HHH-3358:
--------------------------------

    Description: 
Per issue HHH-3110, a JNDI lookup occurs when attempting to acquire a UserTransaction.  This causes problems for 'standalone' JTA TransactionManagers that don't require JNDI.

By abstracting the JNDI lookup to a method, that method could be overridden to acquire the UserTransaction in an implementation specific manner if so desired.

I'll attach the patch after I create the issue.

<note>
As discussed on dev list, this is actually a misnomer since by definition of the JTA specification a JTA compliant implementation would be required to publish its UserTransaction into JNDI.  However, it was decided that this is worthwhile enough to allow because quite a few TM implementations do not follow that part of the spec to allow for "out of container" operation.
</note> 

  was:
Per issue HHH-3110, a JNDI lookup occurs when attempting to acquire a UserTransaction.  This causes problems for 'standalone' JTA TransactionManagers that don't require JNDI.

By abstracting the JNDI lookup to a method, that method could be overridden to acquire the UserTransaction in an implementation specific manner if so desired.

I'll attach the patch after I create the issue.


> Enable JTATransactionFactory and JTATransaction factory to work without JNDI
> ----------------------------------------------------------------------------
>
>                 Key: HHH-3358
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3358
>             Project: Hibernate3
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.2.x
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>             Fix For: 3.2.x, 3.3.0.CR2
>
>         Attachments: HHH-3358-2.patch, HHH-3358.patch
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Per issue HHH-3110, a JNDI lookup occurs when attempting to acquire a UserTransaction.  This causes problems for 'standalone' JTA TransactionManagers that don't require JNDI.
> By abstracting the JNDI lookup to a method, that method could be overridden to acquire the UserTransaction in an implementation specific manner if so desired.
> I'll attach the patch after I create the issue.
> <note>
> As discussed on dev list, this is actually a misnomer since by definition of the JTA specification a JTA compliant implementation would be required to publish its UserTransaction into JNDI.  However, it was decided that this is worthwhile enough to allow because quite a few TM implementations do not follow that part of the spec to allow for "out of container" operation.
> </note> 

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