5.1 is pretty stable right now and due to some concerns of my own (*), I'll be pushing to release it fairly soon. I think the Spring Web Flow support may move out to 5.2.
It's not going to go 18 releases like 5.0! (*) I have clients of my own who are in the same predicament. Also I think it would be good to release 5.1 with tons of new features (100 issues closed so far) that is fully backwards compatible to 5.0 ... just upgrade and receive the benefits. On Thu, Feb 5, 2009 at 12:28 PM, xfile80303 <l...@grokers.net> wrote: > > Thanks for the reply Howard. > > Is 5.1 at a state where I can start using it to develop a service which will > go to production in a couple months? > > (i.e. does this help me now?) > > Levi > > > Howard Lewis Ship wrote: >> >> I've been doing some cleanup of some internal APIs lately with the >> goal to centralizing Tapestry's logic for generating and parsing >> component event and page render links. This will allow an application >> to override how that information is incorporated into the URL. >> >> In your case, you could have a Dispatcher recognize the "/venue_name" >> part and then generate a PageRenderRequestParameters object and invoke >> the ComponentRequestHandler.handlePageRender() pipeline method. >> >> Note: I'm talking about 5.1 here! >> >> On Thu, Feb 5, 2009 at 9:17 AM, xfile80303 <l...@grokers.net> wrote: >>> >>> Greetings all, >>> >>> I've searched this list and found several people looking to do the same >>> thing, but no definitive answers, so perhaps someone has some new info. >>> >>> Specifically, I would like to manipulate the URLs such that I can have >>> "nice" RESTful style URLs which feed information into the page ultimately >>> being rendered. >>> >>> For example: >>> >>> /app/venue_name/en_US/category/product/UUID >>> >>> where product would be the rendering page, UUID could be the activation >>> context (which, if I understand correctly T5 will handle already). >>> However, >>> the "venue_name" and locale are not actual pages and are simply >>> information >>> which is to be gleaned from the URL and passed to the page so it can >>> render >>> as specified. >>> >>> As other posts have suggested, it would seem to me that any manipulation >>> of >>> the URL would have to happen in such a way that Tapestry would properly >>> 1) >>> parse these URL "parameters" and pass them into the system for use by the >>> page, and 2) understand these "parameters" would need to be in Tapestry >>> generated links to preserve this data from link to link (page to page). >>> >>> There has been mention of using a RequestFilter or a Dispatcher to do >>> this, >>> but I have two concerns with this: 1) I am not sure how I would modify >>> the >>> Request (at all?) so Tapestry internals would find the page to render >>> (remove the venu_name and locale parameters and let Tapestry locate the >>> category/product page) 2) Even if I was able to modify the Request, how >>> would I accomplish #2 above, so generated links would contain this data? >>> >>> I appreciate your time and patience with this. >>> >>> Levi >>> -- >>> View this message in context: >>> http://n2.nabble.com/-T5--URL-Manipulation-tp2276010p2276010.html >>> Sent from the Tapestry Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>> >> >> >> >> -- >> Howard M. Lewis Ship >> >> Creator Apache Tapestry and Apache HiveMind >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> >> > > -- > View this message in context: > http://n2.nabble.com/-T5--URL-Manipulation-tp2276010p2277078.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
