[arquillian-issues] [JBoss JIRA] (ARQ-1074) TransactionProvider should be supported on client side

[Jakub Narloch (JIRA)]

    [ https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711820#comment-12711820 ] 

Jakub Narloch commented on ARQ-1074:
------------------------------------

Any idea how to reconcile the registration on the client side with error handling of missing providers on the classpath as done in TransactionHandler#getTransactionProvider?

{code}
 private TransactionProvider getTransactionProvider() {

        try {
            ServiceLoader serviceLoader = serviceLoaderInstance.get();

            TransactionProvider transactionProvider = serviceLoader.onlyOne(TransactionProvider.class);

            if (transactionProvider == null) {
                throw new TransactionProviderNotFoundException(
                        "Transaction provider for given test case has not been found.");
            }

            return transactionProvider;
        } catch (IllegalStateException exc) {
            // thrown if there were multiple providers registered in the context
            throw new TransactionProviderNotFoundException(
                    "More then one transaction provider has been specified.", exc);
        }
    }
{code}
                
> TransactionProvider should be supported on client side
> ------------------------------------------------------
>
>                 Key: ARQ-1074
>                 URL: https://issues.jboss.org/browse/ARQ-1074
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Extension - Transaction
>    Affects Versions: transaction_1.0.0.Alpha1
>            Reporter: Aslak Knutsen
>             Fix For: transaction_1.0.0.next
>
>
> We should support automating TransactionManagement for the Client side as well as for in container. 
> A TransactionProvider could register it self to be in Client context. This will allow for embedded service containers to provide their own hooks without reloading the AuxiliaryArchives as it's done by Remote Containers.

--
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