September 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1789) add tomcat 8 managed and/or remote container adapters

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.s... ] Ian Brandt reassigned ARQ-1789: ------------------------------- Assignee: Ian Brandt > add tomcat 8 managed and/or remote container adapters > ----------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Reporter: Peter Butkovic > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1789) add tomcat 8 managed and/or remote container adapters

by Ian Brandt (JIRA)

[ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.s... ] Ian Brandt updated ARQ-1789: ---------------------------- Fix Version/s: tomcat_1.0.0.Final > add tomcat 8 managed and/or remote container adapters > ----------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Reporter: Peter Butkovic > Assignee: Ian Brandt > Fix For: tomcat_1.0.0.Final > > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Emond Papegaaij commented on ARQ-1852: -------------------------------------- We are running selenium test with Arquillian with custom Wicket integration. These test run on the server to be able to access the Wicket state from within the selenium test itself. In this setting, I would like these commands for two purposes: reporting and resource management. The first I was able to solve with commands from the server to the client. But the second still remains open. Opening a new browser and setting up the user session is quite expensive compared to the actual test cases so I want to pool browsers with active sessions. However, these need to be closed after the last case. Because Arquillian triggers AfterSuite after every case, I can't use this event in the container. I would like to send a command from the client on AfterSuite to close all open browsers. In general, I think the ability to send commands from the client to the container can be useful in many other cases. From what I've seen in Warp's code, is that they implemented a separate servlet filter to implement this. A lot of code is duplicated between SevletProtocol and warp, including for example the code to get the right URL, causing bugs like ARQ-1592. > 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)

11 years, 6 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1852: ------------------------------------ At which points do the Client know? The normal execution flow in Arquillian is to for each @Test on client side execute the full In Container cycle(BeforeSuite/BeforeClass/Before/Test...), then take the result from container and move on. This is per say single threaded, so the Client can't really send anything at 'random' points to the container. It only sends one 'command'; run the complete test. It's from within the container side you can send fine grained commands back to the client within any of the events(BeforeSuite, BeforeClass.. ).. If you can explain in more detail what you're trying to do. > 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)

11 years, 6 months

1
0
0 / 0

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

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Emond Papegaaij commented on ARQ-1852: -------------------------------------- Yes, I Observe several events at the client side and need to execute code at the server in response. Warp has a CommandService, which, if I'm not mistaken, is used to execute its inspections. In our case, I need to container to generate a report at certain points and send it to the client. Only the client knows when. The easiest way to implement this, is using a servlet, but that would duplicate a lot of work already done in the protocols and in Warp. > 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)

11 years, 6 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen edited comment on ARQ-1852 at 9/10/14 8:52 AM: ------------------------------------------------------------- CommandService is part of Core already. Every Protocol has it's own implementation of it to allow InContainer to communicate with Client side: https://github.com/arquillian/arquillian-core/blob/master/container/test-... E.g. the ServletCommandService from the Servlet Protocol: https://github.com/arquillian/arquillian-core/blob/master/protocols/servl... After re-reading, you want the opposite direction? Client to send commands to Container at any point? was (Author: aslak): CommandService is part of Core already. Every Protocol has it's own implementation of it to allow InContainer to communicate with Client side: https://github.com/arquillian/arquillian-core/blob/master/container/test-... E.g. the ServletCommandService from the Servlet Protocol: https://github.com/arquillian/arquillian-core/blob/master/protocols/servl... After re-reading, you want the opposite way? Client to send commands to Container at any point? > 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)

11 years, 6 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen edited comment on ARQ-1852 at 9/10/14 8:52 AM: ------------------------------------------------------------- CommandService is part of Core already. Every Protocol has it's own implementation of it to allow InContainer to communicate with Client side: https://github.com/arquillian/arquillian-core/blob/master/container/test-... E.g. the ServletCommandService from the Servlet Protocol: https://github.com/arquillian/arquillian-core/blob/master/protocols/servl... After re-reading, you want the opposite way? Client to send commands to Container at any point? was (Author: aslak): CommandService is part of Core already. Every Protocol has it's own implementation of it to allow InContainer to communicate with Client side: https://github.com/arquillian/arquillian-core/blob/master/container/test-... E.g. the ServletCommandService from the Servlet Protocol: https://github.com/arquillian/arquillian-core/blob/master/protocols/servl... ? > 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)

11 years, 6 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1852: ------------------------------------ CommandService is part of Core already. Every Protocol has it's own implementation of it to allow InContainer to communicate with Client side: https://github.com/arquillian/arquillian-core/blob/master/container/test-... E.g. the ServletCommandService from the Servlet Protocol: https://github.com/arquillian/arquillian-core/blob/master/protocols/servl... ? > 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)

11 years, 6 months

1
0
0 / 0

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

by Emond Papegaaij (JIRA)

[ https://issues.jboss.org/browse/ARQ-1852?page=com.atlassian.jira.plugin.s... ] 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)

11 years, 6 months

1
0
0 / 0

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

by Emond Papegaaij (JIRA)

Emond Papegaaij created ARQ-1852: ------------------------------------ Summary: 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 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. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 September 2014