[
http://issues.ops4j.org/jira/browse/PAXWICKET-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_10806
]
David Leangen commented on PAXWICKET-14:
----------------------------------------
Nope. The problem is with Pax Wicket in PaxWicketRequest.
The problem is due to what PaxWicketRequest passes into
wicket.protocol.http.request.WebRequestCodingStrategy.urlPrefix(RequestCycle).
However, Wicket docs don't say precisely how getContextPath() and
getServletPath() are supposed to behave with regards to slashes.
Anybody know? Or maybe know where I can find this info?
Anyway, in the meantime I'll try a hack just to remove the slash at the end of
the context path (assuming that wicket works correctly, it means that that
slash should not be there) to see if it works, but it would be nice to be able
to verify against some kind of spec.
> Need to remove extra slashes in URL
> -----------------------------------
>
> Key: PAXWICKET-14
> URL: http://issues.ops4j.org/jira/browse/PAXWICKET-14
> Project: Pax Wicket
> Issue Type: Bug
> Reporter: David Leangen
> Assignee: Niclas Hedhman
>
> It seems that Pax Wicket is outputting extra slashes in URLs.
> Problem needs to be fixed, since this is not OSGi compliant (see
> http://issues.ops4j.org/jira/browse/PAXWEB-41).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
