[
https://issues.jboss.org/browse/WFLY-11166?page=com.atlassian.jira.plugin...
]
David Lloyd commented on WFLY-11166:
------------------------------------
bq. David Lloyd So all the existing Service injection should be ripped out?
Yes. I didn't rip it all out initially because in addition to the (useless) injection
of the relevant values, the service dependencies add an ordering facet which would entail
a separate stage of testing. That, combined with my unwillingness to move it all to
cap/req in one giant refactor (and uncertainty as to how to handle having a global default
with the option of a local override), led me to do a minimal refactor which included
leaving the compatibility-only services intact and, in some cases, still in use.
+1 to your points though.
Create capabilities for TransactionManager, UserTransaction and
TransactionSynchronizationRegistry
--------------------------------------------------------------------------------------------------
Key: WFLY-11166
URL:
https://issues.jboss.org/browse/WFLY-11166
Project: WildFly
Issue Type: Sub-task
Components: Management, Transactions
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
See
https://issues.jboss.org/browse/WFLY-9587?focusedCommentId=13647549&p...
in the parent issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)