[ 
https://issues.apache.org/jira/browse/OPENEJB-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578958#action_12578958
 ] 

David Jencks commented on OPENEJB-702:
--------------------------------------

This patch isn't quite right.  The containerId should be used as the name, not 
xaResource.toString().

The use of NamedXAResource is needed for any use of the geronimo transaction 
manager, not just geronimo, so the dependency may be more general than implied 
by the comments in the patch.

Since transacted message delivery to mdbs depends on this patch I hope it can 
be included in openejb 3.0.

> Transaction Logging not working in OpenEJB for MDBs
> ---------------------------------------------------
>
>                 Key: OPENEJB-702
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-702
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: container system
>    Affects Versions: 3.0
>         Environment: All
>            Reporter: Manu T George
>             Fix For: 3.0.x
>
>         Attachments: OPENEJB-702.patch
>
>
>   I was investigating GERONIMO-3354. Found that the exception
> getting thrown was due to an XAResource getting passed to the the
> geronimo transaction manager instead of a NamedXAResource .
> To fix this we need to change the method  
> public MessageEndpoint createEndpoint(XAResource xaResource) throws 
> UnavailableException in
> org.apache.openejb.core.mdb.EndpointFactory
> In this method in the case of using the Geronimo Transaction Manager we need 
> to pass a NamedXAResource if we need transaction logging to function.
> Directly passing a NamedXAResource will fix this problem at the openEJB side 
> for now but we need to bring in a layer of abstraction since the 
> NamedXAResource is a geronimo TM specific class and in OpenEJB standalone the 
> TM must be pluggable.
> For the time being its acceptable to use NamedXAResource. 
> This requires a fix in AMQ also to work . The JIRA in question is 
> https://issues.apache.org/activemq/browse/AMQ-1438

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to