[JBoss JIRA] (ARQ-1489) response payload was never registered when used with OCPsoft Rewrite
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on ARQ-1489:
---------------------------------
As a solution, we should register WarpFilter web-fragment.xml which will allow us specify ordering (including known conflicting filters such as RewriteFilter):
{code:xml}
<ordering>
<before>
<others />
<name>com_ocpsoft_rewrite</name>
</before>
</ordering>
{code}
Solution for second issue is preparing WarpFilter for forwarding in filter chain.
> response payload was never registered when used with OCPsoft Rewrite
> --------------------------------------------------------------------
>
> Key: ARQ-1489
> URL: https://issues.jboss.org/browse/ARQ-1489
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: 1.0.0.Alpha4
> Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final
> Reporter: Harald Albers
> Fix For: warp_1.0.0.Alpha5
>
>
> I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp.
> Warp tests work as long as I use the original unaliased URLs.
> Warp tests using the aliased URLs fail with
> ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered
> I created a demonstration project, see README.md for details:
> https://github.com/albers/arquillian-showcase/tree/rewrite
--
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, 2 months
[JBoss JIRA] (ARQ-1489) response payload was never registered when used with OCPsoft Rewrite
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1489?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on ARQ-1489:
---------------------------------
There are two problems:
* Rewrite uses web filter RewriteFilter for request processing and WarpFilter doesn't react correctly on filtering when it is invoked after RewriteFilter
* RewriteFilter forwards request, repeating filter chain several times, which again brokes WarpFilter which does activate manager and its scopes repeatedly
> response payload was never registered when used with OCPsoft Rewrite
> --------------------------------------------------------------------
>
> Key: ARQ-1489
> URL: https://issues.jboss.org/browse/ARQ-1489
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: 1.0.0.Alpha4
> Environment: Arquillian Warp 1.0.0.Alpha4 with Rewrite 2.0.7.Final in a JBoss AS 7.1.1.Final
> Reporter: Harald Albers
> Fix For: warp_1.0.0.Alpha5
>
>
> I use OCPsoft Rewrite (http://ocpsoft.org/rewrite/) to add fancy URL aliases to my JSF webapp.
> Warp tests work as long as I use the original unaliased URLs.
> Warp tests using the aliased URLs fail with
> ClientWarpExecutionException: deenriching response failed: The response payload with serialId [...] was never registered
> I created a demonstration project, see README.md for details:
> https://github.com/albers/arquillian-showcase/tree/rewrite
--
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, 2 months
[JBoss JIRA] (ARQ-1555) Rest Extension clients should be decoupled from RestEasy
by John Ament (JIRA)
[ https://issues.jboss.org/browse/ARQ-1555?page=com.atlassian.jira.plugin.s... ]
John Ament commented on ARQ-1555:
---------------------------------
The problem with using @ArquillianResource is that its value is a class, which you currently use to determine which class's context to use (even though @OperateOnDeployment uses a name - String). Hence why I was saying to use @ArquillianRestClient or something like that, don't want to break core.
> Rest Extension clients should be decoupled from RestEasy
> --------------------------------------------------------
>
> Key: ARQ-1555
> URL: https://issues.jboss.org/browse/ARQ-1555
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - REST
> Reporter: John Ament
> Priority: Minor
>
> Currently, the annotation marking a REST client is "ArquillianResteasyResource", this implies that the client framework can only ever work with RestEasy. I would like to propose renaming this annotation ArquillianRestClient, which clearily identifies it as being useful to any Rest Client framework, and make it's clearer that it's a client API (not the resource itself).
--
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, 2 months