Wrong relative URL's when using Java EE 6 container with ERROR dispatching
--------------------------------------------------------------------------
Key: WICKET-2712
URL: https://issues.apache.org/jira/browse/WICKET-2712
Project: Wicket
Issue Type: Task
Components: wicket
Affects Versions: 1.4.6
Environment: Sun JDK 1.6.0u18, GlassFish v3 appserver
Reporter: Major Peter
In the Servlet API 3.0 spec [1] the ERROR dispatched pages requests does not
contain forward attributes, that's why in
ServletWebRequest#getRelativePathPrefixToWicketHandler() on the line #270 the
return value is null, and the relative urls are calculated wrong.
Way to reproduce:
create an error page which is mapped to /error/NotFound for instance (at least
on way deeper then the wicketfilter), and register the errorpage to 404 HTTP
code. On the 404 page place a link to a wicket page or resource.
Now if you check the result with GlassFish v3, then the links on the page
starts with error/NotFound/, but with GlassFish v2 this works flawlessly
(because it's a bug in it), see for more details [2] and [3].
[1]: http://jcp.org/aboutJava/communityprocess/final/jsr315/index.html section
10.9.1. on pages 102-103
[2]: http://old.nabble.com/Mounting-problem-with-GlassFishv3-td27386691.html
[3]: http://forums.java.net/jive/thread.jspa?threadID=73771&tstart=0
If needed I can attach a quickstart to the issue, which shows the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
