[
https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen edited comment on ARQ-1852 at 9/10/14 8:52 AM:
-------------------------------------------------------------
CommandService is part of Core already. Every Protocol has it's own implementation of
it to allow InContainer to communicate with Client side:
https://github.com/arquillian/arquillian-core/blob/master/container/test-...
E.g. the ServletCommandService from the Servlet Protocol:
https://github.com/arquillian/arquillian-core/blob/master/protocols/servl...
After re-reading, you want the opposite direction? Client to send commands to Container at
any point?
was (Author: aslak):
CommandService is part of Core already. Every Protocol has it's own implementation of
it to allow InContainer to communicate with Client side:
https://github.com/arquillian/arquillian-core/blob/master/container/test-...
E.g. the ServletCommandService from the Servlet Protocol:
https://github.com/arquillian/arquillian-core/blob/master/protocols/servl...
After re-reading, you want the opposite way? Client to send commands to Container at any
point?
Move Warp's CommandService to Protocol
--------------------------------------
Key: ARQ-1852
URL:
https://issues.jboss.org/browse/ARQ-1852
Project: Arquillian
Issue Type: Enhancement
Components: Extension - Warp, Test Protocol SPIs and Implementation
Affects Versions: 1.1.5.Final
Reporter: Emond Papegaaij
Priority: Optional
Warp provides a very nice SPI for running commands remotely. I would love to see this
this SPI become part of the Protocol classes, making it available to all Arquillian code.
I'm writing an extension, which needs to execute some code in the container, but is
triggered on events fired on the client. Warp's CommandService would allow me to do
this, but it only works in Warp tests, which my tests are not. Also, making the code part
of Protocol should remove quite some duplication between Protocol and Warp's
CommandService.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)