Hi,
I'm having a feature request and before filing an issue, I would like to
have other users' opinions on its necessity.
Anyway, in clean URLs you can use defaults for parameter values:
@UrlBinding("/members/{page=1}")
This default value helps when building an URL (e.g. with the stripes:url and
:link tags). Now, I thought that it would be nice if this default value
could be dynamic:
@UrlBinding("/blog/{year=currentYear()}/{month=currentMonth()}")
The currentYear/currentMonth methods could be action bean methods (which
would be nice since in that case, the action bean context would be available
as well). Another option could be to reuse the validation's EL support.
Now my question is: does this make sense? The counterargument is that you
can have dynamic parameters using the stripes:param tag and that in that
case, you can supply any value you want. Does the added value compensate for
the increased complexity? I think it does, but I'm interested in other
points of view.
Regards,
Levi
-------------------------------------------------------------------------
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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
