[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1400?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč resolved ARQ-1400.
-----------------------------
Resolution: Done
> Failure to create Enrichment hidden by Client Assertion
> -------------------------------------------------------
>
> Key: ARQ-1400
> URL: https://issues.jboss.org/browse/ARQ-1400
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
>
> The chain of event are:
> * Activity is executed
> * Client Request fail to enrich
> * Request goes to server
> * Response comes back
> * Client asserts the Response and fail
> * Exception shown to user is the failed Client side Assertion.
> The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
> Two things odd here:
> * Enrichment problems are hidden
> * Request still goes to server even tho we couldn't fulfill the setup
--
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
[JBoss JIRA] (ARQ-1413) Warp: The request is processed even though the transfer of inspection failed
by Lukáš Fryč (JIRA)
Lukáš Fryč created ARQ-1413:
-------------------------------
Summary: Warp: The request is processed even though the transfer of inspection failed
Key: ARQ-1413
URL: https://issues.jboss.org/browse/ARQ-1413
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha2
Reporter: Lukáš Fryč
Assignee: Aslak Knutsen
Originally reported in ARQ-1400.
Lukas:
{quote}
When the inspection is wrapped to a payload ({{RequestPayload}} / {{ResponsePayload}}) and tried to be serialized, it can fail.
In this case, the response should contain failure to indicate that something went wrong in the request processing.
{quote}
--
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
[JBoss JIRA] (ARQ-1400) Failure to create Enrichment hidden by Client Assertion
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1400?page=com.atlassian.jira.plugin.s... ]
Work on ARQ-1400 started by Lukáš Fryč.
> Failure to create Enrichment hidden by Client Assertion
> -------------------------------------------------------
>
> Key: ARQ-1400
> URL: https://issues.jboss.org/browse/ARQ-1400
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Aslak Knutsen
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Alpha3
>
>
> The chain of event are:
> * Activity is executed
> * Client Request fail to enrich
> * Request goes to server
> * Response comes back
> * Client asserts the Response and fail
> * Exception shown to user is the failed Client side Assertion.
> The real cause of the failure is the failed serialization of the enrichment object to setup the server side, which cause the server side response to be wrong and client assertion of course failing.
> Two things odd here:
> * Enrichment problems are hidden
> * Request still goes to server even tho we couldn't fulfill the setup
--
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