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