This repository is a fork of the Arquillian Showcase. Its rewrite branch illustrates problems I faced when using OCPsoft's URL-Rewriting Framework rewrite with Arquillian Warp.
- updated some dependencies in arquillian-showcase-parent to current versions (Arquillian Warp 1.0.0.Alpha5)
- added a rewrite configuration and a failing test to the arquillian-showcase-warp project
See git changelog for details.
arquillian-showcase-warp contains two simple JSF applications and a Warp test case for each one of them.
I added RewriteConfigurationProvider
which introduces an URI alias "/index" for the JSF page "index.xhtml".
In BasicJSFUnitTestCase
, I added a copy of the existing Warp test.
Now, there are two warp test performing the same task, one using the original URI and one the aliased one.
To see the URI alias in action,
- cd to the warp directory
- build and deploy to a running local JBoss AS 7.1.1 with
mvn jboss-as:deploy -DskipTests
- open the JSF page with its original URI http://localhost:8080/arquillian-showcase-warp/index.jsf
- open the JSF page with its aliased URI http://localhost:8080/arquillian-showcase-warp/index
- undeploy with
mvn jboss-as:undeploy
- Make sure no local JBoss server is running.
- cd to the warp directory
- Run
mvn test
all tests pass.
BasicJSFUnitTestCase.shouldExecutePage_usingUrlAlias()
fails with ClientWarpExecutionException:
deenriching response failed: The response payload with serialId [...] was never registered
The Warp test using the unaliased URI passes as expected. But when Rewrite rewrites a request, the corresponding Warp test fails.
I'm not sure whether this is an rewrite or Warp issue. Any help on how to combine these two technologies would be greatly appreciated.