[
https://issues.apache.org/jira/browse/ARTEMIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262670#comment-15262670
]
Jonathan S. Fisher commented on ARTEMIS-245:
--------------------------------------------
hmm... actually after reading this:
http://docs.oracle.com/cd/B25221_04/web.1013/b14436/trmgcont.htm
"...through its implementation of the SPI LazyEnlistableConnectionManager
interface, so you can use lazy enlistment with any resource adapter that
implements the LazyEnlistableManagedConnection interface for its managed
connections"
I suspect everything is just fine, but it's up to you... Here's my thoughts:
1) It only says this implementation's interface, not the whole RA
2) The connection manager doesn't implement LazyEnlistableConnectionManager
anyway
3) The goal was just to allow TomEE to do connection tracking, not enable the
lazy optimization.
But even with that, if you uncomfortable with the change, I can implement the
Lazy Optimization per the directions on the API, but I would have no idea how
to test it and that'd leave me a little uneasy.
> Change resource adapter to work with Tomee
> ------------------------------------------
>
> Key: ARTEMIS-245
> URL: https://issues.apache.org/jira/browse/ARTEMIS-245
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 1.0.0, 1.1.0, 1.2.0
> Reporter: clebert suconic
> Fix For: 1.3.0
>
> Attachments: patch.txt
>
>
> It seems that Tomee requires a JMS interface to be returned. We should try
> changing the RA to be compatible with it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
