I'm going to write a blog entry, I suppose, to start. After feedback and if it's good enough, I can put it closer to other Stripes libraries and documentation.
Although, I'd really like to talk about how we can support adding other HTTP parameters to bindings. Would it be possible to change ActionResolver to accept a whole HttpRequest? In the case of the action resolution for the form tag, a wrapped HttpRequest that represents what the request for that form might look like? Alan On Jul 18, 2008, at 3:40 AM, Mark Smith wrote: > This is good! I will be needing to do a similar thing too.. > > Is this in a How-to? > > Cheers > Mark > > On Thu, Jul 17, 2008 at 8:38 PM, Alan Gutierrez > <[EMAIL PROTECTED]> wrote: > Gregg > > Good. Then I'll work on putting it in it's own project. > > To make it work you need to use a special HttpRequest wrapper, which > I build in a a special ActionBeanContextFactory. You can drop in my > factory or make sure to wrap the request in your own, if you're using > one. If that really doesn't work, then you can also use a special > StripesFilter which will wrap the HttpRequest. > > I'm wondering if we can talk about making some adjustments to Stripes > itself to support more intricate binding strategies. How does one go > about suggesting changes to the core? I'm hoping that as I suggest > changes you all will tell me that they are unnecessary. > > Alan > > On Jul 17, 2008, at 12:47 PM, Gregg Bolinger wrote: > > > I really like this idea. I am going to be in a similar situation > > where > > I need to publish a URL based on an account, the same as you, Alan. > > > > Gregg > > > > Alan Gutierrez wrote: > > >> I'd like to add the ability to bind to other variables in the > >> request. Specifically, the server, because I'd like to have a > >> Basecamp hosting strategy for my app in the long run... > >> > >> http://account.domain.com/orders/edit/1 > >> > >> This is a very popular strategy and it's going to fit nicely > into my > >> grand plan. > >> > >> Which would mean that UrlBinding and ActionResolvers in general > would > >> have to bind to more than just a path, but an entire URL plus, for > >> the REST folks, a verb. So why not bind against the full HTTP > >> request? Or at least the combination of verb and full URL -- Alan Gutierrez | [EMAIL PROTECTED] | http://blogometer.com/ | 504 717 1428 Think New Orleans | http://thinknola.com/ ------------------------------------------------------------------------- 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
