URI parameter is present with null value even when not specified
----------------------------------------------------------------
Key: STS-790
URL: http://www.stripesframework.org/jira/browse/STS-790
Project: Stripes
Issue Type: Bug
Components: ActionBean Dispatching
Affects Versions: Release 1.5.4
Reporter: Ben Gunter
Assignee: Ben Gunter
Priority: Minor
Fix For: Release 1.5.5, Release 1.6
This is perhaps best illustrated by example. Say you have an ActionBean with
@UrlBinding("/foo/{a}/{b}"). A request to /foo should have no parameters
present, /foo/bar should have only a=foo present, and /foo/bar/baz should have
a=bar and b=baz. Instead, when a parameter value is omitted from the URI, the
parameter is actually present in the request with a null value.
The difference seems negligible, but it's not. It has a direct impact on form
population. In this example, a form with <s:hidden name="a" value="blah" />
rendered with a request to /foo would render the hidden input with a value=""
because the request parameter is actually present. Instead, since the value was
omitted from the URI, the parameter should be absent and the input's value
should be "blah".
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Stripes-development mailing list
Stripes-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-development
