May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1353) Warp: propagate manager's context to proxy correctly

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1353?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1353: ---------------------------- Fix Version/s: warp_1.0.0.Alpha3 (was: warp_1.0.0.Beta1) > Warp: propagate manager's context to proxy correctly > ---------------------------------------------------- > > Key: ARQ-1353 > URL: https://issues.jboss.org/browse/ARQ-1353 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Priority: Minor > Fix For: warp_1.0.0.Alpha3 > > > Warp's proxy current serves in no context - we should use at least following hack to propagate context: > https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/... -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1353) Warp: propagate manager's context to proxy correctly

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1353?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1353: ---------------------------- Sprint: Warp Alpha3 > Warp: propagate manager's context to proxy correctly > ---------------------------------------------------- > > Key: ARQ-1353 > URL: https://issues.jboss.org/browse/ARQ-1353 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Priority: Minor > Fix For: warp_1.0.0.Beta1 > > > Warp's proxy current serves in no context - we should use at least following hack to propagate context: > https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/... -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1324) Warp HTTP request header size beyond reasonable limits

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1324?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1324: ---------------------------- Sprint: Critical Issues (was: Critical Issues, Warp Alpha3) > Warp HTTP request header size beyond reasonable limits > ------------------------------------------------------ > > Key: ARQ-1324 > URL: https://issues.jboss.org/browse/ARQ-1324 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha2 > Environment: JBoss AS 7.1.1.Final > Reporter: Marek Schmidt > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > HTTP servers usually limit HTTP header size of the requests (e.g. 8192 bytes for AS7) and refuse to accept requests with larger headers with "Invalid request" errors. Such limit is easily exceeded by a non-trivial Inspection object. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1325) Warp: replace piggy-backing on request/response with direct test->filter communication

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1325?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1325 started by Lukáš Fryč. > Warp: replace piggy-backing on request/response with direct test->filter communication > -------------------------------------------------------------------------------------- > > Key: ARQ-1325 > URL: https://issues.jboss.org/browse/ARQ-1325 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We can do similar processing as we did with CommandService here: > https://github.com/arquillian/arquillian-extension-warp/blob/aa0745237f5d... > The CommandService communicates with the WarpFilter asynchronously and its requests are not processed directly, they delegates to the request-serving routine. > ---- > This way, Warp could: > 0. request is issued against proxy > 1. catch the request on the proxy > 2. register the RequestPayload (with Inspection) in the registry via the WarpFilter (under generated request-specific UUID) > 3. proxy passes request to WarpFilter with a request header which contains UUID > 4. WarpFilter associates Inspection from the registry with given request > 5. Warp proceeds with a request inspection > 6. response is commited and sent back to the proxy (with given UUID as response header) > 7. proxy catches the response and obtains ResponsePayload (with Inspection result) from the WarpFilter (using UUID) > 8. proxy processes the ResponsePayload and passes the request to the client > 9. the client processes response > This would avoid a need for piggy-backing on request/response, so it will also eliminate need for response-wrapping (NonWritingResponse). -- 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

10 years, 11 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č resolved ARQ-1395. ----------------------------- Resolution: Done Starting the service only when @WarpTest annotation is present. > 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 > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

10 years, 11 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... ] Work on ARQ-1395 started by Lukáš Fryč. > 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 > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

10 years, 11 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č reassigned ARQ-1395: ------------------------------- Assignee: Lukáš Fryč > 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 > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1368) Warp: reverse order of chaining of request builder

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1368?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved ARQ-1368. ----------------------------- Resolution: Done > Warp: reverse order of chaining of request builder > -------------------------------------------------- > > Key: ARQ-1368 > URL: https://issues.jboss.org/browse/ARQ-1368 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > If we have following observer: > {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code} > we want observe first request matching criteria - (URI containing given string), however that is not what happens: > the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...]. > ---- > Reverse the order of evaluation in order to fix semantics of fluent API. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1368) Warp: reverse order of chaining of request builder

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1368?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated ARQ-1368: ---------------------------- Description: If we have following observer: {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code} we want observe first request matching criteria - (URI containing given string), however that is not what happens: the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...]. ---- Reverse the order of evaluation in order to fix semantics of fluent API. was: If we are following observer: {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code} we want observe first request matching criteria - (URI containing given string), however that is not what happens: the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...]. ---- Reverse the order of evaluation in order to fix semantics of fluent API. > Warp: reverse order of chaining of request builder > -------------------------------------------------- > > Key: ARQ-1368 > URL: https://issues.jboss.org/browse/ARQ-1368 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > If we have following observer: > {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code} > we want observe first request matching criteria - (URI containing given string), however that is not what happens: > the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...]. > ---- > Reverse the order of evaluation in order to fix semantics of fluent API. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1368) Warp: reverse order of chaining of request builder

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1368?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1368 started by Lukáš Fryč. > Warp: reverse order of chaining of request builder > -------------------------------------------------- > > Key: ARQ-1368 > URL: https://issues.jboss.org/browse/ARQ-1368 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Warp > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: warp_1.0.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > If we are following observer: > {code}.observe(request().uri().contains("__richfacesPushAsync").index(1)){code} > we want observe first request matching criteria - (URI containing given string), however that is not what happens: > the {{index(1)}} calls method [{{addFilter}}|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Alpha2/impl/src/main/java/org/jboss/arquillian/warp/impl/client/filter/http/DefaultHttpFilterBuilder.java#L111] which allows chaining, but this chain [evaluates the newly passed filter before it evaluates previous one|https://github.com/arquillian/arquillian-extension-warp/blob/1.0.0.Al...]. > ---- > Reverse the order of evaluation in order to fix semantics of fluent API. -- 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

10 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013