[JBoss JIRA] (ARQ-1306) Prepare GWT 1.0.0.Alpha1
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1306:
----------------------------------
Summary: Prepare GWT 1.0.0.Alpha1
Key: ARQ-1306
URL: https://issues.jboss.org/browse/ARQ-1306
Project: Arquillian
Issue Type: Release
Security Level: Public (Everyone can see)
Components: Extension - GWT
Affects Versions: gwt_1.0.0.Alpha1
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1251) Arquillian Drone is unable to instantiate Firefox driver if acceptSslCerts, webStorageEnabled, loggingPrefs properties are used in arquillian.xml
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ARQ-1251?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on ARQ-1251:
----------------------------------------------
Marek Novotny <mnovotny(a)redhat.com> changed the Status of [bug 888458|https://bugzilla.redhat.com/show_bug.cgi?id=888458] from MODIFIED to ON_QA
> Arquillian Drone is unable to instantiate Firefox driver if acceptSslCerts, webStorageEnabled, loggingPrefs properties are used in arquillian.xml
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1251
> URL: https://issues.jboss.org/browse/ARQ-1251
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: drone_1.1.0.Final
> Reporter: Tomas Repel
> Assignee: Tomas Repel
> Fix For: drone_1.1.1.Final, drone_1.2.0.Alpha1
>
>
> Description of problem:
> If you set these properties via arquillian.xml, the Drone fails to instantiate the Firefox driver. The problem is during creation of org.openqa.selenium.firefox.FirefoxDriver instance, these properties are cast from String to e.g. Boolean (in case of acceptSslCerts) resulting in ClassCastException.
> Snippet of arquillian.xml:
> {code:xml}
> <extension qualifier="webdriver">
> <property name="acceptSslCerts">false</property>
> <property name="webStorageEnabled">false</property>
> <property name="loggingPrefs">someLoggingPrefs</property>
> </extension>
> {code}
> Snippet of Firefox driver injection that fails:
> {code}
> @Drone
> FirefoxDriver browser;
> {code}
> Version-Release number of selected component (if applicable):
> Arquillian 1.0.3.Final
> Arquillian Drone extension 1.1.0.Final
> Selenium 2.27.0 (WebDriver 2)
> How reproducible:
> Always.
> Steps to Reproduce:
> 1. launch functional test using code snippets above
>
> Actual results:
> {noformat}
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean
> at org.openqa.selenium.firefox.FirefoxDriver.populateProfile(FirefoxDriver.java:148)
> at org.openqa.selenium.firefox.FirefoxDriver.extractProfile(FirefoxDriver.java:133)
> at org.openqa.selenium.firefox.FirefoxDriver.<init>(FirefoxDriver.java:100)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> at org.jboss.arquillian.drone.webdriver.factory.SecurityActions.newInstance(SecurityActions.java:142)
> ... 50 more
> {noformat}
> Expected results:
> It launches Firefox browser.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1292) Remove custom wire protocol and replace with REST API over HTTP
by Ralf Battenfeld (JIRA)
[ https://issues.jboss.org/browse/ARQ-1292?page=com.atlassian.jira.plugin.s... ]
Ralf Battenfeld commented on ARQ-1292:
--------------------------------------
Hi Aslak and Andrew
This looks very interesting. Shall I do some investigations?
> Remove custom wire protocol and replace with REST API over HTTP
> ---------------------------------------------------------------
>
> Key: ARQ-1292
> URL: https://issues.jboss.org/browse/ARQ-1292
> Project: Arquillian
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Daemon
> Affects Versions: daemon_1.0.0.Alpha1
> Reporter: Andrew Rubinger
>
> The slim custom wire protocol for 1.0.0.Alpha1 is premature optimization; there's no need to shave bytes on the protocol when the intended payload is a deployable archive. Implementing as HTTP (via some RESTful API) will pave the way towards fulfilling feature requests for secure transfer (ie. SSL) and authentication/authorization (ie. BASIC).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1305) Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
by Jakub Narloch (JIRA)
[ https://issues.jboss.org/browse/ARQ-1305?page=com.atlassian.jira.plugin.s... ]
Jakub Narloch updated ARQ-1305:
-------------------------------
Fix Version/s: spring_1.0.0.next
Affects Version/s: spring_1.0.0.Beta1
Component/s: Extension - Spring
> Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
> ----------------------------------------------------------------------------
>
> Key: ARQ-1305
> URL: https://issues.jboss.org/browse/ARQ-1305
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Spring
> Affects Versions: spring_1.0.0.Beta1
> Reporter: Jakub Narloch
> Fix For: spring_1.0.0.next
>
>
> The idea is similar to the 'convention over configuration' approach from Spring Test.
> When configuring test with @SpringConfiguration when no XML configuration will specified the extension by default should try to load file with exact same name as the test class and additional '-context.xml' suffix e.g.
> For class org.sample.Test the default resource location should be org/sample/Test-context.xml.
> In case of @SpringAnnotationConfiguration when no class or package has been specified the extension by default should scan for static (non final) class annoated with @Configuration and use it when instantiating the AnnotationApplicationContext.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1305) Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
by Jakub Narloch (JIRA)
[ https://issues.jboss.org/browse/ARQ-1305?page=com.atlassian.jira.plugin.s... ]
Jakub Narloch reassigned ARQ-1305:
----------------------------------
Assignee: Jakub Narloch
> Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
> ----------------------------------------------------------------------------
>
> Key: ARQ-1305
> URL: https://issues.jboss.org/browse/ARQ-1305
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Spring
> Affects Versions: spring_1.0.0.Beta1
> Reporter: Jakub Narloch
> Assignee: Jakub Narloch
> Fix For: spring_1.0.0.next
>
>
> The idea is similar to the 'convention over configuration' approach from Spring Test.
> When configuring test with @SpringConfiguration when no XML configuration will specified the extension by default should try to load file with exact same name as the test class and additional '-context.xml' suffix e.g.
> For class org.sample.Test the default resource location should be org/sample/Test-context.xml.
> In case of @SpringAnnotationConfiguration when no class or package has been specified the extension by default should scan for static (non final) class annoated with @Configuration and use it when instantiating the AnnotationApplicationContext.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1305) Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
by Jakub Narloch (JIRA)
Jakub Narloch created ARQ-1305:
----------------------------------
Summary: Defaults values for @SpringConfiguration and @SpringApplicationConfiguration
Key: ARQ-1305
URL: https://issues.jboss.org/browse/ARQ-1305
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Jakub Narloch
The idea is similar to the 'convention over configuration' approach from Spring Test.
When configuring test with @SpringConfiguration when no XML configuration will specified the extension by default should try to load file with exact same name as the test class and additional '-context.xml' suffix e.g.
For class org.sample.Test the default resource location should be org/sample/Test-context.xml.
In case of @SpringAnnotationConfiguration when no class or package has been specified the extension by default should scan for static (non final) class annoated with @Configuration and use it when instantiating the AnnotationApplicationContext.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months