we only use servletpath when we are in servlet mode:
public String getRelativePath(HttpServletRequest request)
{
String path = Strings.stripJSessionId(request.getRequestURI());
String contextPath = request.getContextPath();
path = path.substring(contextPath.length());
Hmm, interesting. The code I'm looking at, from the beta1 snapshot, looks
more like this:
String path = request.getServletPath();
if (servletMode)
{
path = request.getPathInfo();
// No path info =
http://www.wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3.0-incubating-SNAPSHOT/
On 5/11/07, dukejansen [EMAIL PROTECTED] wrote:
Hmm, interesting. The code I'm looking at, from the beta1 snapshot, looks
more like this:
String path = request.getServletPath();
I believe I have identified a rather serious bug in WicketFilter.
I'm using a recent 1.3 snapshot, and I have recently updated our application
to leverage the WicketFilter instead of WicketServlet. This is working great
in Tomcat, but when we deploy to our Weblogic server, Wicket dies an ugly
Probably would be wise to look at all calls to
HttpServletRequest.getServletPath.
--
View this message in context:
http://www.nabble.com/WicketFilter-doesn%27t-work-in-Weblogic--Wicket-1.3--tf3724994.html#a10424543
Sent from the Wicket - User mailing list archive at Nabble.com.
