[
https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s...
]
Emond Papegaaij commented on ARQ-1852:
--------------------------------------
Yes, I Observe several events at the client side and need to execute code at the server in
response. Warp has a CommandService, which, if I'm not mistaken, is used to execute
its inspections. In our case, I need to container to generate a report at certain points
and send it to the client. Only the client knows when. The easiest way to implement this,
is using a servlet, but that would duplicate a lot of work already done in the protocols
and in Warp.
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)