[JBoss JIRA] (ARQ-992) Warp does not support request redirection.
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-992?page=com.atlassian.jira.plugin.sy... ]
Lukáš Fryč updated ARQ-992:
---------------------------
Priority: Critical (was: Minor)
> Warp does not support request redirection.
> ------------------------------------------
>
> Key: ARQ-992
> URL: https://issues.jboss.org/browse/ARQ-992
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha1
> Environment: JBoss AS 7.1.1
> Reporter: Jakub Narloch
> Assignee: Lukáš Fryč
> Priority: Critical
> Labels: warp
> Fix For: warp_1.0.0.Alpha2
>
>
> When I was running tests of Spring controllers I found out that whenever a controller is redirecting the response for example by returning a String as view name: {code}return "redirect:welcome.do"{code} the execution of the test hangs till end of timeout.
> I've debuged the WarpFilter and it seems that the Warp header is not beeing added into the 302 HTTP response. On the client side this result with ResponseDeenrichmentFilter can not find any ResponsePayload in response.
> Taking into consideration fact that the RequestEnrichmentFilter allows to push the assertion only once, so when the second request is being made the assertion is not being send once again I'm unable to test such response.
--
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
12 years, 1 month
[JBoss JIRA] (ARQ-1027) Support CommandService Protocol SPI via Warp Protocol
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1027?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on ARQ-1027:
---------------------------------
Discussion from IRC:
http://transcripts.jboss.org/channel/irc.freenode.org/%23jbosstesting/201...
> Support CommandService Protocol SPI via Warp Protocol
> -----------------------------------------------------
>
> Key: ARQ-1027
> URL: https://issues.jboss.org/browse/ARQ-1027
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha1
> Reporter: Curtis McMillen
> Fix For: warp_1.0.0.Alpha2
>
> Attachments: stacktrace.txt
>
>
> It seems there is a problem with running Warp tests if arquillian-jacoco is on the classpath.
> When WarpFilter fires the AfterSuite event, the writeCoverageData observer in arquillian-jacoco is executing which ultimately leads to a NPE coming from servlet protocol. The full stacktrace is attached.
> You can reproduce by simply adding the following dependencies to the pom for warp in arquillian-showcase and then running the BasicJSFUnitTestCase.
> {code:xml}
> <dependency>
> <groupId>org.jboss.arquillian.extension</groupId>
> <artifactId>arquillian-jacoco</artifactId>
> <version>1.0.0.Alpha3</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jacoco</groupId>
> <artifactId>org.jacoco.core</artifactId>
> <version>0.5.7.201204190339</version>
> <scope>test</scope>
> </dependency>
> {code}
> Removing these dependencies isn't really an option because I have other arquillian tests not using Warp that I want code coverage on. I tried using alternative annotated with @Specializes thinking I could basically disable the observer in arquillian-jacoco simply by including a different beans.xml in the deployment of my Warp tests. This however fails with "WELD-000047 Specializing bean must extend another bean" which I'm thinking is due to https://issues.jboss.org/browse/WELD-1113.
> Any ideas for getting this to work?
--
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
12 years, 1 month
[JBoss JIRA] (ARQGRA-230) Override a toString method in BooleanConditionWrapper
by Jiří Štefek (JIRA)
Jiří Štefek created ARQGRA-230:
----------------------------------
Summary: Override a toString method in BooleanConditionWrapper
Key: ARQGRA-230
URL: https://issues.jboss.org/browse/ARQGRA-230
Project: Arquillian Graphene
Issue Type: Enhancement
Reporter: Jiří Štefek
Priority: Trivial
It would be great if BooleanConditionWrapper had its own toString() method, so the logs from selenium could be more readable than:
{code}org.openqa.selenium.TimeoutException: Timed out after 5 seconds waiting for org.jboss.arquillian.graphene.condition.BooleanConditionWrapper@198de25e{code}
--
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
12 years, 1 month
[JBoss JIRA] (ARQ-1172) Implement an embedded WebLogic Server container
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-1172:
------------------------------------
Summary: Implement an embedded WebLogic Server container
Key: ARQ-1172
URL: https://issues.jboss.org/browse/ARQ-1172
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: WebLogic Containers
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Priority: Minor
WebLogic Server 12c supports EJB 3.1 and is hence expected to support testing of EJBs in an embedded container, at a minimum.
This feature request is to investigate implementation of the embedded Arquillian container for WLS 12c in particular. Support for an embedded mode of operation for WLS 10.3.x is to be investigated, and may be implemented if supported by Oracle (as documentated APIs or similar).
--
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
12 years, 1 month
[JBoss JIRA] (ARQ-1208) Multiple line statements are not handled properly
by Bartosz Majsak (JIRA)
Bartosz Majsak created ARQ-1208:
-----------------------------------
Summary: Multiple line statements are not handled properly
Key: ARQ-1208
URL: https://issues.jboss.org/browse/ARQ-1208
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Persistence
Affects Versions: persistence_1.0.0.Alpha5
Reporter: Bartosz Majsak
Assignee: Bartosz Majsak
Fix For: persistence_1.0.0.next
When sql statement spans multiple lines it's not handled properly by the current implementation.
--
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
12 years, 1 month
[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, 1 month