[arquillian-issues] [JBoss JIRA] (ARQ-1852) Move Warp's CommandService to Protocol

[Emond Papegaaij (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij updated ARQ-1852:
---------------------------------
    Description: 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.  (was: Warp provides are very nice SPI for running commands remotely. It would be very nice if this SPI became 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. Also, making the code part of Protocol should remove quite some duplication between Protocol and Warp's CommandService.)


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