Kris,
Thanks again for your help with this!
If you want to help, you could provide native support for the
TransactionSynchronizationRegistry as an alternative to
TransactionManager. We created a new issue for that here:
https://jira.jboss.org/jira/browse/JBRULES-2322
Thanks,
Allen
-----Original Message-----
From: Kris Verlaenen [mailto:kris.verlaenen@cs.kuleuven.be]
Sent: Friday, October 30, 2009 10:10 AM
To: Rules Users List; Allen Day
Subject: Re: [rules-users] JTA question
Quoting Allen Day <DayAK(a)ldschurch.org>:
Looking at the source code you referenced it appears the
TransactionManager interface is only being used to register a
synchronization. Is there any other code you're aware of that uses
the EnvironmentName.TRANSACTION_MANAGER?
No, this class handles the transaction
management.
Is it possible for us to provide
an alternative implementation of the SingleSessionCommandService?
Sure, we use a
provider strategy for getting the actual implementation.
So you can use JPAKnowledgeService.setJPAKnowledgeServiceProvider to
configure another provider. If you look at
JPAKnowledgeServiceProviderImpl, it simply uses a property to specify
the command service, so your own provider impl. should change that to
use your custom implementation:
props.setProperty( "drools.commandService",
"org.drools.persistence.session.SingleSessionCommandService" );
Let us know how it goes, or if there is anything we could improve in our
implementation to make this easier for you.
Kris
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm
NOTICE: This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient, please contact the
sender by reply email and destroy all copies of the original message.