mistercam wrote:
> @UrlBinding("/a/admin/client/{client.uid}/exportTemplate/{$event}/{exportTemplate.uid}")
>
>
> @UrlBinding("/a/admin/client/{client.uid}/reportTemplate/{$event}/{reportTemplate.uid}")
>
>
> I don't want to move the client portion of the UrlBinding to the end of the
> pattern, either. Are there any ways to reconfigure the UrlBinding lookup
> process to handle this situation? Are there any other options available?
>
I have to say that I am only a little surprised that this is happening
and I think the option you mention is the solution. IIRC it has come up
on this list that the prefix portions need to be unique... though you
are correct that it should be OK... it obviously isn't.
I can see why you might want your URLs to remain this way as it almost
reads as a programmer ... client var = <some_id> / export var =
<some_event, some_id> but I think there is some elegance and symmetry
(and perhaps the ability to eliminate some redundant wording) in
tweaking your URL bindings like:
<some_prefix> / <event> / <entity_id> / <action_id> e.g.:
/a/admin/exportTemplate/edit/1/123
/a/admin/reportTemplate/edit/1/123
At least that is how I like to setup my URLs though of course your
requirements may be at odds but I'm not sure you have much choice unless
you re-wrote some of the URL binding logic I guess... (which I don't
think is worth the trouble and wouldn't recommend).
HTH,
--Nikolaos
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
