[
https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen commented on ARQ-1852:
------------------------------------
At which points do the Client know?
The normal execution flow in Arquillian is to for each @Test on client side execute the
full In Container cycle(BeforeSuite/BeforeClass/Before/Test...), then take the result from
container and move on. This is per say single threaded, so the Client can't really
send anything at 'random' points to the container. It only sends one
'command'; run the complete test. It's from within the container side you can
send fine grained commands back to the client within any of the events(BeforeSuite,
BeforeClass.. )..
If you can explain in more detail what you're trying to do.
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)