I doubt this would work with 1.5, but if you checkout the latest code from
either the trunk or the 1.5.x branch and compile it, you can easily do
@UrlBinding("/{first}/{otherStuff}"). The main drawback to a mapping like
this is that it makes it such that you'll have to handle 404 errors yourself
because that binding matches everything that starts with a slash, unless the
URL points to an existing static resource or is a better match for another
ActionBean.
These capabilities will be available in 1.5.1. And to answer the inevitable
next question, I don't know when it will be released. I have a lot going on
right now and haven't had any time to work on it.
-Ben
On Fri, Jan 23, 2009 at 5:56 PM, Randy Jones <m...@jonesrc.com> wrote:
> Another newbie question.
>
> I would like to use Stripes but my application needs to have full control
> over
> the URL. Some of the action beans can map ok using the UrlBinding but some
> will
> require code to analyze the URL to determine which action bean should be
> called.
> My gut feeling is that Stripes has a way for me to do this but I could use
> some
> pointing in the right direction. Here are some URL examples:
>
> /clinic - this can map with @UrlBinding
>
> /dalmation/female/fred
> /labador+retriever/male/brown - need these to map to same action bean
> /cocker-spaniel/steve/update
>
>
> There might be hundreds of different first parameters in the URL that need
> to
> map to the same action bean.
>
> Thanks,
> Randy
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
