[
http://www.stripesframework.org/jira/browse/STS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Gunter updated STS-592:
---------------------------
Fix Version/s: Release 1.5.1
Priority: Minor (was: Major)
On the proposed addition of a public parseUrlBinding(String): Yes, please log a
new issue for that request. I'll be glad to open the API up in 1.5.1 if I can.
On supporting query-string-style parameters in @UrlBinding: I don't think it
would be a good idea, and I can give one really good reason why. Say you have
@UrlBinding("/foo?bar={bar}"). It becomes a big problem if you want to add more
parameters to the query string because /foo?bar=x&blah=y would result in a
parameter named "bar" with a value of "x&blah=y" from the embedded parameter
and then another parameter "bar" with value "x" from the app server and another
named "blah" with value "y" from the app server. There's just way too much
potential for trouble with such a thing.
If anything, we'll change it so that special characters in the binding are
URL-encoded.
> Stripes 1.5 URLBindingFactory does not parse clean URLs with appended
> parameters
> ---------------------------------------------------------------------------------
>
> Key: STS-592
> URL: http://www.stripesframework.org/jira/browse/STS-592
> Project: Stripes
> Issue Type: Bug
> Components: ActionBean Dispatching
> Affects Versions: Release 1.5
> Environment: OS X
> Reporter: Andrew Jaquith
> Assignee: Ben Gunter
> Priority: Minor
> Fix For: Release 1.5.1
>
>
> I've found an issue in build 947 with the implementation of clean URLs, which
> relates to differences in how the ActionResolver and UrlBuilder handle
> appended parameters. I had previously written up my observations in comments
> on STS-262, but that issue had been marked closed. I was not sure if my
> comments had been read, hence I am opening a new issue.
> Summary:
> With a given "clean" @UrlPattern, if parameters otherwise unspecified in the
> pattern are added to the UrlBuilder, they are properly appended in the
> generated URL. But if that generated URL is passed back to the StripesFilter,
> the trailing parameters are not parsed as expected, even if the ActionBean
> has properties that those parameters "should" bind do. In other words, it is
> not a "round trip" operation.
> For more in-depth comments, *and* a proposed patch to fix the issue, see
> STS-262.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
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
