It's not supposed to do that. I just tried to replicate it using your
example, and I couldn't. Usually when someone complains that their context
path is being stripped off a URL it's because the context-relative path
begins with the context name. E.g., in context /foo you might have problems
working with the path /foo/bar (where you want the full path to be
/foo/foo/bar).
If you can pass along some specific code that definitely triggers this in
your environment then I'll try it out. My testing was on the same version of
Stripes, Tomcat and Java.
-Ben
On Mon, May 24, 2010 at 8:17 PM, Chris Cheshire <cheshira...@gmail.com>wrote:
> (Using Stripes 1.5.3, Tomcat 6.0.x, Java6)
>
> I have an action bound as "/action/{blah}" as part of an app installed
> under a sub-context /foo.
>
> In a stripes:form tag I put a stripes:param for blah and the resultant
> html shows the action url as just "/action/blah", instead of
> "/foo/action/blah".
>
> If I change the param to a hidden field instead, the action for the
> form is now "/foo/action".
>
> Why is the context being stripped from the form action url when a
> param is being used inside the form?
>
>
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
