RE: Need Help With Event URL Rewriting

2012-04-25 Thread Mike Dunbar
Thought I'd share what finally worked with this. In the end, it turned out to be pretty simple. We just: - Implemented ComponentEventLinkEncoder.createComponentEventLink, wherein we a) Return a Link with the URL of our choice and b) Stash away the associated ComponentEventRequestParameters obje

Re: Need Help With Event URL Rewriting

2012-04-09 Thread Thiago H. de Paula Figueiredo
On Mon, 09 Apr 2012 15:03:26 -0300, Mike Dunbar wrote: Hi Thiago, Thanks for your response. My replies inline below. -Mike Why aren't the Tapestry URLs RESTful enough for your scenario? Using PUT, DELETE, etc? Just curious. :) I may be using the term 'RESTful' incorrectly. What I meant i

RE: Need Help With Event URL Rewriting

2012-04-09 Thread Mike Dunbar
Hi Thiago, Thanks for your response. My replies inline below. -Mike > Why aren't the Tapestry URLs RESTful enough for your scenario? Using PUT, > DELETE, etc? Just curious. :) I may be using the term 'RESTful' incorrectly. What I meant is suppose I have a page that displays the details of an or

Re: Need Help With Event URL Rewriting

2012-04-09 Thread Thiago H. de Paula Figueiredo
On Mon, 09 Apr 2012 12:51:19 -0300, Mike Dunbar wrote: Hi, Hi! We are trying to build an application with RESTful URLs, rather than the out-of-box Tapestry URLs. Why aren't the Tapestry URLs RESTful enough for your scenario? Using PUT, DELETE, etc? Just curious. :) We've been able