December 2011 - arquillian-issues

[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, 11 months

8
8
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, 11 months

5
6
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, 11 months

2
5
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, 11 months

6
10
0 / 0

[JBoss JIRA] (ARQAJO-100) Allow user to fail tests with AssertionError() with wait* objects

by Karel Piwko (Created) (JIRA)

Allow user to fail tests with AssertionError() with wait* objects ----------------------------------------------------------------- Key: ARQAJO-100 URL: https://issues.jboss.org/browse/ARQAJO-100 Project: Arquillian Ajocado Issue Type: Feature Request Components: core Affects Versions: 1.0.0.CR2 Reporter: Karel Piwko Assignee: Lukáš Fryč Expecting user want to fail (e.g. marking as failure instead of error) his test if some element is not present: {code} waitModel.failWith(new AssertionError("Invalid message not present")).until(elementPresent.locator(REG_INVALID)); {code} This is not possible. User has do to it following way. {code} waitModel.dontFail().until(elementPresent.locator(REG_INVALID)); Assert.assertTrue("Invalid message not present", selenium.isElementPresent(REG_INVALID)); {code} This is either an usability problem or a complete misunderstood of the usage by myself. -- 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, 12 months

4
4
0 / 0

[JBoss JIRA] Created: (ARQAJO-79) Forge integration

by Lukáš Fryč (JIRA)

Forge integration ----------------- Key: ARQAJO-79 URL: https://issues.jboss.org/browse/ARQAJO-79 Project: Arquillian Ajocado Issue Type: Feature Request Components: planning Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQAJO-89) Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic

by Juraj Huska (JIRA)

Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic ----------------------------------------------------------------------------------------------------------- Key: ARQAJO-89 URL: https://issues.jboss.org/browse/ARQAJO-89 Project: Arquillian Ajocado Issue Type: Feature Request Components: doc Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Lukáš Fryč Thread-Local Contexts section in docs should be more clean even for people not so familiar with given topic. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 12 months

3
2
0 / 0

[JBoss JIRA] (ARQ-693) Custom SQL statements / scripts to be run before and after test execution

by Bartosz Majsak (Created) (JIRA)

Custom SQL statements / scripts to be run before and after test execution ------------------------------------------------------------------------- Key: ARQ-693 URL: https://issues.jboss.org/browse/ARQ-693 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next Extend currently available feature of running custom SQL before test execution (initStatement defined in arquillian.xml) with following: * possibility to run custom SQL after test execution. * support SQL scripts (files) as an alternative to SQL statements (as it is now). * provide custom annotations on test class and method level for defining statements or SQL scripts to be executed before and/or after tests. This for instance might be handy for dropping constraints in some tests. -- 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

13 years

4
6
0 / 0

[JBoss JIRA] (ARQ-685) Failing to locate datasets when deploying as WAR archive.

by Bartosz Majsak (Created) (JIRA)

Failing to locate datasets when deploying as WAR archive. --------------------------------------------------------- Key: ARQ-685 URL: https://issues.jboss.org/browse/ARQ-685 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha2 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next When deploying test archive as WAR, datasets are not available for persistence extension. -- 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

13 years

6
6
0 / 0

[JBoss JIRA] (ARQ-694) Seeding database using SQL scripts

by Bartosz Majsak (Created) (JIRA)

Seeding database using SQL scripts ---------------------------------- Key: ARQ-694 URL: https://issues.jboss.org/browse/ARQ-694 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next As an alternative to DBUnit datasets it might be handy in some cases to seed database SQL scripts (direct export from the DB and more features than just inserting rows). For example by using annotation such as @UsingScript("script.sql") -- 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

13 years

6
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2011