[
https://issues.jboss.org/browse/JBTM-1722?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-1722:
----------------------------------------
I have added 2 quickstarts showcasing the integration API:
https://github.com/jbosstm/quickstart/tree/master/rest-tx/service/service2
https://github.com/jbosstm/quickstart/tree/master/rest-tx/recovery/recovery2
These parallel the same examples that use the standard RESTAT api.
I am undecided as to whether having an example showing integration with wildfly is useful
since it should be simply a case of taking one of the existing examples and deploying it
as a war into wildfly. NB currently all of the quickstarts run on Grizzly with the
coordinator deployed to wildfly so perhaps for completeness it could be worthwhile.
REST-AT participant support framework should have associated
quickstarts
------------------------------------------------------------------------
Key: JBTM-1722
URL:
https://issues.jboss.org/browse/JBTM-1722
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: REST
Reporter: Michael Musgrove
Assignee: Gytis Trikleris
JBTM-1365 introduced the RTS wildfly subsystem and an interface for simplifying
participant registration into a REST-AT transaction by providing callbacks for
prepare/commit/rollback. We need some quickstarts that show how to use it:
- a standalone example similar to
https://github.com/jbosstm/quickstart/tree/master/rest-tx/service showing the difference
between the two approaches to building services
- showing integration with wildfly
- one for recovery
If we want to split the work between engineers that would be fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira