[
https://issues.jboss.org/browse/ISPN-1168?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on ISPN-1168:
------------------------------------
I think the
synchronisationRegistrationPolicy="fully.qualified.name.RegistrationPolicy"
doesn't account for passing the TransactionSynchronizationRegistry instance in, it
only identifies the desire to use a configured TransactionSynchronizationRegistry. Which
needs to be injected still.
I think the policy for TransactionSynchronizationRegistry, should be built in and know how
to access the injected TransactionSynchronizationRegistry.
Stuart came up with this patch last night
(
https://github.com/scottmarlow/infinispan/commit/ff6a0050d5f3bde4b6f66193...)
that is a start (doesn't take the suggestions from this jira into account yet because
they didn't exist yet).
If I can get past this scala related build error, I'll take a shot at what we
discussed above (I wanted to mention the change from Stuart Douglas in case it helps us).
The build error that I'm hitting is here
http://pastie.org/2040797
Support for interposed synchronization
--------------------------------------
Key: ISPN-1168
URL:
https://issues.jboss.org/browse/ISPN-1168
Project: Infinispan
Issue Type: Task
Affects Versions: 5.0.0.CR4
Reporter: Scott Marlow
Assignee: Mircea Markus
Fix For: 5.0.0.CR5
Support for interposed synchronization should be configurable to avoid the following
exception:
http://pastie.org/2035067
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira