11:42 a.m.
Aslak Knutsen created ARQ-1074:
----------------------------------
Summary: 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
1:02 p.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
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
10:46 a.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on ARQ-1074:
------------------------------------
You would need to add an extract check. If @Test is runOnClient or LocalProtocol(used by
embedded containers) and Class/Method is transactional, then verify existence of
TxProvider
Similar to this:
https://github.com/arquillian/arquillian-core/blob/master/container/test-...
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
11:53 a.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
Jakub Narloch updated ARQ-1074:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request:
https://github.com/arquillian/arquillian-extension-transaction/pull/2
Pull request linked.
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
12:17 p.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen updated ARQ-1074:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Assignee: Jakub Narloch
Resolution: Done
pushed upstream
https://github.com/arquillian/arquillian-extension-transaction/commit/b20...
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
Assignee: Jakub Narloch
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:02 p.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen updated ARQ-1074:
-------------------------------
Fix Version/s: transaction_1.0.0.Alpha2
(was: transaction_1.0.0.next)
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
Assignee: Jakub Narloch
Fix For: transaction_1.0.0.Alpha2
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
[
https://issues.jboss.org/browse/ARQ-1074?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen closed ARQ-1074.
------------------------------
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
Assignee: Jakub Narloch
Fix For: transaction_1.0.0.Alpha2
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4460
days inactive
4536
days old
arquillian-issues@lists.jboss.org
6 comments
2 participants
participants (2)
-
Aslak Knutsen (JIRA) -
Jakub Narloch (JIRA)