[
https://issues.jboss.org/browse/ARQ-1395?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen edited comment on ARQ-1395 at 5/28/13 1:10 AM:
-------------------------------------------------------------
This issue becomes obvious if you run Warp against WildFly 8a1. While the
CommandBusService handles 404 responses by ignoring them (this is what JBoss AS 7.1.1
return on a missing mapping), WildFly 8a1 on the other hand return a 405 Method not
allowed. 405 is not ignored so the CommandBusService throw an Exception.
was (Author: aslak):
This issue becomes obvious if you run Warp against WildFly 8a1. While the
CommandBusService handles 404 responses by ignoring them (this is what JBoss AS 7.1.1
return on a missing mapping), WildFly 8a1 on the other hand return a 405 Method not
allowed. 405 is not handled so the CommandBusService throw an Exception.
CommandBusService is started even tho the test is not a @WarpTest
-----------------------------------------------------------------
Key: ARQ-1395
URL:
https://issues.jboss.org/browse/ARQ-1395
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha2
Reporter: Aslak Knutsen
By having Warp on CP, even tho the current test is not marked with @WarpTest, the
CommandBusService is still started and attempts to communicate with the server.
--
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