Hello,
I'm surprised by an UrlBinding conflict I recently encountered.
I have two classes with the following URL bindings:
@UrlBinding("/a/admin/client/{client.uid}/exportTemplate/{$event}/{exportTemplate.uid}")
public class ExportTemplateAction extends BaseAction {...}
@UrlBinding("/a/admin/client/{client.uid}/reportTemplate/{$event}/{reportTemplate.uid}")
public class ReportTemplateAction extends BaseAction {...}
The problem is an URL like "/a/admin/client/1/exportTemplate/edit/123" will
collide with the second UrlBinding pattern listed above. I thought the
"exportTemplate" and "reportTemplate" between the {client.uid} and {$event}
parameters would be enough to differentiate the two.
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?
Thanks,
-- Cameron
--
View this message in context:
http://old.nabble.com/UrlBinding-Conflict.-Configuring-UrlBinding-lookups--tp29257757p29257757.html
Sent from the stripes-users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
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
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
