May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1395?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1395: ---------------------------- Fix Version/s: warp_1.0.0.Alpha3 > 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 > Fix For: warp_1.0.0.Alpha3 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1395?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1395: ---------------------------- Priority: Critical (was: Major) > 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 > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > > 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1396) CommandEventBusService use wrong metadata to match Request URI

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1396?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1396: ---------------------------- Priority: Critical (was: Major) > CommandEventBusService use wrong metadata to match Request URI > -------------------------------------------------------------- > > Key: ARQ-1396 > URL: https://issues.jboss.org/browse/ARQ-1396 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > > canDelegate use request.getServletPath to check if the current request match a given path. > The problem is, pr spec, getServletPath is a empty String when Servlet is mapped to /*, and in this case it's just a Filter. Both getServletPath and getPathInfo are bound to a Servlet. > getServletPath works in JBoss AS 7.1.1, but not in WildFly 8. > getServletPath works in WildFly 8, but not in JBoss AS 7.1.1. > The correct check seems to be: > getRequestURI().endsWith(COMMAND_EVENT_BUS_MAPPING) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1396) CommandEventBusService use wrong metadata to match Request URI

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1396?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1396: ---------------------------- Fix Version/s: warp_1.0.0.Alpha3 > CommandEventBusService use wrong metadata to match Request URI > -------------------------------------------------------------- > > Key: ARQ-1396 > URL: https://issues.jboss.org/browse/ARQ-1396 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Reporter: Aslak Knutsen > Fix For: warp_1.0.0.Alpha3 > > > canDelegate use request.getServletPath to check if the current request match a given path. > The problem is, pr spec, getServletPath is a empty String when Servlet is mapped to /*, and in this case it's just a Filter. Both getServletPath and getPathInfo are bound to a Servlet. > getServletPath works in JBoss AS 7.1.1, but not in WildFly 8. > getServletPath works in WildFly 8, but not in JBoss AS 7.1.1. > The correct check seems to be: > getRequestURI().endsWith(COMMAND_EVENT_BUS_MAPPING) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Aslak Knutsen (JIRA)

[ 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 handled 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. This case the CommandBusService to 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Aslak Knutsen (JIRA)

[ 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1395?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1395: ------------------------------------ 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. This case the CommandBusService to 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1396) CommandEventBusService use wrong metadata to match Request URI

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1396: ---------------------------------- Summary: CommandEventBusService use wrong metadata to match Request URI Key: ARQ-1396 URL: https://issues.jboss.org/browse/ARQ-1396 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha2 Reporter: Aslak Knutsen canDelegate use request.getServletPath to check if the current request match a given path. The problem is, pr spec, getServletPath is a empty String when Servlet is mapped to /*, and in this case it's just a Filter. Both getServletPath and getPathInfo are bound to a Servlet. getServletPath works in JBoss AS 7.1.1, but not in WildFly 8. getServletPath works in WildFly 8, but not in JBoss AS 7.1.1. The correct check seems to be: getRequestURI().endsWith(COMMAND_EVENT_BUS_MAPPING) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1395) CommandBusService is started even tho the test is not a @WarpTest

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-1395: ---------------------------------- Summary: 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-274) The request guard does timeout for delayed requests

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-274?page=com.atlassian.jira.plugin... ] Bernard Labno commented on ARQGRA-274: -------------------------------------- You can also see at https://github.com/blabno/graphene-guard-test/blob/master/src/test/java/p... and https://github.com/blabno/graphene-guard-test/blob/master/src/test/java/p... that no matter how long text we pass to "sendKeys" it will trigger 2 keyup events. (test against commit 14e30170947ba876022b2eb519affc766242211e) > The request guard does timeout for delayed requests > --------------------------------------------------- > > Key: ARQGRA-274 > URL: https://issues.jboss.org/browse/ARQGRA-274 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.0.0.Alpha3 > Reporter: Bernard Labno > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 2.0.0.Alpha5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > In RichFaces, there is request queue which can delay a processing of an user action which avoids overwhelming communication channel. > This is simply the case where request guard should: > * wait specified timeout (by default type "Ajax" timeout) for user action to start AJAX request (xhr.open) > * then wait another timeout (by default type "Ajax" timeout) for AJAX action to complete the request (xhr.readyState == 4) -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013