Currently the logic necessary to do what you want is part of Tapestry internals (non public, subject to change). I would approach this problem using an override of the LinkFactory service (internal) combined with an in-Tapestry filter to extract the client name from the URL and perhaps a little extra work to replace the default component action and page render dispatchers. I would call that journeyman to master level work, not something a total beginner should try to attempt.
There are other options, such as bringing in a Tapestry expert to help out on this aspect. On Thu, Jul 10, 2008 at 9:17 AM, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > On Thu, Jul 10, 2008 at 6:10 PM, <[EMAIL PROTECTED]> wrote: > >> Is there a routing class in tapestry that can be manipulated? like routs.rb >> in RoR? Which would allow me to manipulate the URL->tapestry bindings? > > Not at all. You have other paths to reach the same (maybe similar) goal. > > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
