January 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-687) Support for custom hostname verifiers

by Shajahan Palayil (Created) (JIRA)

Support for custom hostname verifiers ------------------------------------- Key: ARQ-687 URL: https://issues.jboss.org/browse/ARQ-687 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebLogic Containers Affects Versions: wls_1.0.0.Alpha1 Environment: Windows XP/Linux Open Suse , Sun JVM Reporter: Shajahan Palayil My organization has a custom TrustKeyStore which has been configured by weblogic start parameter as below. weblogic.security.SSL.ignoreHostnameVerifictaion=false weblogic.security.SS.hostNameVerifier='custom built class name goes here' weblogic.security.TrustKeyStore=CustomTrust weblogic.security.CustomTrustKeyStoreFileName='location of the .properties file here' weblogic.security.CustomTrustKeyStorePassPhrase='pass phrase here' weblogic.security.CustomTrustKeyStoreType='TYPE goes here' I tried JSFUnit with Arquillian on normal weblogic server (downloaded and installed from Oracle) and its working great. But when I try to run it on organization provided weblogic env, it fails with error on client side with message, "Certificate chain received from localhost was not trusted causing SSL handshake failure etc..etc.." and on server console the error message is BAD_CERTIFICATE alert was received from localhost etc..etc.. The configuration is as below. <container qualifier="wls-ssl-demotrust" default="true"> <configuration> <property name="adminUrl">t3s://localhost:9998</property> <property name="adminUserName">weblogic</property> <property name="adminPassword">weblogic</property> <property name="target">admin_server_name</property> <property name="wlsHome">HOME DIRECTORY HERE</property> <property name="useCustomTrust">true</property> <property name="trustStoreLocation">location of the .properties file here</property> <property name="trustStorePassword">pass phrase here</property> </configuration> </container> -- 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, 3 months

8
8
0 / 0

[JBoss JIRA] (ARQ-731) Prepare WebLogic Container 1.0.0.Alpha2

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-731: --------------------------------- Summary: Prepare WebLogic Container 1.0.0.Alpha2 Key: ARQ-731 URL: https://issues.jboss.org/browse/ARQ-731 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: WebLogic Containers Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: wls_1.0.0.Alpha2 -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] (ARQ-707) Implement a remote wcontainer for WebLogic 12c

by Vineet Reynolds (Created) (JIRA)

Implement a remote wcontainer for WebLogic 12c ---------------------------------------------- Key: ARQ-707 URL: https://issues.jboss.org/browse/ARQ-707 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebLogic Containers Reporter: Vineet Reynolds Assignee: Vineet Reynolds An initial test of the existing Arquillian integration against a WebLogic 12c instance, concluded that it should be fairly easy to add support for the newer WebLogic container. The following points were noted: * The {{WebLogicCDIProcessor}} might have to be removed in the separate WLS 12c integration. This was originally present in the wls.1.0.0.Alpha1 release to enable testcase enrichment using CDI, if the Weld-Servlet dependency were to be packaged in the deployed ShrinkWrap archive. Since WLS 12c supports CDI out-of-the-box, this class is no longer necessary. It must be noted that this class was disabled when running tests against the "exampleServer" of a 12c installation, not a production WebLogic domain; therefore, the use of this class needs to be examined. * The following "warning" message was found in the logs, when the JMX client of the Arquillian integration connected to the WebLogic 12c container: {{Problem creating dummy orb: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No}}. This might need investigation. -- 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, 3 months

5
6
0 / 0

[JBoss JIRA] (ARQ-725) Refactor the WebLogicContainer implementation to a stateful implementation, to improve performance

by Vineet Reynolds (JIRA)

Vineet Reynolds created ARQ-725: ----------------------------------- Summary: Refactor the WebLogicContainer implementation to a stateful implementation, to improve performance Key: ARQ-725 URL: https://issues.jboss.org/browse/ARQ-725 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: WebLogic Containers Reporter: Vineet Reynolds Assignee: Vineet Reynolds Currently, the {{WebLogiContainer}} class does not store any state across archive deployments and undeployments. New instances of the {{WebLogicJMXClient}} class are created on every deployment and undeployment of archives. Internally, a new classloader is also created for every deployment and undeployment. This tends to increase the time elapsed for a deployment, before it is made available for execution of Arquillian tests. A refactoring is therefore proposed wherein the {{WebLogicContainer}} class would create only one reference to the {{WebLogicJMXClient}} class, and reuse it throughout the lifecycle of the container. -- 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, 3 months

2
7
0 / 0

[JBoss JIRA] (ARQ-730) maxTestClassesBeforeRestart sometimes restarts after arquillian-service deployed

by Kory Markevich (JIRA)

Kory Markevich created ARQ-730: ---------------------------------- Summary: maxTestClassesBeforeRestart sometimes restarts after arquillian-service deployed Key: ARQ-730 URL: https://issues.jboss.org/browse/ARQ-730 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR7 Environment: Windows 7 64, JDK 1.6.0_29 64-bit, Jboss 7.1.0.CR1b Reporter: Kory Markevich When using the maxTestClassesBeforeRestart option, server restarts are not ordered with respect to the deployment of the arquillian-service module. Things work fine if the deployment comes second, but if the restart occurs first it automatically undeploys the module. Since the instrumented archive being tested depends upon the arquillian-service module, it can fail and the tests not work. Any exceptions that happen can be very odd and difficult to trace. After doing some debugging, it seems to come down to the order that ContainerEventController and ContainerRestarter receive the BeforeClass TestClass event. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (ARQ-348) Create a Byteman integration

by Aslak Knutsen (JIRA)

Create a Byteman integration ---------------------------- Key: ARQ-348 URL: https://issues.jboss.org/browse/ARQ-348 Project: Arquillian Issue Type: Feature Request Components: Frameworks Reporter: Aslak Knutsen Assignee: Aslak Knutsen http://www.jboss.org/byteman Add support for BMRule(s)/BMScript to be executed against Targeted Deployments. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
5
0 / 0

[JBoss JIRA] (ARQ-727) Prepare Byteman Alpha1

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-727: --------------------------------- Summary: Prepare Byteman Alpha1 Key: ARQ-727 URL: https://issues.jboss.org/browse/ARQ-727 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Extension - Byteman Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: byteman_1.0.0.Alpha1 -- 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 months

1
1
0 / 0

[JBoss JIRA] (ARQ-728) Support Byteman Script annotation

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-728: --------------------------------- Summary: Support Byteman Script annotation Key: ARQ-728 URL: https://issues.jboss.org/browse/ARQ-728 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Byteman Reporter: Aslak Knutsen Fix For: byteman_1.0.0.next Support install of full BM scripts alla @BMScript -- 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 months

1
0
0 / 0

[JBoss JIRA] (ARQAJO-120) capturing screenshot fails with error

by Juraj Huska (JIRA)

Juraj Huska created ARQAJO-120: ---------------------------------- Summary: capturing screenshot fails with error Key: ARQAJO-120 URL: https://issues.jboss.org/browse/ARQAJO-120 Project: Arquillian Ajocado Issue Type: Bug Components: core Affects Versions: 1.0.0.CR3 Reporter: Juraj Huska *Capturing screenshot* either by calling captureEntirePageScreenshot or captureScreenshot methods it *throws error*: {code} java.lang.NoSuchMethodError: org.apache.commons.codec.binary.Base64.decodeBase64(Ljava/lang/String;)[B RemoteTestNG finishing: -1326453926882 ms at org.jboss.arquillian.ajocado.framework.TypedSeleniumImpl.decodeBase64Screenshot(TypedSeleniumImpl.java:800) at org.jboss.arquillian.ajocado.framework.TypedSeleniumImpl.captureEntirePageScreenshot(TypedSeleniumImpl.java:146) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.ajocado.framework.AjaxSeleniumContext.invoke(AjaxSeleniumContext.java:113) at $Proxy4.captureEntirePageScreenshot(Unknown Source) at org.jboss.test.selenium.listener.FailureLoggingTestListener.onFailure(FailureLoggingTestListener.java:126) at org.richfaces.tests.metamer.ftest.MetamerFailureLoggingTestListener.onFailure(MetamerFailureLoggingTestListener.java:56) at org.jboss.test.selenium.listener.FailureLoggingTestListener.onTestFailure(FailureLoggingTestListener.java:77) at org.testng.internal.Invoker.runTestListeners(Invoker.java:1823) at org.testng.internal.Invoker.runTestListeners(Invoker.java:1807) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1226) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109) at org.testng.TestRunner.runWorkers(TestRunner.java:1183) at org.testng.TestRunner.privateRun(TestRunner.java:762) at org.testng.TestRunner.run(TestRunner.java:613) at org.testng.SuiteRunner.runTest(SuiteRunner.java:335) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:330) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292) at org.testng.SuiteRunner.run(SuiteRunner.java:241) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1165) at org.testng.TestNG.runSuitesLocally(TestNG.java:1090) at org.testng.TestNG.run(TestNG.java:1002) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:107) at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:199) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:170) {code} Capturing screenshots *is essential* in implementation of failure testng listeners, when after each failure the screenshot of the page is taken. -- 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 months

2
7
0 / 0

[JBoss JIRA] (ARQAJO-102) Get value of attribute disabled returns true instead of the actual value - disabled

by Juraj Huska (Created) (JIRA)

Get value of attribute disabled returns true instead of the actual value - disabled ----------------------------------------------------------------------------------- Key: ARQAJO-102 URL: https://issues.jboss.org/browse/ARQAJO-102 Project: Arquillian Ajocado Issue Type: Bug Components: core Affects Versions: 1.0.0.CR2 Reporter: Juraj Huska Assignee: Lukáš Fryč Running this code: {code} AttributeLocator<?> disabledAttribute = button.getAttribute(new Attribute("disabled")); String isDisabled = selenium.getAttribute(disabledAttribute); {code} will result in state where *isDisabled will contain String true, instead of actual value disabled.* The .jsp page, just for completeness, contains this input: {code} <input type="submit" disabled="disabled"/> {code} -- 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 months

6
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2012