[ https://issues.jboss.org/browse/JBTM-973?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-973: ------------------------------- Summary: Allow lifecycle events to be handled by remote services (was: Allow a Client to remote WS be a lifecycle handler) Description: The lifecycleClass attribute on @ServiceRequest and @ParticipantService needs to support remote services, such as EJB or Web services. This allows the events to be handled in a remote container. We need to decide how and what context is passed to the remote service. Clearly the remote service needs some context to know what action to take. However, simply flowing the TX context may not be appropriate as the lifecycle methods will be invoked during termination of the protocol. was: This method can be called from a web service method while a transaction is active to notify the framework that no changes have been made during execution of the service method. This is a useful alternative to annotating the ServiceRequest as ReadOnly as it allows the business logic to decide at runtime if modifications were made. {code} public interface Control { public void readOnly(); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBTM-973?page=com.atlassian.jira.plugin.s... ] Paul Robinson updated JBTM-973: ------------------------------- Component/s: TXFramework -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira