[
https://issues.apache.org/jira/browse/DELTASPIKE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-507:
----------------------------------------
Attachment: DELTASPIKE-507_with_cleanup_01.patch
> UserTransaction not available in WAS 8.0 and 8.5 during EJB CMT call
> --------------------------------------------------------------------
>
> Key: DELTASPIKE-507
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-507
> Project: DeltaSpike
> Issue Type: Bug
> Components: JPA-Module
> Affects Versions: 0.5
> Environment: IBM Websphere 8.0.0.6 and 8.5.5.1
> Reporter: Stefan Strobl
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 0.6
>
> Attachments: DELTASPIKE-507_with_cleanup_01.patch,
> DS_509_tested_on_was.patch
>
>
> It seems that due to different interpretations of the EE Spec WAS behaves
> differently when calling a CDI bean from a CMT EJB. While TomEE for example
> gives access to the UserTransaction, WAS will not (@Resource inject fails as
> well as lookup via JNDI "java:comp/UserTransaction". This behavior currently
> (0.6-SNAPSHOT) results in a NameNotFoundException in
> BeanManagedUserTransactionStrategy#resolveUserTransaction()
> To provide a workaround for WAS the idea would be to resort back to
> TransactionSynchronisationRegistry which also exposes the current Transaction
> Status (even on WAS) and should therefore be sufficient to implicitely "join"
> the currently ongoing transaction. A Status != ACTIVE should probably still
> result in an error indicating probably a misconfigured RESOURCE_LOCAL
> Datasource
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
