[
https://issues.jboss.org/browse/WFLY-7337?page=com.atlassian.jira.plugin....
]
Michael Musgrove edited comment on WFLY-7337 at 3/10/17 12:38 PM:
------------------------------------------------------------------
[~dmlloyd] This list of requirements refer to state changes for both transactions and
resources. Please could provide more detail about why these are needed (preferably on an
event by event basis).
Also you say that the list is incomplete, do you have a view about which kind of future
event may be of interest.
And finally how does this requirement relate to WFTC?
was (Author: mmusgrov):
[~dmlloyd] This list of requirements refer to state changes in a transactions and in
resources. Please could provide more detail about why these are needed (preferably on an
event by event basis). Also you say that the list is incomplete, do you have a view about
which kind of future event may be of interest.
Introduce an authorization SPI
------------------------------
Key: WFLY-7337
URL:
https://issues.jboss.org/browse/WFLY-7337
Project: WildFly
Issue Type: Enhancement
Components: Transactions
Reporter: David Lloyd
Assignee: Amos Feng
We need an SPI that can be invoked to authorize state changes in a transaction. The
method(s) should make it clear in some way which operation is being authorized, and it
must run from the same thread as the thread which instigates the state change.
It must be possible to register an implementation of the SPI when the container starts up
or acquires the transaction manager.
The operations that should provide authorization checks include, but are not limited to:
* begin
* rollback
* prepare
* forget
* commit (one or two phase)
* recover
Thanks!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)