May 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Matous Jobanek updated ARQGRA-470: ---------------------------------- Git Pull Request: https://github.com/arquillian/arquillian-graphene/pull/131 > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Pëtr Andreev commented on ARQ-1952: ----------------------------------- [~aslak] I think the ResourceWrapper could be a very useful feature, I even tried to implement [one for Warp|https://github.com/petrandreev/arquillian-extension-warp/blob/ARQ-19...]. But it doesn`t help for the current issue. What I can propose for the solution is to make the [URLResourceResolver|https://github.com/petrandreev/arquillian-core/blob/A...] more cooperative. The whole picture in the environment of Aquillian Core, Warp and Graphene would then look like: 1. ARQ registers the URLResourceProvider 2. Warp overrides the URLResourceProvider by the proxied (ProxyURLProvider) one (and delegates to URLResourceProvider for non-Warp tests) 3. Graphene` [CustomizableURLResourceProvider|https://github.com/petrandreev/arquillian...] is only usable in non-deployment scenarios, so the [GrapheneExtension|https://github.com/petrandreev/arquillian-graphene/blob...] just needs to register it additionally and all tasks for deployments are done by the default URLREsourceProvider [~aslak] and [~lfryc] what do you think about it? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Lukáš Fryč commented on ARQGRA-470: ----------------------------------- Yes, let's remove that definition if that is not required anymore. [~mjobanek] would you try to simply build with the remove dependency management for jboss-logging and if yes, send a PR? > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQGRA-470?page=com.atlassian.jira.plugin... ] Lukáš Fryč updated ARQGRA-470: ------------------------------ Fix Version/s: 2.1-Tracking > Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent > --------------------------------------------------------------------------------------------------- > > Key: ARQGRA-470 > URL: https://issues.jboss.org/browse/ARQGRA-470 > Project: Arquillian Graphene > Issue Type: Bug > Affects Versions: 2.1.0.Alpha2 > Reporter: Matous Jobanek > Fix For: 2.1-Tracking > > > There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: > {code:xml} > <dependency> > <groupId>org.jboss.logging</groupId> > <artifactId>jboss-logging</artifactId> > <version>${version.jboss.logging}</version> > </dependency> > {code} > however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. > see: > [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] > [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1952: ------------------------------------ Wondering if this feature would be helpful in this case; https://github.com/aslakknutsen/arquillian-core/commit/9a1ec4bc1d1f5c8176... > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Pëtr Andreev commented on ARQ-1952: ----------------------------------- I think, I can describe what causing the problem: the new feature for customizable URLs was introduced with [ARQGRA-374|https://issues.jboss.org/browse/ARQGRA-374]. The [GrapheneExtension|https://github.com/arquillian/arquillian-graphene/blob/...] overrides the default _URLResourceProvider_. It works well until Warp comes into the play (which is the case while ITesting the RichFaces): the [WarpExtension|https://github.com/arquillian/arquillian-extension-warp/blo...] overrides the default _URLResourceProvider_ too. So actually both URLProviders coexist in the ServiceRegistry. What happens during the Warp request processing is: while storing the location in [ContextRootStoreInitializer|https://github.com/arquillian/arquillian-grap...] the _ServiceRegistryLoader_ is asked for all available URLProviders and both, the Warp AND Graphene ones, _canProvide_ URL. Since the order of the _Set_ entries returned by _ServiceLoader_ depends on _weather_, the Graphene` _CustomizableURLProvider_ returns the non-proxied URL (port 8080). The suggested solution can be found [here|https://github.com/petrandreev/arquillian-graphene/commit/c8ff5a2096...], it skips the registration of any _CustomizableURLResourceProvider_s in the Warp environment. I think this should not interfere with use cases in the standalone Graphene environment. I can provide a PR. > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQGRA-470) Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent

by Matous Jobanek (JIRA)

Matous Jobanek created ARQGRA-470: ------------------------------------- Summary: Missing version of org.jboss.logging:jboss-logging in org.jboss.arquillian.graphene:graphene-parent Key: ARQGRA-470 URL: https://issues.jboss.org/browse/ARQGRA-470 Project: Arquillian Graphene Issue Type: Bug Affects Versions: 2.1.0.Alpha2 Reporter: Matous Jobanek There in the org.jboss.arquillian.graphene:graphene-parent pom is defined a dependency: {code:xml} <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> <version>${version.jboss.logging}</version> </dependency> {code} however the variable {{version.jboss.logging}} is not defined neither it this pom nor in the parent pom. see: [org.jboss.arquillian.graphene:graphene-parent:2.1.0.Alpha2|https://repo1....] [github|https://github.com/arquillian/arquillian-graphene/blob/master/pom.xml] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1953) Adding attributes file on AsciiDoc header

by Alex Soto (JIRA)

Alex Soto created ARQ-1953: ------------------------------ Summary: Adding attributes file on AsciiDoc header Key: ARQ-1953 URL: https://issues.jboss.org/browse/ARQ-1953 Project: Arquillian Issue Type: Feature Request Components: Extension - Recorder Reporter: Alex Soto Priority: Minor Sometimes you may want to customize the attributes set in AsciiDoc document. For this reason a new attribute called asciiDocAttributesFile is created so when this property is set to a file location, this file will be included using include macro in header. Github issue: https://github.com/arquillian/arquillian-recorder/issues/16 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Pëtr Andreev edited comment on ARQ-1952 at 5/18/15 6:46 PM: ------------------------------------------------------------ [~lfryc] I didn`t inspect the client site yet, do you have any suggestions on the probable cause? was (Author: pjotrovsky): [~lfryc]] I didn`t inspect the client site yet, do you have any suggestions on the probable cause? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one

by Pëtr Andreev (JIRA)

[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.s... ] Pëtr Andreev commented on ARQ-1952: ----------------------------------- [~lfryc]] I didn`t inspect the client site yet, do you have any suggestions on the probable cause? > Warp requests hit the application port instead of LittleProxy`s one > ------------------------------------------------------------------- > > Key: ARQ-1952 > URL: https://issues.jboss.org/browse/ARQ-1952 > Project: Arquillian > Issue Type: Bug > Components: Extension - Warp > Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 > Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 > Reporter: Pëtr Andreev > Attachments: ARQ-1952-failure.log, ARQ-1952-success.log > > > Warp observer intermittently fails while inspecting the requests with: > "There were no requests matched by observer \[containsParameter(XXXX)\] ". > The technical reason for the failure is that the client request hits the original (application server) port and not the [LittleProxy`s|https://github.com/adamfisk/LittleProxy] one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of _HttpFiltersSourceAdapter_ in _DefaultHttpFiltersSource_, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2015