[JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1286:
----------------------------
Sprint: Critical Issues, Warp Beta1 (was: Critical Issues)
> Support Warp on Java EE 5 (Servlets 2.5) compliant containers
> -------------------------------------------------------------
>
> Key: ARQ-1286
> URL: https://issues.jboss.org/browse/ARQ-1286
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests.
> We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested).
--
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, 5 months
[JBoss JIRA] (ARQ-1420) The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception.
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1420?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved ARQ-1420.
-----------------------------
Resolution: Done
Fixed by deferring payload retrieval with failure detection.
> The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ARQ-1420
> URL: https://issues.jboss.org/browse/ARQ-1420
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Jakub Narloch
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
>
> I'm facing some problem in the JAX-RS extension for the CXF. I'm already know that the CXF filter is doing a explicit OutputStream.flush() on the response, but not sure whether this affects anything. Although, it is worth to mention that I'm not facing any problems with other implementations. Currently I was able to debug only that the #retrieveResponsePayload() is being called before the payload registration, which cause an exception to be raised.
--
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, 5 months
[JBoss JIRA] (ARQ-1422) Add support for using Warp with ear deployments
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1422?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1422:
----------------------------
Assignee: Robert Panzer
> Add support for using Warp with ear deployments
> -----------------------------------------------
>
> Key: ARQ-1422
> URL: https://issues.jboss.org/browse/ARQ-1422
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Environment: Win7, JBoss AS 7.2
> Reporter: Robert Panzer
> Assignee: Robert Panzer
> Fix For: warp_1.0.0.Beta1
>
>
> The web filter WarpFilter is currently added to the auxiliary jars that are add as ear libs in case the deployment is an ear so that the filter is not deployed.
> The WarpFilter should be deployed as a web fragment of the web application under test to function properly when testing a war that is contained in an ear.
--
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, 5 months
[JBoss JIRA] (ARQ-1430) Warp does not take superclass into account when scanning for @WarpTest
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1430?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1430:
----------------------------
Estimated Difficulty: Low
> Warp does not take superclass into account when scanning for @WarpTest
> -----------------------------------------------------------------------
>
> Key: ARQ-1430
> URL: https://issues.jboss.org/browse/ARQ-1430
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Aslak Knutsen
> Priority: Minor
> Fix For: warp_1.0.0.Beta1
>
>
> *Given*
> {code}
> @WarpTest
> @RunAsClient
> public abstract class BaseRepositoryResourceBehavior<DOMAIN extends Identifiable> {
> ...
> }
> @RunWith(Arquillian.class)
> public class ConferenceResourceBehaviorTestCase extends BaseRepositoryResourceBehavior<Conference> {
> ...
> }
> {code}
> *Then*
> {code}
> java.lang.IllegalStateException: The Warp runtime isn't initialized. You need to annotate a test class with @WarpTest in order to initialize Warp.
> at org.jboss.arquillian.warp.Warp.initiate(Warp.java:41)
> at org.cedj.geekseek.web.rest.core.test.integration.resource.BaseRepositoryResourceBehavior.shouldHandleMissingResource(BaseRepositoryResourceBehavior.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> {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
11 years, 5 months