FormTag and LinkTagSupport both depend on getServletPath() to return the JSP path when encoding the source page in forms or links.
I learned today that this may not be a good way to go about this, mostly due to a really shitty "bug" (though the Tomcat/Jasper guys will argue it's per-spec): https://issues.apache.org/bugzilla/show_bug.cgi?id=27704 Basically, /foo/bar/baz.jsp will return "/foo/bar/baz.jsp" when getServletPath() is called all day long until you create a jsp-property-group: <jsp-property-group> <url-pattern>/foo/*</url-pattern> <include-prelude>/WEB-INF/jsp/include/page_header.jspf</include-prelude> <trim-directive-whitespaces>true</trim-directive-whitespaces> </jsp-property-group> Once you've done that, the value returned will now be the url-pattern - in this case "/foo". This of course causes Stripes to break down completely when handling things like validations. Greg Wilkins is thinking about it, but he tends to agree with the Jasper guys (though he's way less of a dick as Remy comes off if you read the bug report). Considering Greg, who we probably all agree is a smart guy, thinks this may not deserve to get fixed, perhaps it means Stripes needs a different solution than calling getServletPath. Thoughts? Patrick ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-development
