[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č edited comment on ARQ-1420 at 7/11/13 2:40 AM:
----------------------------------------------------------
Thanks for checking, Jakub.
Just FYI, I haven't ran tests against Tomcat 7 either since Warp requires Java EE web profile to run complete suite.
Tests didn't fully pass on GlassFish - there is a branch I was experimenting in:
https://github.com/arquillian/arquillian-extension-warp/compare/ARQ-1261
was (Author: lfryc):
Thanks for checking, Jakub.
Just FYI, I haven't ran tests against Tomcat 7 either since Warp requires Java EE web profile to run complete suite.
> 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
10 years, 11 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č commented on ARQ-1420:
---------------------------------
Thanks for checking, Jakub.
Just FYI, I haven't ran tests against Tomcat 7 either since Warp requires Java EE web profile to run complete suite.
> 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
10 years, 11 months
[JBoss JIRA] (ARQ-1420) The PayloadRegistry#registerResponsePayload() is being called after the #retrieveResponsePayload() which ends up with ResponsePayloadWasNeverRegistered exception.
by Jakub Narloch (JIRA)
[ https://issues.jboss.org/browse/ARQ-1420?page=com.atlassian.jira.plugin.s... ]
Jakub Narloch commented on ARQ-1420:
------------------------------------
I double check this with Tomcat 7, the result is the same, the test is failing. I will try to figure out why.
> 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
10 years, 11 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:
----------------------------
Fix Version/s: warp_1.0.0.Beta1
> 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
> 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
10 years, 11 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:
----------------------------
Priority: Minor (was: Major)
> 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
10 years, 11 months
[JBoss JIRA] (ARQ-1430) Warp does not take superclass into account when scanning for @WarpTest
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1430?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen updated ARQ-1430:
-------------------------------
Description:
*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}
> 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
>
> *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
10 years, 11 months