April 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-856) Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-856: ----------------------------------- Summary: Embedded GlassFish adapter may use an incorrect HTTP port when a custom domain configuration XML file is used Key: ARQ-856 URL: https://issues.jboss.org/browse/ARQ-856 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Vineet Reynolds The embedded GlassFish container uses the default HTTP bind port of 8181, even though the user-supplied domain configuration XML file may specify a different HTTP port. This results in the following exception being thrown when the Arquillian client attempts to execute a test: {code} ... INFO: WELD-000900 SNAPSHOT 9 Apr, 2012 11:06:12 AM com.sun.enterprise.web.WebApplication start INFO: WEB0671: Loading application [test] at [/test] 9 Apr, 2012 11:06:13 AM org.glassfish.deployment.admin.DeployCommand execute INFO: test was successfully deployed in 18,014 milliseconds. java.net.SocketException: Unexpected end of file from server at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766) at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1195) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.execute(ServletMethodExecutor.java:206) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.access$000(ServletMethodExecutor.java:43) at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor$1.run(ServletMethodExecutor.java:99) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) {code} Note that the deployment is successful, but the {{HTTPContext}} returned by the embedded GlassFish adapter contains the wrong port information. In this case, the http-listener-1/http-listener-2 combo was registered in domain.xml to listen on 8080/8181. When Arquillian established a connection to port 8181, the container obviously did not respond to plain text HTTP traffic, and quite obviously the client errored out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

2
4
0 / 0

[JBoss JIRA] (ARQ-824) Verify Arquillian can run on JDK 1.5

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-824: --------------------------------- Summary: Verify Arquillian can run on JDK 1.5 Key: ARQ-824 URL: https://issues.jboss.org/browse/ARQ-824 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR7 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Final Setting compiler options target/source to 1.5 is not enough to verify that the code can actually run on JDK 1.5 since it ignores API changes. To avoid forcing developers to have JDK 1.5 installed to compile, we can add e.g. the Animal Sniffer Maven Plugin to verify using usage of JDK based on known api signatures. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

4
10
0 / 0

[JBoss JIRA] Created: (ARQ-77) Support @EJB injection

by Andrew Lee Rubinger (JIRA)

Support @EJB injection ----------------------- Key: ARQ-77 URL: https://jira.jboss.org/jira/browse/ARQ-77 Project: Arquillian Issue Type: Feature Request Components: OpenEJB Containers Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name). Note that portable JNDI is under java:global, so only accessible to local JVMs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

5
16
0 / 0

[JBoss JIRA] (ARQAJO-118) Support Sizzle locators with Selenium 2

by Lukáš Fryč (Created) (JIRA)

Support Sizzle locators with Selenium 2 --------------------------------------- Key: ARQAJO-118 URL: https://issues.jboss.org/browse/ARQAJO-118 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Reporter: Lukáš Fryč Fix For: 2.0-Tracking -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
28
0 / 0

[JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown when a test errors out

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-837: ----------------------------------- Summary: Managed GlassFish container does not shutdown when a test errors out Key: ARQ-837 URL: https://issues.jboss.org/browse/ARQ-837 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: glassfish_1.0.0.CR3 Reporter: Vineet Reynolds When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message: {{quote}} The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration {{quote}} The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
8
0 / 0

[JBoss JIRA] (ARQ-796) Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-796: ----------------------------------- Summary: Remove the GlassFishRestDeploymentAppender from the GlassFish container adapter Key: ARQ-796 URL: https://issues.jboss.org/browse/ARQ-796 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: GlassFish Containers Reporter: Vineet Reynolds Priority: Minor The GlassFishRestDeploymentAppender does not appear to serve any purpose. Although it is implemented as an auxiliary archive appender, it does not appear to be used to enhance the deployment archive. It assumes the responsibility of enhancing the archive with TestEnrichers, but this is already done by the TestEnricher extensions themselves. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ARQAJO-45) Provide automatic escapes for JQuery/other locator strategy dangerous characters

by Karel Piwko (JIRA)

Provide automatic escapes for JQuery/other locator strategy dangerous characters -------------------------------------------------------------------------------- Key: ARQAJO-45 URL: https://issues.jboss.org/browse/ARQAJO-45 Project: Arquillian Ajocado Issue Type: Enhancement Affects Versions: 1.0.0.Alpha2 Reporter: Karel Piwko Assignee: Lukas Fryc Fix For: 1.0.0.Alpha3 Selenium command processor behaves differently on different Selenium version. Consolidate the behavior and provide automatic escapes for dangerous characters according to the locator strategy. Implementation note: SimplifiedFormatter couldn't be used to do this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (ARQAJO-99) Integrate XHRHalter from Metamer project

by Lukáš Fryč (Created) (JIRA)

Integrate XHRHalter from Metamer project ---------------------------------------- Key: ARQAJO-99 URL: https://issues.jboss.org/browse/ARQAJO-99 Project: Arquillian Ajocado Issue Type: Enhancement Components: core Reporter: Lukáš Fryč Assignee: Lukáš Fryč -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (ARQGRA-134) KeyPressNative methods do not work on Chrome

by Juraj Huska (JIRA)

Juraj Huska created ARQGRA-134: ---------------------------------- Summary: KeyPressNative methods do not work on Chrome Key: ARQGRA-134 URL: https://issues.jboss.org/browse/ARQGRA-134 Project: Arquillian Graphene Issue Type: Bug Components: core Affects Versions: 1.0.0.Final Environment: browser Chrome Reporter: Juraj Huska Assignee: Lukáš Fryč KeyPressNative methods do not work at all. That is, when they are invoked the particular action which is bound with that native key is not done. No errors or exceptions are thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (ARQGRA-138) JavaScript Interfaces: when creating proxy, check parameters of methods

by Lukáš Fryč (JIRA)

Lukáš Fryč created ARQGRA-138: --------------------------------- Summary: JavaScript Interfaces: when creating proxy, check parameters of methods Key: ARQGRA-138 URL: https://issues.jboss.org/browse/ARQGRA-138 Project: Arquillian Graphene Issue Type: Enhancement Components: core Affects Versions: 2.0.0.Alpha1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 2.0-Tracking see documentation of executeScript(...) method: http://selenium.googlecode.com/svn/trunk/docs/api/java/index.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues April 2012